On 06/05/2012 09:27 PM, Matthias Lange wrote:
> On Tue, Jun 05, 2012 at 04:09:30PM +0300, Avi Kivity wrote:
>> On 06/05/2012 02:59 PM, Matthias Lange wrote:
>> > Do you mean the ABI defined in the Intel Software Developer's manual 3B?
>> > Or is
>> > vmcs12 only an ABI internal to the kvm module?
On Tue, Jun 05, 2012 at 04:09:30PM +0300, Avi Kivity wrote:
> On 06/05/2012 02:59 PM, Matthias Lange wrote:
> > Do you mean the ABI defined in the Intel Software Developer's manual 3B? Or
> > is
> > vmcs12 only an ABI internal to the kvm module?
>
> The latter. We want to be able to live migrate
On 06/05/2012 02:59 PM, Matthias Lange wrote:
> On Sun, May 20, 2012 at 03:39:30PM +0300, Avi Kivity wrote:
>> On 05/18/2012 12:34 PM, Matthias Lange wrote:
>> > The following patch adds support for the GUEST_SMBASE field. This allows
>> > hypervisors running inside kvm read/write access to this fi
On Sun, May 20, 2012 at 03:39:30PM +0300, Avi Kivity wrote:
> On 05/18/2012 12:34 PM, Matthias Lange wrote:
> > The following patch adds support for the GUEST_SMBASE field. This allows
> > hypervisors running inside kvm read/write access to this field. I have
> > tested this to work on a Core i5 ma
On 05/18/2012 12:34 PM, Matthias Lange wrote:
> Hi,
>
> I was playing around with kvm's nested virtualization feature on Intel
> VT-x. When trying to access the GUEST_SMBASE (offset 0x4828)field of the
> VMCS I got a "VMREAD/VMWRITE from/to unsupported VMCS component" error.
> According to the Inte
Hi,
I was playing around with kvm's nested virtualization feature on Intel
VT-x. When trying to access the GUEST_SMBASE (offset 0x4828)field of the
VMCS I got a "VMREAD/VMWRITE from/to unsupported VMCS component" error.
According to the Intel manual this field is not optional. The error
results fr
