On 11/04/2013 06:30 AM, Paolo Bonzini wrote: > After reporting the GUEST_PANICKED monitor event, QEMU stops the VM. > The reason for this is that events are edge-triggered, and can be lost if > management dies at the wrong time. Stopping a panicked VM lets management > know of a panic even if it has crashed; management can learn about the > panic when it restarts and queries running QEMU processes. The downside > is of course that the VM will be paused while management is not running, > but that is acceptable if it only happens with explicit "-device pvpanic". > > Upon learning of a panic, management (if configured to do so) can pick a > variety of behaviors: leave the VM paused, reset it, destroy it. In > addition to all of these behaviors, it is possible to dump the VM core > from the host. > ... > --- > gdbstub.c | 3 --- > vl.c | 6 ++---- > 2 files changed, 2 insertions(+), 7 deletions(-)
Reviewed-by: Eric Blake <ebl...@redhat.com> -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
