Fwd: Xen as L1 support

Fwd: Xen as L1 support

[Alex Palesandro]

[-- Attachment #1: Type: text/plain, Size: 723 bytes --]

Hi,
I'm new to KVM. I'm doing some test on nested Virtualization with Xen
and KVM. I tried to test the Xen hypervisor as L1 over KVM ( Linux
3.9.0) and I found this in
"xm dmesg" log ( for the complete log, see the attached file).
--------------------------------------------
(XEN) VMX: CPU0 has insufficent VMExit Control (00036fff but requires
min 00008200)
(XEN) VMX: failed to initialise.
--------------------------------------------

I found some bug-traces [1] [2] but the hex value here is different from the
previously reported one, so maybe that is a different issue.

Will Xen be supported as L1?

Many Thanks.

Alex

[1] https://patchwork.kernel.org/patch/1318301/
[2} https://patchwork.kernel.org/patch/789632/

[-- Attachment #2: xmdmesg.txt --]
[-- Type: text/plain, Size: 3536 bytes --]

(XEN) Xen version 4.1.4 (Debian 4.1.4-3+deb7u1) (carnil@debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) Sun May  5 14:44:49 UTC 2013
(XEN) Bootloader: GRUB 1.99-27+deb7u1
(XEN) Command line: placeholder
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000dfffd000 (usable)
(XEN)  00000000dfffd000 - 00000000e0000000 (reserved)
(XEN)  00000000feffc000 - 00000000ff000000 (reserved)
(XEN)  00000000fffc0000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000011b800000 (usable)
(XEN) ACPI: RSDP 000FDA10, 0014 (r0 BOCHS )
(XEN) ACPI: RSDT DFFFDF60, 0034 (r1 BOCHS  BXPCRSDT        1 BXPC        1)
(XEN) ACPI: FACP DFFFFD10, 0074 (r1 BOCHS  BXPCFACP        1 BXPC        1)
(XEN) ACPI: DSDT DFFFDFA0, 11A9 (r1   BXPC   BXDSDT        1 INTL 20100528)
(XEN) ACPI: FACS DFFFFCC0, 0040
(XEN) ACPI: SSDT DFFFF2E0, 09DC (r1 BOCHS  BXPCSSDT        1 BXPC        1)
(XEN) ACPI: APIC DFFFF190, 00B0 (r1 BOCHS  BXPCAPIC        1 BXPC        1)
(XEN) ACPI: HPET DFFFF150, 0038 (r1 BOCHS  BXPCHPET        1 BXPC        1)
(XEN) System RAM: 4023MB (4120176kB)
(XEN) Domain heap initialised
(XEN) Processor #0 6:2 APIC version 20
(XEN) Processor #1 6:2 APIC version 20
(XEN) Processor #2 6:2 APIC version 20
(XEN) Processor #3 6:2 APIC version 20
(XEN) Processor #4 6:2 APIC version 20
(XEN) Processor #5 6:2 APIC version 20
(XEN) Processor #6 6:2 APIC version 20
(XEN) Processor #7 6:2 APIC version 20
(XEN) IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Table is not found!
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2000.110 MHz processor.
(XEN) Initing memory sharing.
(XEN) I/O virtualisation disabled
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) Platform timer is 100.000MHz HPET
(XEN) Allocated console ring of 16 KiB.
(XEN) VMX: CPU0 has insufficent VMExit Control (00036fff but requires min 00008200)
(XEN) VMX: failed to initialise.
(XEN) Brought up 8 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x193d000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000110000000->0000000114000000 (960286 pages to be allocated)
(XEN)  Init. ramdisk: 0000000119a8e000->000000011b7ff200
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff8193d000
(XEN)  Init. ramdisk: ffffffff8193d000->ffffffff836ae200
(XEN)  Phys-Mach map: ffffffff836af000->ffffffff83e31480
(XEN)  Start info:    ffffffff83e32000->ffffffff83e324b4
(XEN)  Page tables:   ffffffff83e33000->ffffffff83e56000
(XEN)  Boot stack:    ffffffff83e56000->ffffffff83e57000
(XEN)  TOTAL:         ffffffff80000000->ffffffff84000000
(XEN)  ENTRY ADDRESS: ffffffff816ab200
(XEN) Dom0 has maximum 8 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 244kB init memory.

RE: Xen as L1 support

[Ren, Yongjie]

> -----Original Message-----
> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org]
> On Behalf Of Alex Palesandro
> Sent: Tuesday, May 14, 2013 10:51 PM
> To: kvm@vger.kernel.org
> Subject: Fwd: Xen as L1 support
> 
> Hi,
> I'm new to KVM. I'm doing some test on nested Virtualization with Xen
> and KVM. I tried to test the Xen hypervisor as L1 over KVM ( Linux
> 3.9.0) and I found this in
> "xm dmesg" log ( for the complete log, see the attached file).
> --------------------------------------------
> (XEN) VMX: CPU0 has insufficent VMExit Control (00036fff but requires
> min 00008200)
> (XEN) VMX: failed to initialise.
> --------------------------------------------
> 
> I found some bug-traces [1] [2] but the hex value here is different from the
> previously reported one, so maybe that is a different issue.
> 
> Will Xen be supported as L1?
> 
So far, I think it's NO. VMX doesn't work, but PV guest can work in L1 Xen.
There's a bug tracking 'Xen on KVM' issue.
https://bugzilla.kernel.org/show_bug.cgi?id=45931

