Avi Kivity wrote: > On 10/20/2009 04:50 PM, Chris Lalancette wrote: >> If we fail to handle a VMEXIT for some reason, print out a lot >> more debugging information about the state of the GUEST VMCS >> area. This does not fix a bug, but helps a lot when trying to >> track down the cause of a VMEXIT/VMENTRY failure. >> > > register state can just as easily be examined in the qemu monitor. > Ah, true. OK, forget this patch. -- Chris Lalancette -- 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