1. 22 Sep, 2014 1 commit
    • Chrysostomos Nanakos's avatar
      async: aio_context_new(): Handle event_notifier_init failure · 2f78e491
      Chrysostomos Nanakos authored
      On a system with a low limit of open files the initialization
      of the event notifier could fail and QEMU exits without printing any
      error information to the user.
      The problem can be easily reproduced by enforcing a low limit of open
      files and start QEMU with enough I/O threads to hit this limit.
      The same problem raises, without the creation of I/O threads, while
      QEMU initializes the main event loop by enforcing an even lower limit of
      open files.
      This commit adds an error message on failure:
       # qemu [...] -object iothread,id=iothread0 -object iothread,id=iothread1
       qemu: Failed to initialize event notifier: Too many open files in system
      Signed-off-by: default avatarChrysostomos Nanakos <cnanakos@grnet.gr>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
  2. 20 Sep, 2014 1 commit
  3. 18 Sep, 2014 1 commit
  4. 11 Sep, 2014 1 commit
  5. 10 Sep, 2014 1 commit
  6. 04 Sep, 2014 1 commit
  7. 28 Aug, 2014 1 commit
  8. 26 Aug, 2014 1 commit
  9. 15 Aug, 2014 2 commits
  10. 06 Aug, 2014 2 commits
  11. 21 Jul, 2014 1 commit
  12. 17 Jul, 2014 1 commit
  13. 11 Jul, 2014 1 commit
  14. 01 Jul, 2014 2 commits
    • Yang Zhiyong's avatar
      trace: add qemu_system_powerdown_request and qemu_system_shutdown_request trace events · bc78cff9
      Yang Zhiyong authored
      We have the experience that the guest doesn't stop successfully
      though it was instructed to shut down.
      The root cause may be not in QEMU mostly.  However, QEMU is often
      suspected at the beginning just because the issue occurred in
      virtualization environment.
      Therefore, we need to affirm that QEMU received the shutdown
      request and raised ACPI irq from "virsh shutdown" command,
      virt-manger or stopping QEMU process to the VM .
      So that we can affirm the problems was belonged to the Guset OS
      rather than the QEMU itself.
      When we stop guests by "virsh shutdown" command or virt-manger,
      or stopping QEMU process, qemu_system_powerdown_request() or
      qemu_system_shutdown_request() is called. Then the below functions
      in main_loop_should_exit() of Vl.c are called roughly in the
      following order.
      	if (qemu_powerdown_requested())
      			monitor_protocol_event(QEVENT_POWERDOWN, NULL)
      		monitor_protocol_event(QEVENT_SHUTDOWN, NULL);
      The tracepoint of monitor_protocol_event() already exists, but no
      tracepoints are defined for qemu_system_powerdown_request() and
      qemu_system_shutdown_request(). So this patch adds two tracepoints for
      the two functions. We believe that it will become much easier to
      isolate the problem mentioned above by these tracepoints.
      Signed-off-by: default avatarYang Zhiyong <yangzy.fnst@cn.fujitsu.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
    • Paolo Bonzini's avatar
      memory: MemoryRegion: use /machine as default owner · b5c2c3d0
      Paolo Bonzini authored
      This will be added (after QOMification) as the QOM parent.
      Reviewed-by: default avatarPeter Crosthwaite <peter.crosthwaite@xilinx.com>
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
  15. 29 Jun, 2014 1 commit
  16. 23 Jun, 2014 12 commits
  17. 19 Jun, 2014 7 commits
  18. 18 Jun, 2014 2 commits
  19. 16 Jun, 2014 1 commit