Best Regards,
     Yongjie (Jay)


> Many Thanks.
> 
> Alex
> 
> [1] https://patchwork.kernel.org/patch/1318301/
> [2} https://patchwork.kernel.org/patch/789632/

Re: Xen as L1 support

[Paolo Bonzini]

Il 15/05/2013 03:24, Ren, Yongjie ha scritto:
>> -----Original Message-----
>> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org]
>> On Behalf Of Alex Palesandro
>> Sent: Tuesday, May 14, 2013 10:51 PM
>> To: kvm@vger.kernel.org
>> Subject: Fwd: Xen as L1 support
>>
>> Hi,
>> I'm new to KVM. I'm doing some test on nested Virtualization with Xen
>> and KVM. I tried to test the Xen hypervisor as L1 over KVM ( Linux
>> 3.9.0) and I found this in
>> "xm dmesg" log ( for the complete log, see the attached file).
>> --------------------------------------------
>> (XEN) VMX: CPU0 has insufficent VMExit Control (00036fff but requires
>> min 00008200)
>> (XEN) VMX: failed to initialise.
>> --------------------------------------------

This is the "Acknowledge interrupt on exit" control.  It shouldn't be
hard to implement it.

Paolo

>> I found some bug-traces [1] [2] but the hex value here is different from the
>> previously reported one, so maybe that is a different issue.
>>
>> Will Xen be supported as L1?
>>
> So far, I think it's NO. VMX doesn't work, but PV guest can work in L1 Xen.
> There's a bug tracking 'Xen on KVM' issue.
> https://bugzilla.kernel.org/show_bug.cgi?id=45931
> 
> Best Regards,
>      Yongjie (Jay)
> 
> 
>> Many Thanks.
>>
>> Alex
>>
>> [1] https://patchwork.kernel.org/patch/1318301/
>> [2} https://patchwork.kernel.org/patch/789632/
> N�����r��y���b�X��ǧv�^�)޺{.n�+����h��\x17��ܨ}���Ơz�&j:+v���\a����zZ+��+zf���h���~����i���z�\x1e�w���?����&�)ߢ^[fl===
> 

Re: Xen as L1 support

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]

On 2013-05-15 16:59, Paolo Bonzini wrote:
> Il 15/05/2013 03:24, Ren, Yongjie ha scritto:
>>> -----Original Message-----
>>> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org]
>>> On Behalf Of Alex Palesandro
>>> Sent: Tuesday, May 14, 2013 10:51 PM
>>> To: kvm@vger.kernel.org
>>> Subject: Fwd: Xen as L1 support
>>>
>>> Hi,
>>> I'm new to KVM. I'm doing some test on nested Virtualization with Xen
>>> and KVM. I tried to test the Xen hypervisor as L1 over KVM ( Linux
>>> 3.9.0) and I found this in
>>> "xm dmesg" log ( for the complete log, see the attached file).
>>> --------------------------------------------
>>> (XEN) VMX: CPU0 has insufficent VMExit Control (00036fff but requires
>>> min 00008200)
>>> (XEN) VMX: failed to initialise.
>>> --------------------------------------------
> 
> This is the "Acknowledge interrupt on exit" control.  It shouldn't be
> hard to implement it.

Isn't this a pretty recent feature Xen should be able to live without -
if it finds itself on a (virtually) older CPU?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

Re: Xen as L1 support

[Gleb Natapov]

