Re: KVM Nested L2 guest startup problems

[Hu Yaohui]

On Fri, May 2, 2014 at 2:39 PM, Bandan Das <bsd@xxxxxxxxxx> wrote:
> Hu Yaohui <loki2441@xxxxxxxxx> writes:
>
>> On Fri, May 2, 2014 at 11:52 AM, Paolo Bonzini <pbonzini@xxxxxxxxxx> 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 command line, and what is the processor?  Also, what guest
>>> you are running?
>>>
>> L0 host
>> - Debian 7 with linux kernel 3.14.2
>> - 24 pCPU, 120G pMEM
>> - cpu mode: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
>
> Ivy Bridge-EP ? Looks similar to
> https://bugzilla.kernel.org/show_bug.cgi?id=73331
>
> Just out of curiosity, any difference if you run with ept=0 ?
I have tried it. The same error with L0 kvm ept=1 and L1 kvm ept=0
Do you have any idea how the Ivy Bridge-EP problem is solved?
>
>> - QEMU command line of L1
>> $ sudo qemu-system-x86_64 -machine accel=kvm -drive
>> file=vdisk.img,if=virtio -m 4096 -smp 10 -net
>> nic,model=virtio,macaddr=52:54:00:12:34:80 -cpu kvm64,+vmx -net
>> tap,ifname=qtap0,script=no,downscript=no -vnc :2
>>
>> L1 guest
>> - Ubuntu 10.04 with linux kernel 3.14.2
>> - QEMU command line of L2
>> $qemu-system-x86_64  -machine accel=kvm -smp 2 -boot c -drive
>> file=/home/nested/vmdisks/vdisk1-virtnet.img,if=virtio -m 2048 -vnc :4
>> -net nic,model=virtio,macaddr=52:54:00:12:34:90 -net
>> tap,ifname=qtap0,script=no,downscript=no
>>
>> L2 guest
>> - Ubuntu 10.04 with linux kernel 2.6.32
>>> Paolo
>>>
>>>
>>>> I still get the same error when running qemu in L1 guest.
>>>
>>>
>> --
>> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/