On Mon, Mar 12, 2012 at 12:33:33PM +0200, 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. As mentioned before, I don't think virtio-serial is a good fit for this. We want something that is simple & guaranteed always available. Using virtio-serial requires significant setup work on both the host and guest. Many management application won't know to make a vioserial device available to all guests they create. Most administrators won't even configure kexec, let alone virtio serial on top of it. The hypercall requires zero host side config, and zero guest side config, which IMHO is what we need for this feature. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