On Wed, May 15, 2013 at 07:43:25PM +0200, Jan Kiszka wrote:
> On 2013-05-15 16:59, Paolo Bonzini wrote:
> > Il 15/05/2013 03:24, Ren, Yongjie ha scritto:
> >>> -----Original Message-----
> >>> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org]
> >>> On Behalf Of Alex Palesandro
> >>> Sent: Tuesday, May 14, 2013 10:51 PM
> >>> To: kvm@vger.kernel.org
> >>> Subject: Fwd: Xen as L1 support
> >>>
> >>> Hi,
> >>> I'm new to KVM. I'm doing some test on nested Virtualization with Xen
> >>> and KVM. I tried to test the Xen hypervisor as L1 over KVM ( Linux
> >>> 3.9.0) and I found this in
> >>> "xm dmesg" log ( for the complete log, see the attached file).
> >>> --------------------------------------------
> >>> (XEN) VMX: CPU0 has insufficent VMExit Control (00036fff but requires
> >>> min 00008200)
> >>> (XEN) VMX: failed to initialise.
> >>> --------------------------------------------
> > 
> > This is the "Acknowledge interrupt on exit" control.  It shouldn't be
> > hard to implement it.
> 
> Isn't this a pretty recent feature Xen should be able to live without -
> if it finds itself on a (virtually) older CPU?
> 
IIRC the feature was always there. KVM started to use it only from 3.10 since
posted interrupt requires it.

--
			Gleb.

Re: Xen as L1 support

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]

On 2013-05-15 19:45, Gleb Natapov wrote:
> On Wed, May 15, 2013 at 07:43:25PM +0200, Jan Kiszka wrote:
>> On 2013-05-15 16:59, Paolo Bonzini wrote:
>>> Il 15/05/2013 03:24, Ren, Yongjie ha scritto:
>>>>> -----Original Message-----
>>>>> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org]
>>>>> On Behalf Of Alex Palesandro
>>>>> Sent: Tuesday, May 14, 2013 10:51 PM
>>>>> To: kvm@vger.kernel.org
>>>>> Subject: Fwd: Xen as L1 support
>>>>>
>>>>> Hi,
>>>>> I'm new to KVM. I'm doing some test on nested Virtualization with Xen
>>>>> and KVM. I tried to test the Xen hypervisor as L1 over KVM ( Linux
>>>>> 3.9.0) and I found this in
>>>>> "xm dmesg" log ( for the complete log, see the attached file).
>>>>> --------------------------------------------
>>>>> (XEN) VMX: CPU0 has insufficent VMExit Control (00036fff but requires
>>>>> min 00008200)
>>>>> (XEN) VMX: failed to initialise.
>>>>> --------------------------------------------
>>>
>>> This is the "Acknowledge interrupt on exit" control.  It shouldn't be
>>> hard to implement it.
>>
>> Isn't this a pretty recent feature Xen should be able to live without -
>> if it finds itself on a (virtually) older CPU?
>>
> IIRC the feature was always there. KVM started to use it only from 3.10 since
> posted interrupt requires it.

Ah, indeed. Can even find it on a 6-years old Xeon.

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

Re: Xen as L1 support

[Gleb Natapov]

On Wed, May 15, 2013 at 04:59:24PM +0200, Paolo Bonzini wrote:
> Il 15/05/2013 03:24, Ren, Yongjie ha scritto:
> >> -----Original Message-----
> >> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org]
> >> On Behalf Of Alex Palesandro
> >> Sent: Tuesday, May 14, 2013 10:51 PM
> >> To: kvm@vger.kernel.org
> >> Subject: Fwd: Xen as L1 support
> >>
> >> Hi,
> >> I'm new to KVM. I'm doing some test on nested Virtualization with Xen
> >> and KVM. I tried to test the Xen hypervisor as L1 over KVM ( Linux
> >> 3.9.0) and I found this in
> >> "xm dmesg" log ( for the complete log, see the attached file).
> >> --------------------------------------------
> >> (XEN) VMX: CPU0 has insufficent VMExit Control (00036fff but requires
> >> min 00008200)
> >> (XEN) VMX: failed to initialise.
> >> --------------------------------------------
> 
> This is the "Acknowledge interrupt on exit" control.  It shouldn't be
> hard to implement it.
> 
To run 3.10 as L1 we need it anyway.

> Paolo
> 
> >> I found some bug-traces [1] [2] but the hex value here is different from the
> >> previously reported one, so maybe that is a different issue.
> >>
> >> Will Xen be supported as L1?
> >>
> > So far, I think it's NO. VMX doesn't work, but PV guest can work in L1 Xen.
> > There's a bug tracking 'Xen on KVM' issue.
> > https://bugzilla.kernel.org/show_bug.cgi?id=45931
> > 
> > Best Regards,
> >      Yongjie (Jay)
> > 
> > 
> >> Many Thanks.
> >>
> >> Alex
> >>
> >> [1] https://patchwork.kernel.org/patch/1318301/
> >> [2} https://patchwork.kernel.org/patch/789632/
> > N�����r��y���b�X��ǧv�^�)޺{.n�+����h��\x17��ܨ}���Ơz�&j:+v���\a����zZ+��+zf���h���~����i���z�\x1e�w���?����&�)ߢ^[fl===
> > 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
			Gleb.