On 10/20/2009 05:57 PM, Chris Lalancette wrote:
Nikola Ciprich wrote:
Hi,
maybe it's stupid question, but is this available also when qemu/kvm
is started using libvirt& stuff? I think it uses monitor so it's
inaccessible for user no?
Yes and no. The monitor is inaccessible when usin
Nikola Ciprich wrote:
> Hi,
> maybe it's stupid question, but is this available also when qemu/kvm
> is started using libvirt & stuff? I think it uses monitor so it's
> inaccessible for user no?
Yes and no. The monitor is inaccessible when using libvirt, but I totally
forgot that qemu dumps the
Hi,
maybe it's stupid question, but is this available also when qemu/kvm
is started using libvirt & stuff? I think it uses monitor so it's
inaccessible for user no?
n.
On Tue, Oct 20, 2009 at 10:42:24AM +0200, Chris Lalancette wrote:
> Avi Kivity wrote:
> > On 10/20/2009 04:50 PM, Chris Lalance
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
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.
regist
Gleb Natapov wrote:
> On Tue, Oct 20, 2009 at 09:50:45AM +0200, 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 t
On Tue, Oct 20, 2009 at 09:50:45AM +0200, 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/VMENT
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.
Signed-off-by: Chris Lalancette
---
arch/x86/kvm/vmx.c |
