Re: [PATCH 0/2] Introduce panic hypercall

[Avi Kivity <avi@redhat.com>]

On 06/20/2011 04:38 PM, Daniel Gollub wrote:
> Introduce panic hypercall to enable the crashing guest to notify the
> host. This enables the host to run some actions as soon a guest
> crashed (kernel panic).
>
> This patch series introduces the panic hypercall at the host end.
> As well as the hypercall for KVM paravirtuliazed Linux guests, by
> registering the hypercall to the panic_notifier_list.
>
> The basic idea is to create KVM crashdump automatically as soon the
> guest paniced and power-cycle the VM (e.g. libvirt<on_crash />).

This would be more easily done via a "panic device" (I/O port or 
memory-mapped address) that the guest hits.  It would be intercepted by 
qemu without any new code in kvm.\

However, I'm not sure I see the gain.  Most enterprisey guests already 
contain in-guest crash dumpers which provide more information than a 
qemu memory dump could, since they know exact load addresses etc. and 
are integrated with crash analysis tools.  What do you have in mind?

-- 
error compiling committee.c: too many arguments to function