Il 07/05/2014 17:30, Abel Gordon ha scritto:
> > ... which we already do. The only secondary execution controls we allow are
> > APIC page, unrestricted guest, WBINVD exits, and of course EPT.
>
> But we don't verify if L1 tries to enable the feature for L1 (even if
> it's not exposed)... Or do
On Wed, May 7, 2014 at 2:40 PM, Paolo Bonzini wrote:
> Il 07/05/2014 13:37, Paolo Bonzini ha scritto:
>
>> Il 07/05/2014 13:16, Abel Gordon ha scritto:
> PLE should be left enabled, I think.
>>>
>>> Well... the PLE settings L0 uses to run L1 (vmcs01) may be different
>>> than the PLE
Il 07/05/2014 13:37, Paolo Bonzini ha scritto:
Il 07/05/2014 13:16, Abel Gordon ha scritto:
> PLE should be left enabled, I think.
Well... the PLE settings L0 uses to run L1 (vmcs01) may be different
than the PLE settings L1 configured to run L2 (vmcs12).
For example, L0 can use a ple_gap
Il 07/05/2014 13:16, Abel Gordon ha scritto:
> PLE should be left enabled, I think.
Well... the PLE settings L0 uses to run L1 (vmcs01) may be different
than the PLE settings L1 configured to run L2 (vmcs12).
For example, L0 can use a ple_gap to run L1 that is bigger than the
ple_gap L1
On Wed, May 7, 2014 at 11:58 AM, Paolo Bonzini wrote:
> Il 04/05/2014 18:33, Hu Yaohui ha scritto:
>
>>> I experienced a similar problem that was related to nested code
>>> having some bugs related to apicv and other new vmx features.
>>>
>>> For example, the code enabled posted interrupts to run
Il 04/05/2014 18:33, Hu Yaohui ha scritto:
I experienced a similar problem that was related to nested code
having some bugs related to apicv and other new vmx features.
For example, the code enabled posted interrupts to run L2 even when the
feature was not exposed to L1 and L1 didn't use it.
Il 04/05/2014 18:33, Hu Yaohui ha scritto:
I experienced a similar problem that was related to nested code
having some bugs related to apicv and other new vmx features.
For example, the code enabled posted interrupts to run L2 even when the
feature was not exposed to L1 and L1 didn't use it.
On Wed, May 7, 2014 at 11:58 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 04/05/2014 18:33, Hu Yaohui ha scritto:
I experienced a similar problem that was related to nested code
having some bugs related to apicv and other new vmx features.
For example, the code enabled posted interrupts
Il 07/05/2014 13:16, Abel Gordon ha scritto:
PLE should be left enabled, I think.
Well... the PLE settings L0 uses to run L1 (vmcs01) may be different
than the PLE settings L1 configured to run L2 (vmcs12).
For example, L0 can use a ple_gap to run L1 that is bigger than the
ple_gap L1
Il 07/05/2014 13:37, Paolo Bonzini ha scritto:
Il 07/05/2014 13:16, Abel Gordon ha scritto:
PLE should be left enabled, I think.
Well... the PLE settings L0 uses to run L1 (vmcs01) may be different
than the PLE settings L1 configured to run L2 (vmcs12).
For example, L0 can use a ple_gap to
On Wed, May 7, 2014 at 2:40 PM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 07/05/2014 13:37, Paolo Bonzini ha scritto:
Il 07/05/2014 13:16, Abel Gordon ha scritto:
PLE should be left enabled, I think.
Well... the PLE settings L0 uses to run L1 (vmcs01) may be different
than the PLE
Il 07/05/2014 17:30, Abel Gordon ha scritto:
... which we already do. The only secondary execution controls we allow are
APIC page, unrestricted guest, WBINVD exits, and of course EPT.
But we don't verify if L1 tries to enable the feature for L1 (even if
it's not exposed)... Or do we ?
Hi Abel,
Thanks a lot! It works now.
Best Wishes,
Yaohui
On Sun, May 4, 2014 at 10:57 AM, Abel Gordon wrote:
> On Fri, May 2, 2014 at 11:11 PM, Hu Yaohui wrote:
>>
>> On Fri, May 2, 2014 at 2:39 PM, Bandan Das wrote:
>> > Hu Yaohui writes:
>> >
>> >> On Fri, May 2, 2014 at 11:52 AM, Paolo
On Fri, May 2, 2014 at 11:11 PM, Hu Yaohui wrote:
>
> On Fri, May 2, 2014 at 2:39 PM, Bandan Das wrote:
> > Hu Yaohui writes:
> >
> >> On Fri, May 2, 2014 at 11:52 AM, Paolo Bonzini wrote:
> >>> Il 02/05/2014 17:17, Hu Yaohui ha scritto:
> >>>
> Hi Paolo,
> I have tried L0 with linux
On Fri, May 2, 2014 at 11:11 PM, Hu Yaohui loki2...@gmail.com wrote:
On Fri, May 2, 2014 at 2:39 PM, Bandan Das b...@redhat.com wrote:
Hu Yaohui loki2...@gmail.com writes:
On Fri, May 2, 2014 at 11:52 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 02/05/2014 17:17, Hu Yaohui ha scritto:
Hi Abel,
Thanks a lot! It works now.
Best Wishes,
Yaohui
On Sun, May 4, 2014 at 10:57 AM, Abel Gordon a...@stratoscale.com wrote:
On Fri, May 2, 2014 at 11:11 PM, Hu Yaohui loki2...@gmail.com wrote:
On Fri, May 2, 2014 at 2:39 PM, Bandan Das b...@redhat.com wrote:
Hu Yaohui
On Fri, May 2, 2014 at 2:39 PM, Bandan Das wrote:
> Hu Yaohui writes:
>
>> On Fri, May 2, 2014 at 11:52 AM, Paolo Bonzini wrote:
>>> Il 02/05/2014 17:17, Hu Yaohui ha scritto:
>>>
Hi Paolo,
I have tried L0 with linux kernel 3.14.2 and L1 with linux kernel 3.14.2
L1 QEMU
Hu Yaohui writes:
> On Fri, May 2, 2014 at 11:52 AM, Paolo Bonzini wrote:
>> Il 02/05/2014 17:17, Hu Yaohui ha scritto:
>>
>>> Hi Paolo,
>>> I have tried L0 with linux kernel 3.14.2 and L1 with linux kernel 3.14.2
>>> L1 QEMU qemu-1.7.0
>>> L2 QEMU qemu-1.7.0.
>>
>>
>> Do you mean L0 and L1?
>
On Fri, May 2, 2014 at 11:52 AM, Paolo Bonzini wrote:
> Il 02/05/2014 17:17, Hu Yaohui ha scritto:
>
>> Hi Paolo,
>> I have tried L0 with linux kernel 3.14.2 and L1 with linux kernel 3.14.2
>> L1 QEMU qemu-1.7.0
>> L2 QEMU qemu-1.7.0.
>
>
> Do you mean L0 and L1?
Yes.
>
> What is your QEMU
Il 02/05/2014 17:17, Hu Yaohui ha scritto:
Hi Paolo,
I have tried L0 with linux kernel 3.14.2 and L1 with linux kernel 3.14.2
L1 QEMU qemu-1.7.0
L2 QEMU qemu-1.7.0.
Do you mean L0 and L1?
What is your QEMU command line, and what is the processor? Also, what
guest you are running?
Paolo
Hi Paolo,
I have tried L0 with linux kernel 3.14.2 and L1 with linux kernel 3.14.2
L1 QEMU qemu-1.7.0
L2 QEMU qemu-1.7.0.
I still get the same error when running qemu in L1 guest.
KVM: entry failed, hardware error 0x0
EAX= EBX= ECX= EDX=0f61
ESI= EDI=
Il 02/05/2014 03:43, Hu Yaohui ha scritto:
Hi all,
I have a problem running the latest version of kvm with nested configuration.
I used to run it with kernel 3.2.2 both for L0 and L1, which works perfectly.
When I change my L0 to kernel 3.10.36, L1 to kernel 3.12.10.
When I start L2 guest in L1
Il 02/05/2014 03:43, Hu Yaohui ha scritto:
Hi all,
I have a problem running the latest version of kvm with nested configuration.
I used to run it with kernel 3.2.2 both for L0 and L1, which works perfectly.
When I change my L0 to kernel 3.10.36, L1 to kernel 3.12.10.
When I start L2 guest in L1
Hi Paolo,
I have tried L0 with linux kernel 3.14.2 and L1 with linux kernel 3.14.2
L1 QEMU qemu-1.7.0
L2 QEMU qemu-1.7.0.
I still get the same error when running qemu in L1 guest.
log
KVM: entry failed, hardware error 0x0
EAX= EBX= ECX= EDX=0f61
ESI=
Il 02/05/2014 17:17, Hu Yaohui ha scritto:
Hi Paolo,
I have tried L0 with linux kernel 3.14.2 and L1 with linux kernel 3.14.2
L1 QEMU qemu-1.7.0
L2 QEMU qemu-1.7.0.
Do you mean L0 and L1?
What is your QEMU command line, and what is the processor? Also, what
guest you are running?
Paolo
On Fri, May 2, 2014 at 11:52 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 02/05/2014 17:17, Hu Yaohui ha scritto:
Hi Paolo,
I have tried L0 with linux kernel 3.14.2 and L1 with linux kernel 3.14.2
L1 QEMU qemu-1.7.0
L2 QEMU qemu-1.7.0.
Do you mean L0 and L1?
Yes.
What is your QEMU
Hu Yaohui loki2...@gmail.com writes:
On Fri, May 2, 2014 at 11:52 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 02/05/2014 17:17, Hu Yaohui ha scritto:
Hi Paolo,
I have tried L0 with linux kernel 3.14.2 and L1 with linux kernel 3.14.2
L1 QEMU qemu-1.7.0
L2 QEMU qemu-1.7.0.
Do you mean
On Fri, May 2, 2014 at 2:39 PM, Bandan Das b...@redhat.com wrote:
Hu Yaohui loki2...@gmail.com writes:
On Fri, May 2, 2014 at 11:52 AM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 02/05/2014 17:17, Hu Yaohui ha scritto:
Hi Paolo,
I have tried L0 with linux kernel 3.14.2 and L1 with linux
Hi all,
I have a problem running the latest version of kvm with nested configuration.
I used to run it with kernel 3.2.2 both for L0 and L1, which works perfectly.
When I change my L0 to kernel 3.10.36, L1 to kernel 3.12.10.
When I start L2 guest in L1 with qemu-kvm. I get the following error
from
Hi all,
I have a problem running the latest version of kvm with nested configuration.
I used to run it with kernel 3.2.2 both for L0 and L1, which works perfectly.
When I change my L0 to kernel 3.10.36, L1 to kernel 3.12.10.
When I start L2 guest in L1 with qemu-kvm. I get the following error
from
30 matches
Mail list logo