I am testing out nested virtualization on a Lenovo x220 (Intel i7-2620M). I am running xen-unstable (23842:483c5f8319ad) and Linux 3.0 (Ubuntu 10.10). I brought up a Centos 5.6 VM and installed Xen that is packaged with it. I think it is a variant of 3.0. The CentOS Xen VM boots very slowly but it does finally come up in to the nested Dom0. Now when I do an "xm create" of an HVM domain I just get a blank sdl screen. I don''t even see the bios screen. Are there any more patches that I need to be adding to get this to work? I have also included some log output. Please let me know if you need any other info. Thanks, AP Config of nested hypervisor VM ======================kernel = "hvmloader" builder=''hvm'' memory = 1024 name = ''centos'' vcpus = 1 pae = 1 acpi = 1 apic = 1 vif = [ ''bridge=br0'' ] disk = [''phy:/dev/vollumvg/centos,hda,w'', ''phy:/dev/vollumvg/centosfi,hdb,w''] device_model = ''qemu-dm'' vnc = 0 sdl = 1 stdvga = 1 serial = ''pty'' monitor=1 usb=1 videoram = 16 nestedhvm = 1 Host Xen messages during nested hypervisor Xen VM boot --------------------------------------------------------------------------------------- (XEN) HVM2: HVM Loader (XEN) HVM2: Detected Xen v4.2-unstable (XEN) HVM2: Xenbus rings @0xfeffc000, event channel 2 (XEN) HVM2: System requested ROMBIOS (XEN) HVM2: CPU speed is 2691 MHz (XEN) irq.c:269: Dom2 PCI link 0 changed 0 -> 5 (XEN) HVM2: PCI-ISA link 0 routed to IRQ5 (XEN) irq.c:269: Dom2 PCI link 1 changed 0 -> 10 (XEN) HVM2: PCI-ISA link 1 routed to IRQ10 (XEN) irq.c:269: Dom2 PCI link 2 changed 0 -> 11 (XEN) HVM2: PCI-ISA link 2 routed to IRQ11 (XEN) irq.c:269: Dom2 PCI link 3 changed 0 -> 5 (XEN) HVM2: PCI-ISA link 3 routed to IRQ5 (XEN) HVM2: pci dev 01:2 INTD->IRQ5 (XEN) HVM2: pci dev 01:3 INTA->IRQ10 (XEN) HVM2: pci dev 03:0 INTA->IRQ5 (XEN) HVM2: pci dev 04:0 INTA->IRQ5 (XEN) HVM2: pci dev 02:0 bar 10 size 01000000: f0000008 (XEN) HVM2: pci dev 03:0 bar 14 size 01000000: f1000008 (XEN) HVM2: pci dev 03:0 bar 10 size 00000100: 0000c001 (XEN) HVM2: pci dev 04:0 bar 10 size 00000100: 0000c101 (XEN) HVM2: pci dev 04:0 bar 14 size 00000100: f2000000 (XEN) HVM2: pci dev 01:2 bar 20 size 00000020: 0000c201 (XEN) HVM2: pci dev 01:1 bar 20 size 00000010: 0000c221 (XEN) HVM2: Multiprocessor initialisation: (XEN) HVM2: - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM2: Testing HVM environment: (XEN) HVM2: - REP INSB across page boundaries ... passed (XEN) HVM2: - GS base MSRs and SWAPGS ... passed (XEN) HVM2: Passed 2 of 2 tests (XEN) HVM2: Writing SMBIOS tables ... (XEN) HVM2: Loading ROMBIOS ... (XEN) HVM2: 9724 bytes of ROMBIOS high-memory extensions: (XEN) HVM2: Relocating to 0xfc000000-0xfc0025fc ... done (XEN) HVM2: Creating MP tables ... (XEN) HVM2: Loading Standard VGABIOS ... (XEN) HVM2: Loading PCI Option ROM ... (XEN) HVM2: - Manufacturer: http://etherboot.org (XEN) HVM2: - Product name: gPXE (XEN) HVM2: Loading ACPI ... (XEN) HVM2: vm86 TSS at fc012800 (XEN) HVM2: BIOS map: (XEN) HVM2: c0000-c9fff: VGA BIOS (XEN) HVM2: ca000-d7fff: Etherboot ROM (XEN) HVM2: f0000-fffff: Main BIOS (XEN) HVM2: E820 table: (XEN) HVM2: [00]: 00000000:00000000 - 00000000:0009e000: RAM (XEN) HVM2: [01]: 00000000:0009e000 - 00000000:000a0000: RESERVED (XEN) HVM2: HOLE: 00000000:000a0000 - 00000000:000e0000 (XEN) HVM2: [02]: 00000000:000e0000 - 00000000:00100000: RESERVED (XEN) HVM2: [03]: 00000000:00100000 - 00000000:3f000000: RAM (XEN) HVM2: HOLE: 00000000:3f000000 - 00000000:fc000000 (XEN) HVM2: [04]: 00000000:fc000000 - 00000001:00000000: RESERVED (XEN) HVM2: Invoking ROMBIOS ... (XEN) HVM2: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $ (XEN) stdvga.c:147:d2 entering stdvga and caching modes (XEN) HVM2: VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert Exp $ (XEN) HVM2: VBE Bios $Id: vbe.c,v 1.60 2008/03/02 07:47:21 vruppert Exp $ (XEN) HVM2: Bochs BIOS - build: 06/23/99 (XEN) HVM2: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $ (XEN) HVM2: Options: apmbios pcibios eltorito PMM (XEN) HVM2: (XEN) HVM2: ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 (XEN) HVM2: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (10240 MBytes) (XEN) HVM2: ata0-1: PCHS=10402/16/63 translation=lba LCHS=652/255/63 (XEN) HVM2: ata0 slave: QEMU HARDDISK ATA-7 Hard-Disk (5120 MBytes) (XEN) HVM2: (XEN) HVM2: (XEN) HVM2: (XEN) HVM2: Press F12 for boot menu. (XEN) HVM2: (XEN) HVM2: Booting from Hard Disk... (XEN) HVM2: Booting from 0000:7c00 (XEN) HVM2: int13_harddisk: function 41, unmapped device for ELDL=82 (XEN) HVM2: int13_harddisk: function 08, unmapped device for ELDL=82 (XEN) HVM2: *** int 15h function AX=00c0, BX=0000 not yet supported! (XEN) HVM2: int13_harddisk: function 02, unmapped device for ELDL=82 (XEN) HVM2: int13_harddisk: function 41, unmapped device for ELDL=82 (XEN) irq.c:269: Dom2 PCI link 0 changed 5 -> 0 (XEN) irq.c:269: Dom2 PCI link 1 changed 10 -> 0 (XEN) irq.c:269: Dom2 PCI link 2 changed 11 -> 0 (XEN) irq.c:269: Dom2 PCI link 3 changed 5 -> 0 Nested Xen Messages during nested VM boot ------------------------------------------------------------------- (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version (XEN) memory.c:124:d0 Could not allocate order=9 extent: id=1 memflags=0 (0 of 1) (XEN) memory.c:124:d0 Could not allocate order=9 extent: id=1 memflags=0 (0 of 1) (XEN) memory.c:124:d0 Could not allocate order=9 extent: id=1 memflags=0 (0 of 1) (XEN) memory.c:124:d0 Could not allocate order=9 extent: id=1 memflags=0 (0 of 1) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Sep-17 13:42 UTC
Re: [Xen-devel] Testing nested virtualization on Intel CPUs
On Fri, Sep 16, 2011 at 06:16:20PM -0700, AP wrote:> I am testing out nested virtualization on a Lenovo x220 (Intel > i7-2620M). I am running xen-unstable (23842:483c5f8319ad) and Linux > 3.0 (Ubuntu 10.10). > I brought up a Centos 5.6 VM and installed Xen that is packaged with > it. I think it is a variant of 3.0. >Xen hypervisor in RHEL5 / CentOS5 is heavily patched Xen 3.1.2+. (the userland tools are 3.0.3-based though).> The CentOS Xen VM boots very > slowly but it does finally come up in to the nested Dom0. Now when I > do an "xm create" of an HVM domain I just get a blank sdl screen. I > don''t even see the bios screen. Are there any more patches that I need > to be adding to get this to work? >Hmm.. I remember AMD guys mentioning nested virt Xen-on-Xen and KVM-on-Xen works OK in xen-unstable. Not sure about the status of Intel nested virt currently. You could also try using Xen 4.x in the CentOS VM, just to see if that makes a difference. rpms in http://gitco.de/repo/ -- Pasi> I have also included some log output. Please let me know if you need > any other info. > > Thanks, > AP > > Config of nested hypervisor VM > ======================> kernel = "hvmloader" > builder=''hvm'' > memory = 1024 > name = ''centos'' > vcpus = 1 > pae = 1 > acpi = 1 > apic = 1 > vif = [ ''bridge=br0'' ] > disk = [''phy:/dev/vollumvg/centos,hda,w'', ''phy:/dev/vollumvg/centosfi,hdb,w''] > device_model = ''qemu-dm'' > vnc = 0 > sdl = 1 > stdvga = 1 > serial = ''pty'' > monitor=1 > usb=1 > videoram = 16 > nestedhvm = 1 > > Host Xen messages during nested hypervisor Xen VM boot > --------------------------------------------------------------------------------------- > (XEN) HVM2: HVM Loader > (XEN) HVM2: Detected Xen v4.2-unstable > (XEN) HVM2: Xenbus rings @0xfeffc000, event channel 2 > (XEN) HVM2: System requested ROMBIOS > (XEN) HVM2: CPU speed is 2691 MHz > (XEN) irq.c:269: Dom2 PCI link 0 changed 0 -> 5 > (XEN) HVM2: PCI-ISA link 0 routed to IRQ5 > (XEN) irq.c:269: Dom2 PCI link 1 changed 0 -> 10 > (XEN) HVM2: PCI-ISA link 1 routed to IRQ10 > (XEN) irq.c:269: Dom2 PCI link 2 changed 0 -> 11 > (XEN) HVM2: PCI-ISA link 2 routed to IRQ11 > (XEN) irq.c:269: Dom2 PCI link 3 changed 0 -> 5 > (XEN) HVM2: PCI-ISA link 3 routed to IRQ5 > (XEN) HVM2: pci dev 01:2 INTD->IRQ5 > (XEN) HVM2: pci dev 01:3 INTA->IRQ10 > (XEN) HVM2: pci dev 03:0 INTA->IRQ5 > (XEN) HVM2: pci dev 04:0 INTA->IRQ5 > (XEN) HVM2: pci dev 02:0 bar 10 size 01000000: f0000008 > (XEN) HVM2: pci dev 03:0 bar 14 size 01000000: f1000008 > (XEN) HVM2: pci dev 03:0 bar 10 size 00000100: 0000c001 > (XEN) HVM2: pci dev 04:0 bar 10 size 00000100: 0000c101 > (XEN) HVM2: pci dev 04:0 bar 14 size 00000100: f2000000 > (XEN) HVM2: pci dev 01:2 bar 20 size 00000020: 0000c201 > (XEN) HVM2: pci dev 01:1 bar 20 size 00000010: 0000c221 > (XEN) HVM2: Multiprocessor initialisation: > (XEN) HVM2: - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs > [2/8] ... done. > (XEN) HVM2: Testing HVM environment: > (XEN) HVM2: - REP INSB across page boundaries ... passed > (XEN) HVM2: - GS base MSRs and SWAPGS ... passed > (XEN) HVM2: Passed 2 of 2 tests > (XEN) HVM2: Writing SMBIOS tables ... > (XEN) HVM2: Loading ROMBIOS ... > (XEN) HVM2: 9724 bytes of ROMBIOS high-memory extensions: > (XEN) HVM2: Relocating to 0xfc000000-0xfc0025fc ... done > (XEN) HVM2: Creating MP tables ... > (XEN) HVM2: Loading Standard VGABIOS ... > (XEN) HVM2: Loading PCI Option ROM ... > (XEN) HVM2: - Manufacturer: http://etherboot.org > (XEN) HVM2: - Product name: gPXE > (XEN) HVM2: Loading ACPI ... > (XEN) HVM2: vm86 TSS at fc012800 > (XEN) HVM2: BIOS map: > (XEN) HVM2: c0000-c9fff: VGA BIOS > (XEN) HVM2: ca000-d7fff: Etherboot ROM > (XEN) HVM2: f0000-fffff: Main BIOS > (XEN) HVM2: E820 table: > (XEN) HVM2: [00]: 00000000:00000000 - 00000000:0009e000: RAM > (XEN) HVM2: [01]: 00000000:0009e000 - 00000000:000a0000: RESERVED > (XEN) HVM2: HOLE: 00000000:000a0000 - 00000000:000e0000 > (XEN) HVM2: [02]: 00000000:000e0000 - 00000000:00100000: RESERVED > (XEN) HVM2: [03]: 00000000:00100000 - 00000000:3f000000: RAM > (XEN) HVM2: HOLE: 00000000:3f000000 - 00000000:fc000000 > (XEN) HVM2: [04]: 00000000:fc000000 - 00000001:00000000: RESERVED > (XEN) HVM2: Invoking ROMBIOS ... > (XEN) HVM2: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $ > (XEN) stdvga.c:147:d2 entering stdvga and caching modes > (XEN) HVM2: VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert Exp $ > (XEN) HVM2: VBE Bios $Id: vbe.c,v 1.60 2008/03/02 07:47:21 vruppert Exp $ > (XEN) HVM2: Bochs BIOS - build: 06/23/99 > (XEN) HVM2: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $ > (XEN) HVM2: Options: apmbios pcibios eltorito PMM > (XEN) HVM2: > (XEN) HVM2: ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 > (XEN) HVM2: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (10240 MBytes) > (XEN) HVM2: ata0-1: PCHS=10402/16/63 translation=lba LCHS=652/255/63 > (XEN) HVM2: ata0 slave: QEMU HARDDISK ATA-7 Hard-Disk (5120 MBytes) > (XEN) HVM2: > (XEN) HVM2: > (XEN) HVM2: > (XEN) HVM2: Press F12 for boot menu. > (XEN) HVM2: > (XEN) HVM2: Booting from Hard Disk... > (XEN) HVM2: Booting from 0000:7c00 > (XEN) HVM2: int13_harddisk: function 41, unmapped device for ELDL=82 > (XEN) HVM2: int13_harddisk: function 08, unmapped device for ELDL=82 > (XEN) HVM2: *** int 15h function AX=00c0, BX=0000 not yet supported! > (XEN) HVM2: int13_harddisk: function 02, unmapped device for ELDL=82 > (XEN) HVM2: int13_harddisk: function 41, unmapped device for ELDL=82 > (XEN) irq.c:269: Dom2 PCI link 0 changed 5 -> 0 > (XEN) irq.c:269: Dom2 PCI link 1 changed 10 -> 0 > (XEN) irq.c:269: Dom2 PCI link 2 changed 11 -> 0 > (XEN) irq.c:269: Dom2 PCI link 3 changed 5 -> 0 > > > Nested Xen Messages during nested VM boot > ------------------------------------------------------------------- > (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version > (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version > (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version > (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version > (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version > (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version > (XEN) memory.c:124:d0 Could not allocate order=9 extent: id=1 > memflags=0 (0 of 1) > (XEN) memory.c:124:d0 Could not allocate order=9 extent: id=1 > memflags=0 (0 of 1) > (XEN) memory.c:124:d0 Could not allocate order=9 extent: id=1 > memflags=0 (0 of 1) > (XEN) memory.c:124:d0 Could not allocate order=9 extent: id=1 > memflags=0 (0 of 1) > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Sat, Sep 17, 2011 at 6:42 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Fri, Sep 16, 2011 at 06:16:20PM -0700, AP wrote: >> I am testing out nested virtualization on a Lenovo x220 (Intel >> i7-2620M). I am running xen-unstable (23842:483c5f8319ad) and Linux >> 3.0 (Ubuntu 10.10). >> I brought up a Centos 5.6 VM and installed Xen that is packaged with >> it. I think it is a variant of 3.0. >> > > Xen hypervisor in RHEL5 / CentOS5 is heavily patched Xen 3.1.2+. > (the userland tools are 3.0.3-based though). > > >> The CentOS Xen VM boots very >> slowly but it does finally come up in to the nested Dom0. Now when I >> do an "xm create" of an HVM domain I just get a blank sdl screen. I >> don''t even see the bios screen. Are there any more patches that I need >> to be adding to get this to work? >> > > Hmm.. I remember AMD guys mentioning nested virt Xen-on-Xen and KVM-on-Xen works OK in xen-unstable. > Not sure about the status of Intel nested virt currently. > > You could also try using Xen 4.x in the CentOS VM, just to see if that makes a difference. > rpms in http://gitco.de/repo/With Xen-4.1.0 from gitco the inner Dom0 kernel doesn''t come up fully. So I changed tracks and tried running KVM within the guest and installing an inner guest with KVM as the hypervisor. That seemingly worked! I passed -enable-kvm to qemu-kvm. Is there anyway of confirming this from the outer host Xen? AP> -- Pasi > > >> I have also included some log output. Please let me know if you need >> any other info. >> >> Thanks, >> AP >> >> Config of nested hypervisor VM >> ======================>> kernel = "hvmloader" >> builder=''hvm'' >> memory = 1024 >> name = ''centos'' >> vcpus = 1 >> pae = 1 >> acpi = 1 >> apic = 1 >> vif = [ ''bridge=br0'' ] >> disk = [''phy:/dev/vollumvg/centos,hda,w'', ''phy:/dev/vollumvg/centosfi,hdb,w''] >> device_model = ''qemu-dm'' >> vnc = 0 >> sdl = 1 >> stdvga = 1 >> serial = ''pty'' >> monitor=1 >> usb=1 >> videoram = 16 >> nestedhvm = 1 >> >> Host Xen messages during nested hypervisor Xen VM boot >> --------------------------------------------------------------------------------------- >> (XEN) HVM2: HVM Loader >> (XEN) HVM2: Detected Xen v4.2-unstable >> (XEN) HVM2: Xenbus rings @0xfeffc000, event channel 2 >> (XEN) HVM2: System requested ROMBIOS >> (XEN) HVM2: CPU speed is 2691 MHz >> (XEN) irq.c:269: Dom2 PCI link 0 changed 0 -> 5 >> (XEN) HVM2: PCI-ISA link 0 routed to IRQ5 >> (XEN) irq.c:269: Dom2 PCI link 1 changed 0 -> 10 >> (XEN) HVM2: PCI-ISA link 1 routed to IRQ10 >> (XEN) irq.c:269: Dom2 PCI link 2 changed 0 -> 11 >> (XEN) HVM2: PCI-ISA link 2 routed to IRQ11 >> (XEN) irq.c:269: Dom2 PCI link 3 changed 0 -> 5 >> (XEN) HVM2: PCI-ISA link 3 routed to IRQ5 >> (XEN) HVM2: pci dev 01:2 INTD->IRQ5 >> (XEN) HVM2: pci dev 01:3 INTA->IRQ10 >> (XEN) HVM2: pci dev 03:0 INTA->IRQ5 >> (XEN) HVM2: pci dev 04:0 INTA->IRQ5 >> (XEN) HVM2: pci dev 02:0 bar 10 size 01000000: f0000008 >> (XEN) HVM2: pci dev 03:0 bar 14 size 01000000: f1000008 >> (XEN) HVM2: pci dev 03:0 bar 10 size 00000100: 0000c001 >> (XEN) HVM2: pci dev 04:0 bar 10 size 00000100: 0000c101 >> (XEN) HVM2: pci dev 04:0 bar 14 size 00000100: f2000000 >> (XEN) HVM2: pci dev 01:2 bar 20 size 00000020: 0000c201 >> (XEN) HVM2: pci dev 01:1 bar 20 size 00000010: 0000c221 >> (XEN) HVM2: Multiprocessor initialisation: >> (XEN) HVM2: - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs >> [2/8] ... done. >> (XEN) HVM2: Testing HVM environment: >> (XEN) HVM2: - REP INSB across page boundaries ... passed >> (XEN) HVM2: - GS base MSRs and SWAPGS ... passed >> (XEN) HVM2: Passed 2 of 2 tests >> (XEN) HVM2: Writing SMBIOS tables ... >> (XEN) HVM2: Loading ROMBIOS ... >> (XEN) HVM2: 9724 bytes of ROMBIOS high-memory extensions: >> (XEN) HVM2: Relocating to 0xfc000000-0xfc0025fc ... done >> (XEN) HVM2: Creating MP tables ... >> (XEN) HVM2: Loading Standard VGABIOS ... >> (XEN) HVM2: Loading PCI Option ROM ... >> (XEN) HVM2: - Manufacturer: http://etherboot.org >> (XEN) HVM2: - Product name: gPXE >> (XEN) HVM2: Loading ACPI ... >> (XEN) HVM2: vm86 TSS at fc012800 >> (XEN) HVM2: BIOS map: >> (XEN) HVM2: c0000-c9fff: VGA BIOS >> (XEN) HVM2: ca000-d7fff: Etherboot ROM >> (XEN) HVM2: f0000-fffff: Main BIOS >> (XEN) HVM2: E820 table: >> (XEN) HVM2: [00]: 00000000:00000000 - 00000000:0009e000: RAM >> (XEN) HVM2: [01]: 00000000:0009e000 - 00000000:000a0000: RESERVED >> (XEN) HVM2: HOLE: 00000000:000a0000 - 00000000:000e0000 >> (XEN) HVM2: [02]: 00000000:000e0000 - 00000000:00100000: RESERVED >> (XEN) HVM2: [03]: 00000000:00100000 - 00000000:3f000000: RAM >> (XEN) HVM2: HOLE: 00000000:3f000000 - 00000000:fc000000 >> (XEN) HVM2: [04]: 00000000:fc000000 - 00000001:00000000: RESERVED >> (XEN) HVM2: Invoking ROMBIOS ... >> (XEN) HVM2: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $ >> (XEN) stdvga.c:147:d2 entering stdvga and caching modes >> (XEN) HVM2: VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert Exp $ >> (XEN) HVM2: VBE Bios $Id: vbe.c,v 1.60 2008/03/02 07:47:21 vruppert Exp $ >> (XEN) HVM2: Bochs BIOS - build: 06/23/99 >> (XEN) HVM2: $Revision: 1.221 $ $Date: 2008/12/07 17:32:29 $ >> (XEN) HVM2: Options: apmbios pcibios eltorito PMM >> (XEN) HVM2: >> (XEN) HVM2: ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 >> (XEN) HVM2: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (10240 MBytes) >> (XEN) HVM2: ata0-1: PCHS=10402/16/63 translation=lba LCHS=652/255/63 >> (XEN) HVM2: ata0 slave: QEMU HARDDISK ATA-7 Hard-Disk (5120 MBytes) >> (XEN) HVM2: >> (XEN) HVM2: >> (XEN) HVM2: >> (XEN) HVM2: Press F12 for boot menu. >> (XEN) HVM2: >> (XEN) HVM2: Booting from Hard Disk... >> (XEN) HVM2: Booting from 0000:7c00 >> (XEN) HVM2: int13_harddisk: function 41, unmapped device for ELDL=82 >> (XEN) HVM2: int13_harddisk: function 08, unmapped device for ELDL=82 >> (XEN) HVM2: *** int 15h function AX=00c0, BX=0000 not yet supported! >> (XEN) HVM2: int13_harddisk: function 02, unmapped device for ELDL=82 >> (XEN) HVM2: int13_harddisk: function 41, unmapped device for ELDL=82 >> (XEN) irq.c:269: Dom2 PCI link 0 changed 5 -> 0 >> (XEN) irq.c:269: Dom2 PCI link 1 changed 10 -> 0 >> (XEN) irq.c:269: Dom2 PCI link 2 changed 11 -> 0 >> (XEN) irq.c:269: Dom2 PCI link 3 changed 5 -> 0 >> >> >> Nested Xen Messages during nested VM boot >> ------------------------------------------------------------------- >> (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version >> (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version >> (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version >> (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version >> (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version >> (XEN) sysctl.c:51: Allowing physinfo call with newer ABI version >> (XEN) memory.c:124:d0 Could not allocate order=9 extent: id=1 >> memflags=0 (0 of 1) >> (XEN) memory.c:124:d0 Could not allocate order=9 extent: id=1 >> memflags=0 (0 of 1) >> (XEN) memory.c:124:d0 Could not allocate order=9 extent: id=1 >> memflags=0 (0 of 1) >> (XEN) memory.c:124:d0 Could not allocate order=9 extent: id=1 >> memflags=0 (0 of 1) >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Tim Deegan
2011-Sep-20 17:57 UTC
Re: [Xen-devel] Testing nested virtualization on Intel CPUs
Hi, Cc''ing Eddie Dong, who wrote this code. At 18:16 -0700 on 16 Sep (1316196980), AP wrote:> I am testing out nested virtualization on a Lenovo x220 (Intel > i7-2620M). I am running xen-unstable (23842:483c5f8319ad) and Linux > 3.0 (Ubuntu 10.10). > I brought up a Centos 5.6 VM and installed Xen that is packaged with > it. I think it is a variant of 3.0. The CentOS Xen VM boots very > slowly but it does finally come up in to the nested Dom0.Yes, booting Xen as a nested guest is very slow at startup, because of how Xen relocates the bottom 1MB at boot time. You might find that 32-bit Xen boots faster. In general I expect performance of a nested-HVM guest on Intel to be quite poor, because it doesn''t yet have nested EPT support. Eddie, is that something you''re working on? Tim. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Sep 20, 2011 10:57 AM, "Tim Deegan" <tim@xen.org> wrote:> > Hi, > > Cc''ing Eddie Dong, who wrote this code. > > At 18:16 -0700 on 16 Sep (1316196980), AP wrote: > > I am testing out nested virtualization on a Lenovo x220 (Intel > > i7-2620M). I am running xen-unstable (23842:483c5f8319ad) and Linux > > 3.0 (Ubuntu 10.10). > > I brought up a Centos 5.6 VM and installed Xen that is packaged with > > it. I think it is a variant of 3.0. The CentOS Xen VM boots very > > slowly but it does finally come up in to the nested Dom0. > > Yes, booting Xen as a nested guest is very slow at startup, because of > how Xen relocates the bottom 1MB at boot time. You might find that > 32-bit Xen boots faster. >Could please expand a little on why the relocation causes it to slow down? Thanks, AP> In general I expect performance of a nested-HVM guest on Intel to be > quite poor, because it doesn''t yet have nested EPT support. Eddie, is > that something you''re working on? > > Tim. >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Tim Deegan
2011-Sep-21 16:38 UTC
Re: [Xen-devel] Testing nested virtualization on Intel CPUs
At 22:18 -0700 on 20 Sep (1316557136), AP wrote:> > Yes, booting Xen as a nested guest is very slow at startup, because of > > how Xen relocates the bottom 1MB at boot time. You might find that > > 32-bit Xen boots faster. > > Could please expand a little on why the relocation causes it to slow down?IIRC, the relocation itself is very slow because Xen just copies the low 1MB, which includes the VGA hole, so there are a lot of emulated reads. Tim. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Alan Cox
2011-Sep-21 16:50 UTC
Re: [Xen-devel] Testing nested virtualization on Intel CPUs
On Wed, 21 Sep 2011 17:38:10 +0100 Tim Deegan <tim@xen.org> wrote:> At 22:18 -0700 on 20 Sep (1316557136), AP wrote: > > > Yes, booting Xen as a nested guest is very slow at startup, because of > > > how Xen relocates the bottom 1MB at boot time. You might find that > > > 32-bit Xen boots faster. > > > > Could please expand a little on why the relocation causes it to slow down? > > IIRC, the relocation itself is very slow because Xen just copies the low > 1MB, which includes the VGA hole, so there are a lot of emulated reads.That seems a bit odd - ISA space reads can have side effects. Alan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2011-Sep-21 17:23 UTC
Re: [Xen-devel] Testing nested virtualization on Intel CPUs
On 21/09/2011 09:50, "Alan Cox" <alan@lxorguk.ukuu.org.uk> wrote:> On Wed, 21 Sep 2011 17:38:10 +0100 > Tim Deegan <tim@xen.org> wrote: > >> At 22:18 -0700 on 20 Sep (1316557136), AP wrote: >>>> Yes, booting Xen as a nested guest is very slow at startup, because of >>>> how Xen relocates the bottom 1MB at boot time. You might find that >>>> 32-bit Xen boots faster. >>> >>> Could please expand a little on why the relocation causes it to slow down? >> >> IIRC, the relocation itself is very slow because Xen just copies the low >> 1MB, which includes the VGA hole, so there are a lot of emulated reads. > > That seems a bit odd - ISA space reads can have side effects.We should probably not do that then. :-) In fact we only do it because the code was more convenient that way. The first thing we do with out relocated copy of the bottom megabyte is zap it with poison bytes. -- Keir> Alan > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel