Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

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

切换分支/标签
  1. 26 8月, 2014 1 次提交
  3. 15 8月, 2014 2 次提交
  5. 06 8月, 2014 2 次提交
  7. 22 7月, 2014 1 次提交
  9. 18 7月, 2014 1 次提交
  11. 12 7月, 2014 1 次提交
  13. 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
  15. 29 6月, 2014 1 次提交
  17. 24 6月, 2014 1 次提交
  19. 23 6月, 2014 11 次提交
  21. 19 6月, 2014 9 次提交
  23. 16 6月, 2014 1 次提交
  25. 09 6月, 2014 1 次提交
    • L
      trace: Multi-backend tracing · 5b808275
      由 Lluís Vilanova 提交于 
      Adds support to compile QEMU with multiple tracing backends at the same time.

For example, you can compile QEMU with:

  $ ./configure --enable-trace-backends=ftrace,dtrace

Where 'ftrace' can be handy for having an in-flight record of events, and 'dtrace' can be later used to extract more information from the system.

This patch allows having both available without recompiling QEMU.
Signed-off-by: NLluís Vilanova <vilanova@ac.upc.edu>
Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      5b808275
  27. 06 6月, 2014 1 次提交
    • D
      qdev: Display warning about unused -global · 9f9260a3
      由 Don Slutz 提交于 
      This can help a user understand why -global was ignored.

For example: with "-vga cirrus"; "-global vga.vgamem_mb=16" is just
ignored when "-global cirrus-vga.vgamem_mb=16" is not.

This is currently clear when the wrong property is provided:

out/x86_64-softmmu/qemu-system-x86_64 -global cirrus-vga.vram_size_mb=16 -monitor pty -vga cirrus
char device redirected to /dev/pts/20 (label compat_monitor0)
qemu-system-x86_64: Property '.vram_size_mb' not found
Aborted (core dumped)

vs

out/x86_64-softmmu/qemu-system-x86_64 -global vga.vram_size_mb=16 -monitor pty -vga cirrus
char device redirected to /dev/pts/20 (label compat_monitor0)
VNC server running on `::1:5900'
^Cqemu: terminating on signal 2
Signed-off-by: NDon Slutz <dslutz@verizon.com>
Acked-by: NMichael S. Tsirkin <mst@redhat.com>
      9f9260a3
  29. 28 5月, 2014 3 次提交
  31. 24 5月, 2014 1 次提交
  33. 10 5月, 2014 1 次提交
    • K
      vl.c: remove init_clocks call from main · 02ce232c
      由 Kirill Batuzov 提交于 
      Clocks are initialized in qemu_init_main_loop. They are not needed before it.
Initializing them twice is not only unnecessary but is harmful: it results in
memory leak and potentially can lead to a situation where different parts of
QEMU use different sets of timers.

To avoid it remove init_clocks call from main and add an assertion to
qemu_clock_init that corresponding clock has not been initialized yet.
Signed-off-by: NKirill Batuzov <batuzovk@ispras.ru>
Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      02ce232c