Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 04 10月, 2014 1 次提交
  3. 30 9月, 2014 1 次提交
  5. 22 9月, 2014 1 次提交
    • C
      async: aio_context_new(): Handle event_notifier_init failure · 2f78e491
      由 Chrysostomos Nanakos 提交于 
      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: NChrysostomos Nanakos <cnanakos@grnet.gr>
Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      2f78e491
  7. 20 9月, 2014 1 次提交
  9. 19 9月, 2014 1 次提交
  11. 11 9月, 2014 1 次提交
  13. 10 9月, 2014 1 次提交
  15. 04 9月, 2014 1 次提交
  17. 29 8月, 2014 1 次提交
  19. 26 8月, 2014 1 次提交
  21. 15 8月, 2014 2 次提交
  23. 06 8月, 2014 2 次提交
  25. 22 7月, 2014 1 次提交
  27. 18 7月, 2014 1 次提交
  29. 12 7月, 2014 1 次提交
  31. 01 7月, 2014 2 次提交
    • Y
      trace: add qemu_system_powerdown_request and qemu_system_shutdown_request trace events · bc78cff9
      由 Yang Zhiyong 提交于 
      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())
		qemu_system_powerdown()
			monitor_protocol_event(QEVENT_POWERDOWN, NULL)

	OR

	if(qemu_shutdown_requested()}
		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: NYang Zhiyong <yangzy.fnst@cn.fujitsu.com>
Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      bc78cff9
    • P
      memory: MemoryRegion: use /machine as default owner · b5c2c3d0
      由 Paolo Bonzini 提交于 
      This will be added (after QOMification) as the QOM parent.
Reviewed-by: NPeter Crosthwaite <peter.crosthwaite@xilinx.com>
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      b5c2c3d0
  33. 29 6月, 2014 1 次提交
  35. 24 6月, 2014 1 次提交
  37. 23 6月, 2014 11 次提交
  39. 19 6月, 2014 8 次提交