On 02/29/2012 12:44 PM, Gleb Natapov wrote: > > > > > > > Yes, crash can be so severe that it is not even detected by a kernel > > > itself, so not OOPS message even printed. But in most cases if kernel is > > > functional enough to print OOPS it is functional enough to call single > > > hypercall instruction. > > > > Why not print the oops to virtio-serial? Or even just a regular serial > > port? That's what bare metal does. > > > The more interface is complex the more chances it will fail during > panic. Regular serial is likely more reliable than virtio-serial. > Hypercall is likely more reliable than uart. On serial user can > fake panic notification. The serial device is under control of the kernel, so the user can only access it if the kernel so allows. > Can this be problematic? >From the point of view of the guest, yes, it can generate support calls in fill up the admin's dump quota. From the point of view of the host, there's no difference between the guest's admin and a random user. -- error compiling committee.c: too many arguments to function -- 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
