Messages in this thread | | | Date | Tue, 13 Mar 2012 10:54:14 +0200 | From | Avi Kivity <> | Subject | Re: [PATCH 0/2 v3] kvm: notify host when guest panicked |
| |
On 03/13/2012 08:44 AM, Wen Congyang wrote: > At 03/12/2012 06:33 PM, Avi Kivity Wrote: > > On 03/12/2012 11:04 AM, Wen Congyang wrote: > >> Do you have any other comments about this patch? > >> > > > > Not really, but I'm not 100% convinced the patch is worthwhile. It's > > likely to only be used by Linux, which has kexec facilities, and you can > > put talk to management via virtio-serial and describe the crash in more > > details than a simple hypercall. > > Hmm, can we use virtio-serial to talk with not-linux OS? I guess the answer > is no. If so, virtio-serial is also used by linux.
You can use virtio-serial with any guest that has a driver. There are drivers available for Windows.
> Another problem is: virtio-serial is available on many deployed versions > but the guest must have virtio-serial device. So we cannot know the guest > is panicked if it does not have virtio-serial device while the hypercall does > not depend on any device. >
The hypercall implementation must exist in the hypervisor.
virtio-serial is used by the guest agent, so it's likely to be availalble in all cloud or data center deployments.
-- error compiling committee.c: too many arguments to function
| |