1. 17 4月, 2018 2 次提交
  2. 16 4月, 2018 1 次提交
  3. 12 4月, 2018 3 次提交
  4. 10 4月, 2018 2 次提交
  5. 06 4月, 2018 1 次提交
  6. 03 4月, 2018 6 次提交
  7. 02 4月, 2018 1 次提交
  8. 26 3月, 2018 1 次提交
  9. 24 3月, 2018 1 次提交
  10. 15 3月, 2018 2 次提交
  11. 13 3月, 2018 5 次提交
  12. 12 3月, 2018 1 次提交
  13. 09 3月, 2018 11 次提交
  14. 08 3月, 2018 1 次提交
  15. 07 3月, 2018 1 次提交
    • M
      qemuDomainObjBeginJob: Don't account DESTROY job to maxQueuedJobs · c1766641
      Michal Privoznik 提交于
      When trying to destroy a domain (e.g. because we've seen EOF on
      the monitor) we try to acquire QEMU_JOB_DESTROY. However, if
      max_queued is set in qemu.conf this may fail and since our code
      doesn't count on that we will still report domain as active even
      though the qemu process is long gone. More specifically, if we've
      seen EOF on the monitor, qemuProcessHandleMonitorEOF() is called
      which sends MONITOR_EOF job to the event worker pool and
      unregisters monitor from the event loop. The worker pool calls
      processMonitorEOFEvent() which tries to set job which may fail
      due to the limit as described above.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      c1766641
  16. 22 2月, 2018 1 次提交