Hello all, this is my first post to the mailing list, so I hope this is the right way to ask a question. I''ve installed xen on my laptop (Asus N51Vf, specs here: http://www.asus.com/product.aspx?P_ID=0Tc42s23bOdbbvY5), as I''m currently at university and don''t have my proper desktop hardware to play with. The laptop supports IOMMU/Vt-d and has one PCI-e Geforce GT130M graphics card. I installed xen and the pvOps kernel (on top of kubuntu 9.10) according to the guide here: http://bderzhavets.wordpress.com/2009/08/31/loading-xen-via-grub2-on-top-ubuntu-karmic-server-alpha-4/ After some tweaking, it now boots up fine and I can start xend properly. The problem is that I cannot detach my graphics card from Dom0 (I compiled the kernel with hot-(un)plug support, but I think the problem occurs somewhere else). lspci outputs the following:> 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory >> Controller Hub (rev 07) > > 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express >> Graphics Port (rev 07) > > 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >> Controller #4 (rev 03) > > 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >> Controller #5 (rev 03) > > 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >> Controller #6 (rev 03) > > 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI >> Controller #2 (rev 03) > > 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio >> Controller (rev 03) > > 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port >> 1 (rev 03) > > 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port >> 2 (rev 03) > > 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port >> 3 (rev 03) > > 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port >> 4 (rev 03) > > 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port >> 5 (rev 03) > > 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port >> 6 (rev 03) > > 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >> Controller #1 (rev 03) > > 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >> Controller #2 (rev 03) > > 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >> Controller #3 (rev 03) > > 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI >> Controller #1 (rev 03) > > 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) > > 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev >> 03) > > 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller >> (rev 03) > > 01:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce GT 130M] >> (rev a1) > > 03:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100 > > 08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B >> PCI Express Gigabit Ethernet controller (rev 02) > > 09:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev >> 05) > > 09:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host >> Adapter (rev 22) > > 09:01.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host >> Adapter (rev 12) > > 09:01.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12) > >but using: xm pci-detach 0 0000:01:00.0 OR: xm pci-detach 0 01:00.0 returns:> Error: Cannot detach when pci platform does not exist > > Usage: xm pci-detach <Domain> <domain:bus:slot.func> > > >> Remove a domain''s pass-through pci device. > >Also, passing the pciback.hide=(01:00.0)(00:02.0) argument to the pvOps kernel doesn''t seem to have an effect (the appropriate modules are compiled statically into the kernel). Can anybody help me with this? Also, a little thing that''s annoying me, but is not as critical, is that my Dom0 crashes when xserver starts if graphics drivers are enabled. I assume this is because even Dom0 is not in the correct address space for DMA, and according to http://wiki.xensource.com/xenwiki/VTdHowTo, there is no DMA translation for Dom0. I don''t really need my graphics card for Dom0, but if anybody knows a way to get it working I''d appreciate it. Thanks, Kai _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
pciback was renamed to xen-pciback, I ran into this exact problem recently and bashed my head against the wall a bit to figure it out. Change your kernel cmdline to use xen-pciback.hide. Good luck! chris On Sun, Dec 20, 2009 at 10:28 AM, Kai Wohlfahrt <kjw53@cam.ac.uk> wrote:> Hello all, this is my first post to the mailing list, so I hope this is the > right way to ask a question. > > I''ve installed xen on my laptop (Asus N51Vf, specs here: > http://www.asus.com/product.aspx?P_ID=0Tc42s23bOdbbvY5), as I''m currently > at university and don''t have my proper desktop hardware to play with. The > laptop supports IOMMU/Vt-d and has one PCI-e Geforce GT130M graphics card. > > I installed xen and the pvOps kernel (on top of kubuntu 9.10) according to > the guide here: > http://bderzhavets.wordpress.com/2009/08/31/loading-xen-via-grub2-on-top-ubuntu-karmic-server-alpha-4/ > > After some tweaking, it now boots up fine and I can start xend properly. > > The problem is that I cannot detach my graphics card from Dom0 (I compiled > the kernel with hot-(un)plug support, but I think the problem occurs > somewhere else). > lspci outputs the following: > >> 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory >>> Controller Hub (rev 07) >> >> 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express >>> Graphics Port (rev 07) >> >> 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >>> Controller #4 (rev 03) >> >> 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >>> Controller #5 (rev 03) >> >> 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >>> Controller #6 (rev 03) >> >> 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI >>> Controller #2 (rev 03) >> >> 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio >>> Controller (rev 03) >> >> 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express >>> Port 1 (rev 03) >> >> 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express >>> Port 2 (rev 03) >> >> 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express >>> Port 3 (rev 03) >> >> 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express >>> Port 4 (rev 03) >> >> 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express >>> Port 5 (rev 03) >> >> 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express >>> Port 6 (rev 03) >> >> 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >>> Controller #1 (rev 03) >> >> 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >>> Controller #2 (rev 03) >> >> 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >>> Controller #3 (rev 03) >> >> 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI >>> Controller #1 (rev 03) >> >> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) >> >> 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev >>> 03) >> >> 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller >>> (rev 03) >> >> 01:00.0 VGA compatible controller: nVidia Corporation G96 [GeForce GT >>> 130M] (rev a1) >> >> 03:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100 >> >> 08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B >>> PCI Express Gigabit Ethernet controller (rev 02) >> >> 09:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller >>> (rev 05) >> >> 09:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host >>> Adapter (rev 22) >> >> 09:01.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host >>> Adapter (rev 12) >> >> 09:01.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev >>> 12) >> >> > but using: xm pci-detach 0 0000:01:00.0 OR: xm pci-detach 0 01:00.0 > returns: > >> Error: Cannot detach when pci platform does not exist >> >> Usage: xm pci-detach <Domain> <domain:bus:slot.func> >> >> >>> Remove a domain''s pass-through pci device. >> >> > Also, passing the pciback.hide=(01:00.0)(00:02.0) argument to the pvOps > kernel doesn''t seem to have an effect (the appropriate modules are compiled > statically into the kernel). > Can anybody help me with this? > > Also, a little thing that''s annoying me, but is not as critical, is that my > Dom0 crashes when xserver starts if graphics drivers are enabled. I assume > this is because even Dom0 is not in the correct address space for DMA, and > according to http://wiki.xensource.com/xenwiki/VTdHowTo, there is no DMA > translation for Dom0. I don''t really need my graphics card for Dom0, but if > anybody knows a way to get it working I''d appreciate it. > > Thanks, > Kai > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Still no luck with that. My grub entry looks like so:
menuentry "Xen-Unstable / Kubuntu 9.10 kernel 2.6.31.6 pvops"
{>
> insmod ext2
>
> set root=(hd0,1)
>
> multiboot (hd0,1)/boot/xen.gz dom0_mem=1048M iommu=force
>
> module (hd0,1)/boot/vmlinuz-2.6.31.6-xen xen-pciback.hide=(01:00.0)
>
> module (hd0,1)/boot/initrd.img-2.6.31.6-xen
>
> }
>
>
but my lspci still looks the same (i.e. it still has the line: 01:00.0 VGA
compatible controller: nVidia Corporation G96 [GeForce GT 130M] (rev a1)).
Using xm pci-detach still gives the same error as well (Error: Cannot detach
when pci platform does not exist)
Kai
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hello. I have this exact same problem myself. (I have four onboard gigabit network cards, pci 05:00.0, 06:00.0, 07:00.0 and 08:00.0) I tried using pciback.hide=(06:00.0)(07:00.0) . And in dom0, I now get: xen ~ # ifconfig eth1 eth1: error fetching interface information: Device not found And the same for eth2. So it apparently got "hidden", or detached. But the command "xm pci-list-assignable-devices" doesn''t return anything. And when trying "xm pci-detach", I get the same error as you (Cannot detach when pci platform does not exist). Even though I''ve compiled in all the support I can think of in the kernel. Running: Gentoo 2.6.31-xen-r10 xen-3.4.2-r1 // Jørn On Mon, Dec 21, 2009 at 10:22 PM, Kai Wohlfahrt <kjw53@cam.ac.uk> wrote:> Still no luck with that. My grub entry looks like so: > > menuentry "Xen-Unstable / Kubuntu 9.10 kernel 2.6.31.6 pvops" { >> >> insmod ext2 >> >> set root=(hd0,1) >> >> multiboot (hd0,1)/boot/xen.gz dom0_mem=1048M iommu=force >> >> module (hd0,1)/boot/vmlinuz-2.6.31.6-xen xen-pciback.hide=(01:00.0) >> >> module (hd0,1)/boot/initrd.img-2.6.31.6-xen >> >> } >> >> > but my lspci still looks the same (i.e. it still has the line: 01:00.0 VGA > compatible controller: nVidia Corporation G96 [GeForce GT 130M] (rev a1)). > > Using xm pci-detach still gives the same error as well (Error: Cannot > detach when pci platform does not exist) > > Kai > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I abandoned this project for a while since I''m back at university, but I think I got it to work by enabling the console ( console=tty0 on the vmlinuz module ). Try this and see if it works. Kai On Tue, Jan 19, 2010 at 1:49 PM, Jørn Odberg <jorn.odberg@gmail.com> wrote:> Hello. > > I have this exact same problem myself. > > (I have four onboard gigabit network cards, pci 05:00.0, 06:00.0, 07:00.0 > and 08:00.0) > I tried using pciback.hide=(06:00.0)(07:00.0) . And in dom0, I now get: > > xen ~ # ifconfig eth1 > eth1: error fetching interface information: Device not found > > And the same for eth2. So it apparently got "hidden", or detached. > > But the command "xm pci-list-assignable-devices" doesn''t return anything. > And when trying "xm pci-detach", I get the same error as you (Cannot detach > when pci platform does not exist). Even though I''ve compiled in all the > support I can think of in the kernel. > > Running: > Gentoo 2.6.31-xen-r10 > xen-3.4.2-r1 > > > // Jørn > > > On Mon, Dec 21, 2009 at 10:22 PM, Kai Wohlfahrt <kjw53@cam.ac.uk> wrote: > >> Still no luck with that. My grub entry looks like so: >> >> menuentry "Xen-Unstable / Kubuntu 9.10 kernel 2.6.31.6 pvops" { >>> >>> insmod ext2 >>> >>> set root=(hd0,1) >>> >>> multiboot (hd0,1)/boot/xen.gz dom0_mem=1048M iommu=force >>> >>> module (hd0,1)/boot/vmlinuz-2.6.31.6-xen xen-pciback.hide=(01:00.0) >>> >>> module (hd0,1)/boot/initrd.img-2.6.31.6-xen >>> >>> } >>> >>> >> but my lspci still looks the same (i.e. it still has the line: 01:00.0 VGA >> compatible controller: nVidia Corporation G96 [GeForce GT 130M] (rev a1)). >> >> Using xm pci-detach still gives the same error as well (Error: Cannot >> detach when pci platform does not exist) >> >> Kai >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jan 19, 2010 at 02:49:52PM +0100, Jørn Odberg wrote:> Hello. > > I have this exact same problem myself. > > (I have four onboard gigabit network cards, pci 05:00.0, 06:00.0, 07:00.0 > and 08:00.0) > I tried using pciback.hide=(06:00.0)(07:00.0) . And in dom0, I now get: >In the recent pv_ops dom0 kernels pciback module is now called xen-pciback, so you need to change that to xen-pciback.hide. -- Pasi> xen ~ # ifconfig eth1 > eth1: error fetching interface information: Device not found > > And the same for eth2. So it apparently got "hidden", or detached. > > But the command "xm pci-list-assignable-devices" doesn''t return anything. > And when trying "xm pci-detach", I get the same error as you (Cannot > detach when pci platform does not exist). Even though I''ve compiled in all > the support I can think of in the kernel. > > Running: > Gentoo 2.6.31-xen-r10 > xen-3.4.2-r1 > > // JÞrn > > On Mon, Dec 21, 2009 at 10:22 PM, Kai Wohlfahrt <[1]kjw53@cam.ac.uk> > wrote: > > Still no luck with that. My grub entry looks like so: > > menuentry "Xen-Unstable / Kubuntu 9.10 kernel 2.6.31.6 pvops" { > > insmod ext2 > > set root=(hd0,1) > > multiboot (hd0,1)/boot/xen.gz dom0_mem=1048M iommu=force > > module (hd0,1)/boot/vmlinuz-2.6.31.6-xen xen-pciback.hide=(01:00.0) > > module (hd0,1)/boot/initrd.img-2.6.31.6-xen > > } > > but my lspci still looks the same (i.e. it still has the line: 01:00.0 > VGA compatible controller: nVidia Corporation G96 [GeForce GT 130M] (rev > a1)). > Using xm pci-detach still gives the same error as well (Error: Cannot > detach when pci platform does not exist) > Kai > _______________________________________________ > Xen-users mailing list > [2]Xen-users@lists.xensource.com > [3]http://lists.xensource.com/xen-users > > References > > Visible links > 1. mailto:kjw53@cam.ac.uk > 2. mailto:Xen-users@lists.xensource.com > 3. http://lists.xensource.com/xen-users> _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jan 19, 2010 at 09:31:27PM +0100, Jørn Odberg wrote:> Hello, and thanks for the reply. > > I''ve added this to my grub (it may be redundant, but I got different > advices, so I added them all;): > > title Xen / Gentoo Linux 2.6.31-xen-r10 IOMMU > root (hd0,0) > kernel /boot/xen.gz iommu=1 vtd=1 > module /boot/vmlinuz-2.6.31-xen-r10 root=/dev/md2 pciback.permissiveOh, it looks like you''re not using pv_ops dom0 kernel, but gentoo kernel with xenlinux patches from opensuse. Then you can forget my xen-pciback comment.> xen-pciback.hide=(01:00.0)(08:00.0)(09:00.0) > pciback.hide=(01:00.0)(08:00.0)(09:00.0) guestdev=01:00.0,08:00.0,09:00.0 > reassign_resources console=tty0 > > And I have installed Xen 3.4.2-r1. > > xm dmesg , shows: > (XEN) Command line: iommu=1 vtd=1 > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) HVM: VMX enabled > (XEN) I/O virtualisation disabled >Please paste the full "xm dmesg", that doesn''t show why it''s disabled in Xen hypervisor. Did you enable VT-d in BIOS? -- Pasi> // JÞrn > > On Tue, Jan 19, 2010 at 7:19 PM, Pasi KÀrkkÀinen <[1]pasik@iki.fi> > wrote: > > On Tue, Jan 19, 2010 at 02:49:52PM +0100, JÞrn Odberg wrote: > >   Hello. > > > >   I have this exact same problem myself. > > > >   (I have four onboard gigabit network cards, pci 05:00.0, 06:00.0, > 07:00.0 > >   and 08:00.0) > >   I tried using pciback.hide=(06:00.0)(07:00.0) . And in dom0, I > now get: > > > > In the recent pv_ops dom0 kernels pciback module is now called > xen-pciback, > so you need to change that to xen-pciback.hide. > > -- Pasi > >   xen ~ # ifconfig eth1 > >   eth1: error fetching interface information: Device not found > > > >   And the same for eth2. So it apparently got "hidden", or > detached. > > > >   But the command "xm pci-list-assignable-devices" doesn''t return > anything. > >   And when trying "xm pci-detach", I get the same error as you > (Cannot > >   detach when pci platform does not exist). Even though I''ve > compiled in all > >   the support I can think of in the kernel. > > > >   Running: > >   Gentoo 2.6.31-xen-r10 > >   xen-3.4.2-r1 > > > >   // JÃ*ÅŸrn > > > >   On Mon, Dec 21, 2009 at 10:22 PM, Kai Wohlfahrt > <[1][2]kjw53@cam.ac.uk> > >   wrote: > > > >    Still no luck with that. My grub entry looks like so: > > > >      menuentry "Xen-Unstable / Kubuntu 9.10 kernel 2.6.31.6 > pvops" { > > > >      insmod ext2 > > > >      set root=(hd0,1) > > > >      multiboot (hd0,1)/boot/xen.gz dom0_mem=1048M iommu=force > > > >      module (hd0,1)/boot/vmlinuz-2.6.31.6-xen > xen-pciback.hide=(01:00.0) > > > >      module (hd0,1)/boot/initrd.img-2.6.31.6-xen > > > >      } > > > >    but my lspci still looks the same (i.e. it still has the line: > 01:00.0 > >    VGA compatible controller: nVidia Corporation G96 [GeForce GT > 130M] (rev > >    a1)). > >    Using xm pci-detach still gives the same error as well (Error: > Cannot > >    detach when pci platform does not exist) > >    Kai > >    _______________________________________________ > >    Xen-users mailing list > >    [2][3]Xen-users@lists.xensource.com > >    [3][4]http://lists.xensource.com/xen-users > > > > References > > > >   Visible links > >   1. mailto:[5]kjw53@cam.ac.uk > >   2. mailto:[6]Xen-users@lists.xensource.com > >   3. [7]http://lists.xensource.com/xen-users > > _______________________________________________ > > Xen-users mailing list > > [8]Xen-users@lists.xensource.com > > [9]http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-users mailing list > [10]Xen-users@lists.xensource.com > [11]http://lists.xensource.com/xen-users > > References > > Visible links > 1. mailto:pasik@iki.fi > 2. mailto:kjw53@cam.ac.uk > 3. mailto:Xen-users@lists.xensource.com > 4. http://lists.xensource.com/xen-users > 5. mailto:kjw53@cam.ac.uk > 6. mailto:Xen-users@lists.xensource.com > 7. http://lists.xensource.com/xen-users > 8. mailto:Xen-users@lists.xensource.com > 9. http://lists.xensource.com/xen-users > 10. mailto:Xen-users@lists.xensource.com > 11. http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Full xm dmesg output: __ __ _____ _ _ ____ \ \/ /___ _ __ |___ /| || | |___ \ \ // _ \ ''_ \ |_ \| || |_ __) | / \ __/ | | | ___) |__ _| / __/ /_/\_\___|_| |_| |____(_) |_|(_)_____| (XEN) Xen version 3.4.2 (root@) (gcc version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5) ) Fri Jan 15 10:45:24 CET 2010 (XEN) Latest ChangeSet: unavailable (XEN) Command line: iommu=1 vtd=1 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 2 MBR signatures (XEN) Found 2 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009cc00 (usable) (XEN) 000000000009cc00 - 00000000000a0000 (reserved) (XEN) 00000000000e4000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000bff70000 (usable) (XEN) 00000000bff70000 - 00000000bff7e000 (ACPI data) (XEN) 00000000bff7e000 - 00000000bffd0000 (ACPI NVS) (XEN) 00000000bffd0000 - 00000000c0000000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ffe00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000140000000 (usable) (XEN) System RAM: 4095MB (4193328kB) (XEN) ACPI: RSDP 000FB280, 0014 (r0 ACPIAM) (XEN) ACPI: RSDT BFF70000, 0044 (r1 A_M_I_ OEMRSDT 5000922 MSFT 97) (XEN) ACPI: FACP BFF70200, 0084 (r2 A_M_I_ OEMFACP 5000922 MSFT 97) (XEN) ACPI: DSDT BFF70440, 9EBF (r1 A1039 A1039001 1 INTL 20060113) (XEN) ACPI: FACS BFF7E000, 0040 (XEN) ACPI: APIC BFF70390, 006C (r1 A_M_I_ OEMAPIC 5000922 MSFT 97) (XEN) ACPI: MCFG BFF70400, 003C (r1 A_M_I_ OEMMCFG 5000922 MSFT 97) (XEN) ACPI: OEMB BFF7E040, 0089 (r1 A_M_I_ AMI_OEM 5000922 MSFT 97) (XEN) ACPI: HPET BFF7A300, 0038 (r1 A_M_I_ OEMHPET 5000922 MSFT 97) (XEN) ACPI: OSFR BFF7A340, 00B0 (r1 A_M_I_ OEMOSFR 5000922 MSFT 97) (XEN) ACPI: TCPA BFF7A3F0, 0032 (r1 A_M_I_ TBLOEMID 1 MSFT 97) (XEN) ACPI: SSDT BFF91A70, 0A7C (r1 DpgPmm CpuPm 12 INTL 20060113) (XEN) Domain heap initialised (XEN) Processor #0 7:7 APIC version 20 (XEN) Processor #1 7:7 APIC version 20 (XEN) Processor #2 7:7 APIC version 20 (XEN) Processor #3 7:7 APIC version 20 (XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) XSM Framework v1.0.0 initialized (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2666.422 MHz processor. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: VMX enabled (XEN) CPU0: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz stepping 0a (XEN) Booting processor 1/1 eip 8c000 (XEN) CPU1: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz stepping 0a (XEN) Booting processor 2/2 eip 8c000 (XEN) CPU2: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz stepping 0a (XEN) Booting processor 3/3 eip 8c000 (XEN) CPU3: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz stepping 0a (XEN) Total of 4 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) checking TSC synchronization across 4 CPUs: passed. (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 4 CPUs (XEN) I/O virtualisation disabled (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x7e6000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000013b000000->000000013c000000 (996433 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80200000->ffffffff807e6000 (XEN) Init. ramdisk: ffffffff807e6000->ffffffff807e6000 (XEN) Phys-Mach map: ffffea0000000000->ffffea00007a2288 (XEN) Start info: ffffffff807e6000->ffffffff807e64b4 (XEN) Page tables: ffffffff807e7000->ffffffff807f0000 (XEN) Boot stack: ffffffff807f0000->ffffffff807f1000 (XEN) TOTAL: ffffffff80000000->ffffffff80c00000 (XEN) ENTRY ADDRESS: ffffffff80200000 (XEN) Dom0 has maximum 4 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 136kB init memory. (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space (XEN) CPU 0 initialization completed (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space (XEN) CPU 1 initialization completed (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space (XEN) CPU 2 initialization completed (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space (XEN) CPU 3 initialization completed In the BIOS I could only find "Intel(R) Virtualization Tech - Enabled" , but no setting for VT-d... damn... DAMN! Does that mean I''m screwed?!? I bought this motherboard and cpu just to do Xen. Motherboard: ASUS P5Q Premium, P45, Socket-775. CPU: Intel Core 2 Quad Q9400. (Has "Intel Virtualization Technology") I was under the impression the Intel P45 chipset had "VT-d" ? ... :\ Am I screwed, or is it only me who screws something up? ;) // Jørn On Tue, Jan 19, 2010 at 9:35 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Tue, Jan 19, 2010 at 09:31:27PM +0100, Jørn Odberg wrote: > > Hello, and thanks for the reply. > > > > I''ve added this to my grub (it may be redundant, but I got different > > advices, so I added them all;): > > > > title Xen / Gentoo Linux 2.6.31-xen-r10 IOMMU > > root (hd0,0) > > kernel /boot/xen.gz iommu=1 vtd=1 > > module /boot/vmlinuz-2.6.31-xen-r10 root=/dev/md2 pciback.permissive > > Oh, it looks like you''re not using pv_ops dom0 kernel, but gentoo kernel > with > xenlinux patches from opensuse. > > Then you can forget my xen-pciback comment. > > > xen-pciback.hide=(01:00.0)(08:00.0)(09:00.0) > > pciback.hide=(01:00.0)(08:00.0)(09:00.0) > guestdev=01:00.0,08:00.0,09:00.0 > > reassign_resources console=tty0 > > > > And I have installed Xen 3.4.2-r1. > > > > xm dmesg , shows: > > (XEN) Command line: iommu=1 vtd=1 > > (XEN) VMX: Supported advanced features: > > (XEN) - APIC MMIO access virtualisation > > (XEN) - APIC TPR shadow > > (XEN) - Virtual NMI > > (XEN) - MSR direct-access bitmap > > (XEN) HVM: VMX enabled > > (XEN) I/O virtualisation disabled > > > > Please paste the full "xm dmesg", that doesn''t show why it''s disabled in > Xen hypervisor. > > Did you enable VT-d in BIOS? > > -- Pasi > > > // JÞrn > > > > On Tue, Jan 19, 2010 at 7:19 PM, Pasi KÀrkkÀinen <[1]pasik@iki.fi> > > wrote: > > > > On Tue, Jan 19, 2010 at 02:49:52PM +0100, JÞrn Odberg wrote: > > >   Hello. > > > > > >   I have this exact same problem myself. > > > > > >   (I have four onboard gigabit network cards, pci 05:00.0, > 06:00.0, > > 07:00.0 > > >   and 08:00.0) > > >   I tried using pciback.hide=(06:00.0)(07:00.0) . And in dom0, > I > > now get: > > > > > > > In the recent pv_ops dom0 kernels pciback module is now called > > xen-pciback, > > so you need to change that to xen-pciback.hide. > > > > -- Pasi > > >   xen ~ # ifconfig eth1 > > >   eth1: error fetching interface information: Device not found > > > > > >   And the same for eth2. So it apparently got "hidden", or > > detached. > > > > > >   But the command "xm pci-list-assignable-devices" doesn''t > return > > anything. > > >   And when trying "xm pci-detach", I get the same error as you > > (Cannot > > >   detach when pci platform does not exist). Even though I''ve > > compiled in all > > >   the support I can think of in the kernel. > > > > > >   Running: > > >   Gentoo 2.6.31-xen-r10 > > >   xen-3.4.2-r1 > > > > > >   // JÃ*ÅŸrn > > > > > >   On Mon, Dec 21, 2009 at 10:22 PM, Kai Wohlfahrt > > <[1][2]kjw53@cam.ac.uk> > > >   wrote: > > > > > >    Still no luck with that. My grub entry looks like so: > > > > > >      menuentry "Xen-Unstable / Kubuntu 9.10 kernel > 2.6.31.6 > > pvops" { > > > > > >      insmod ext2 > > > > > >      set root=(hd0,1) > > > > > >      multiboot (hd0,1)/boot/xen.gz dom0_mem=1048M > iommu=force > > > > > >      module (hd0,1)/boot/vmlinuz-2.6.31.6-xen > > xen-pciback.hide=(01:00.0) > > > > > >      module (hd0,1)/boot/initrd.img-2.6.31.6-xen > > > > > >      } > > > > > >    but my lspci still looks the same (i.e. it still has the > line: > > 01:00.0 > > >    VGA compatible controller: nVidia Corporation G96 [GeForce > GT > > 130M] (rev > > >    a1)). > > >    Using xm pci-detach still gives the same error as well > (Error: > > Cannot > > >    detach when pci platform does not exist) > > >    Kai > > >    _______________________________________________ > > >    Xen-users mailing list > > >    [2][3]Xen-users@lists.xensource.com > > >    [3][4]http://lists.xensource.com/xen-users > > > > > > References > > > > > >   Visible links > > >   1. mailto:[5]kjw53@cam.ac.uk > > >   2. mailto:[6]Xen-users@lists.xensource.com > > >   3. [7]http://lists.xensource.com/xen-users > > > _______________________________________________ > > > Xen-users mailing list > > > [8]Xen-users@lists.xensource.com > > > [9]http://lists.xensource.com/xen-users > > > > _______________________________________________ > > Xen-users mailing list > > [10]Xen-users@lists.xensource.com > > [11]http://lists.xensource.com/xen-users > > > > References > > > > Visible links > > 1. mailto:pasik@iki.fi > > 2. mailto:kjw53@cam.ac.uk > > 3. mailto:Xen-users@lists.xensource.com > > 4. http://lists.xensource.com/xen-users > > 5. mailto:kjw53@cam.ac.uk > > 6. mailto:Xen-users@lists.xensource.com > > 7. http://lists.xensource.com/xen-users > > 8. mailto:Xen-users@lists.xensource.com > > 9. http://lists.xensource.com/xen-users > > 10. mailto:Xen-users@lists.xensource.com > > 11. http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jan 19, 2010 at 09:46:26PM +0100, Jørn Odberg wrote:> Full xm dmesg output: > >  __ __           _____ _ _   ____ >  \ \/ /___ _ __  |___ /| || | |___ \ >  \ // _ \ ''_ \   |_ \| || |_  __) | >  / \ __/ | | | ___) |__  _| / __/ >  /_/\_\___|_| |_| |____(_) |_|(_)_____| >                                       > (XEN) Xen version 3.4.2 (root@) (gcc version 4.3.4 (Gentoo 4.3.4 p1.0, > pie-10.1.5) ) Fri Jan 15 10:45:24 CET 2010 > (XEN) Latest ChangeSet: unavailable > (XEN) Command line: iommu=1 vtd=1 > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (XEN) Disc information: > (XEN) Found 2 MBR signatures > (XEN) Found 2 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009cc00 (usable) > (XEN) 000000000009cc00 - 00000000000a0000 (reserved) > (XEN) 00000000000e4000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 00000000bff70000 (usable) > (XEN) 00000000bff70000 - 00000000bff7e000 (ACPI data) > (XEN) 00000000bff7e000 - 00000000bffd0000 (ACPI NVS) > (XEN) 00000000bffd0000 - 00000000c0000000 (reserved) > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > (XEN) 00000000ffe00000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 0000000140000000 (usable) > (XEN) System RAM: 4095MB (4193328kB) > (XEN) ACPI: RSDP 000FB280, 0014 (r0 ACPIAM) > (XEN) ACPI: RSDT BFF70000, 0044 (r1 A_M_I_ OEMRSDT  5000922 > MSFT      97) > (XEN) ACPI: FACP BFF70200, 0084 (r2 A_M_I_ OEMFACP  5000922 > MSFT      97) > (XEN) ACPI: DSDT BFF70440, 9EBF (r1 A1039 A1039001       1 INTL > 20060113) > (XEN) ACPI: FACS BFF7E000, 0040 > (XEN) ACPI: APIC BFF70390, 006C (r1 A_M_I_ OEMAPIC  5000922 > MSFT      97) > (XEN) ACPI: MCFG BFF70400, 003C (r1 A_M_I_ OEMMCFG  5000922 > MSFT      97) > (XEN) ACPI: OEMB BFF7E040, 0089 (r1 A_M_I_ AMI_OEM  5000922 > MSFT      97) > (XEN) ACPI: HPET BFF7A300, 0038 (r1 A_M_I_ OEMHPET  5000922 > MSFT      97) > (XEN) ACPI: OSFR BFF7A340, 00B0 (r1 A_M_I_ OEMOSFR  5000922 > MSFT      97) > (XEN) ACPI: TCPA BFF7A3F0, 0032 (r1 A_M_I_ TBLOEMID       1 > MSFT      97) > (XEN) ACPI: SSDT BFF91A70, 0A7C (r1 DpgPmm   CpuPm      12 INTL > 20060113) > (XEN) Domain heap initialised > (XEN) Processor #0 7:7 APIC version 20 > (XEN) Processor #1 7:7 APIC version 20 > (XEN) Processor #2 7:7 APIC version 20 > (XEN) Processor #3 7:7 APIC version 20 > (XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23 > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) XSM Framework v1.0.0 initialized > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 2666.422 MHz processor. > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) HVM: VMX enabled > (XEN) CPU0: Intel(R) Core(TM)2 Quad CPU   Q9400 @ 2.66GHz stepping > 0a > (XEN) Booting processor 1/1 eip 8c000 > (XEN) CPU1: Intel(R) Core(TM)2 Quad CPU   Q9400 @ 2.66GHz stepping > 0a > (XEN) Booting processor 2/2 eip 8c000 > (XEN) CPU2: Intel(R) Core(TM)2 Quad CPU   Q9400 @ 2.66GHz stepping > 0a > (XEN) Booting processor 3/3 eip 8c000 > (XEN) CPU3: Intel(R) Core(TM)2 Quad CPU   Q9400 @ 2.66GHz stepping > 0a > (XEN) Total of 4 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using new ACK method > (XEN) checking TSC synchronization across 4 CPUs: passed. > (XEN) Platform timer is 14.318MHz HPET > (XEN) Brought up 4 CPUs > (XEN) I/O virtualisation disabled > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x7e6000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.:  000000013b000000->000000013c000000 (996433 pages > to be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff80200000->ffffffff807e6000 > (XEN) Init. ramdisk: ffffffff807e6000->ffffffff807e6000 > (XEN) Phys-Mach map: ffffea0000000000->ffffea00007a2288 > (XEN) Start info:   ffffffff807e6000->ffffffff807e64b4 > (XEN) Page tables:  ffffffff807e7000->ffffffff807f0000 > (XEN) Boot stack:   ffffffff807f0000->ffffffff807f1000 > (XEN) TOTAL:        ffffffff80000000->ffffffff80c00000 > (XEN) ENTRY ADDRESS: ffffffff80200000 > (XEN) Dom0 has maximum 4 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 136kB init memory. > (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > (XEN) CPU 0 initialization completed > (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > (XEN) CPU 1 initialization completed > (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > (XEN) CPU 2 initialization completed > (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > (XEN) CPU 3 initialization completed > > In the BIOS I could only find "Intel(R) Virtualization Tech    - > Enabled" , but no setting for VT-d... damn... DAMN! Does that mean I''m > screwed?!? I bought this motherboard and cpu just to do Xen. > > Motherboard: ASUS P5Q Premium, P45, Socket-775. > CPU: Intel Core 2 Quad Q9400. (Has "Intel Virtualization Technology") > > I was under the impression the Intel P45 chipset had "VT-d" ? ... :\ > > Am I screwed, or is it only me who screws something up? ;) >Looks bad.. nothing about ACPI DMAR in the log, which is used by VT-d IOMMU.. It looks like your chipset/BIOS doesn''t support VT-d. This wiki page lists some motherboards/chipsets with IOMMU (VT-d): http://wiki.xensource.com/xenwiki/VTdHowTo I don''t see P45 there.. does Asus claim it supports VT-d ? -- Pasi> // JÞrn > > On Tue, Jan 19, 2010 at 9:35 PM, Pasi KÀrkkÀinen <[1]pasik@iki.fi> > wrote: > > On Tue, Jan 19, 2010 at 09:31:27PM +0100, JÞrn Odberg wrote: > >   Hello, and thanks for the reply. > > > >   I''ve added this to my grub (it may be redundant, but I got > different > >   advices, so I added them all;): > > > >   title Xen / Gentoo Linux 2.6.31-xen-r10 IOMMU > >   root (hd0,0) > >   kernel /boot/xen.gz iommu=1 vtd=1 > >   module /boot/vmlinuz-2.6.31-xen-r10 root=/dev/md2 > pciback.permissive > > Oh, it looks like you''re not using pv_ops dom0 kernel, but gentoo kernel > with > xenlinux patches from opensuse. > > Then you can forget my xen-pciback comment. > >   xen-pciback.hide=(01:00.0)(08:00.0)(09:00.0) > >   pciback.hide=(01:00.0)(08:00.0)(09:00.0) > guestdev=01:00.0,08:00.0,09:00.0 > >   reassign_resources console=tty0 > > > >   And I have installed Xen 3.4.2-r1. > > > >   xm dmesg , shows: > >   (XEN) Command line: iommu=1 vtd=1 > >   (XEN) VMX: Supported advanced features: > >   (XEN)Ã*  - APIC MMIO access virtualisation > >   (XEN)Ã*  - APIC TPR shadow > >   (XEN)Ã*  - Virtual NMI > >   (XEN)Ã*  - MSR direct-access bitmap > >   (XEN) HVM: VMX enabled > >   (XEN) I/O virtualisation disabled > > > > Please paste the full "xm dmesg", that doesn''t show why it''s disabled in > Xen hypervisor. > > Did you enable VT-d in BIOS? > > -- Pasi > > >   // JÃ*ÅŸrn > > > >   On Tue, Jan 19, 2010 at 7:19 PM, Pasi KÃ*â*¬rkkÃ*â*¬inen > <[1][2]pasik@iki.fi> > >   wrote: > > > >    On Tue, Jan 19, 2010 at 02:49:52PM +0100, JÃ*ÅŸrn Odberg > wrote: > >    > Ã*  Ã* Hello. > >    > > >    > Ã*  Ã* I have this exact same problem myself. > >    > > >    > Ã*  Ã* (I have four onboard gigabit network cards, pci > 05:00.0, 06:00.0, > >    07:00.0 > >    > Ã*  Ã* and 08:00.0) > >    > Ã*  Ã* I tried using pciback.hide=(06:00.0)(07:00.0) . And > in dom0, I > >    now get: > >    > > > > >    In the recent pv_ops dom0 kernels pciback module is now called > >    xen-pciback, > >    so you need to change that to xen-pciback.hide. > > > >    -- Pasi > >    > Ã*  Ã* xen ~ # ifconfig eth1 > >    > Ã*  Ã* eth1: error fetching interface information: Device > not found > >    > > >    > Ã*  Ã* And the same for eth2. So it apparently got > "hidden", or > >    detached. > >    > > >    > Ã*  Ã* But the command "xm pci-list-assignable-devices" > doesn''t return > >    anything. > >    > Ã*  Ã* And when trying "xm pci-detach", I get the same > error as you > >    (Cannot > >    > Ã*  Ã* detach when pci platform does not exist). Even > though I''ve > >    compiled in all > >    > Ã*  Ã* the support I can think of in the kernel. > >    > > >    > Ã*  Ã* Running: > >    > Ã*  Ã* Gentoo 2.6.31-xen-r10 > >    > Ã*  Ã* xen-3.4.2-r1 > >    > > >    > Ã*  Ã* // JÃ**Ã*Åžrn > >    > > >    > Ã*  Ã* On Mon, Dec 21, 2009 at 10:22 PM, Kai Wohlfahrt > >    <[1][2][3]kjw53@cam.ac.uk> > >    > Ã*  Ã* wrote: > >    > > >    > Ã*  Ã*  Ã* Still no luck with that. My grub entry looks > like so: > >    > > >    > Ã*  Ã*  Ã*  Ã*  Ã* menuentry "Xen-Unstable / Kubuntu > 9.10 kernel 2.6.31.6 > >    pvops" { > >    > > >    > Ã*  Ã*  Ã*  Ã*  Ã* insmod ext2 > >    > > >    > Ã*  Ã*  Ã*  Ã*  Ã* set root=(hd0,1) > >    > > >    > Ã*  Ã*  Ã*  Ã*  Ã* multiboot (hd0,1)/boot/xen.gz > dom0_mem=1048M iommu=force > >    > > >    > Ã*  Ã*  Ã*  Ã*  Ã* module > (hd0,1)/boot/vmlinuz-2.6.31.6-xen > >    xen-pciback.hide=(01:00.0) > >    > > >    > Ã*  Ã*  Ã*  Ã*  Ã* module > (hd0,1)/boot/initrd.img-2.6.31.6-xen > >    > > >    > Ã*  Ã*  Ã*  Ã*  Ã* } > >    > > >    > Ã*  Ã*  Ã* but my lspci still looks the same (i.e. it > still has the line: > >    01:00.0 > >    > Ã*  Ã*  Ã* VGA compatible controller: nVidia Corporation > G96 [GeForce GT > >    130M] (rev > >    > Ã*  Ã*  Ã* a1)). > >    > Ã*  Ã*  Ã* Using xm pci-detach still gives the same error > as well (Error: > >    Cannot > >    > Ã*  Ã*  Ã* detach when pci platform does not exist) > >    > Ã*  Ã*  Ã* Kai > >    > Ã*  Ã*  Ã* _______________________________________________ > >    > Ã*  Ã*  Ã* Xen-users mailing list > >    > Ã*  Ã*  Ã* [2][3][4]Xen-users@lists.xensource.com > >    > Ã*  Ã*  Ã* [3][4][5]http://lists.xensource.com/xen-users > >    > > >    > References > >    > > >    > Ã*  Ã* Visible links > >    > Ã*  Ã* 1. mailto:[5][6]kjw53@cam.ac.uk > >    > Ã*  Ã* 2. mailto:[6][7]Xen-users@lists.xensource.com > >    > Ã*  Ã* 3. [7][8]http://lists.xensource.com/xen-users > >    > _______________________________________________ > >    > Xen-users mailing list > >    > [8][9]Xen-users@lists.xensource.com > >    > [9][10]http://lists.xensource.com/xen-users > > > >    _______________________________________________ > >    Xen-users mailing list > >    [10][11]Xen-users@lists.xensource.com > >    [11][12]http://lists.xensource.com/xen-users > > > > References > > > >   Visible links > >   1. mailto:[13]pasik@iki.fi > >   2. mailto:[14]kjw53@cam.ac.uk > >   3. mailto:[15]Xen-users@lists.xensource.com > >   4. [16]http://lists.xensource.com/xen-users > >   5. mailto:[17]kjw53@cam.ac.uk > >   6. mailto:[18]Xen-users@lists.xensource.com > >   7. [19]http://lists.xensource.com/xen-users > >   8. mailto:[20]Xen-users@lists.xensource.com > >   9. [21]http://lists.xensource.com/xen-users > >  10. mailto:[22]Xen-users@lists.xensource.com > >  11. [23]http://lists.xensource.com/xen-users > _______________________________________________ > Xen-users mailing list > [24]Xen-users@lists.xensource.com > [25]http://lists.xensource.com/xen-users > > References > > Visible links > 1. mailto:pasik@iki.fi > 2. mailto:pasik@iki.fi > 3. mailto:kjw53@cam.ac.uk > 4. mailto:Xen-users@lists.xensource.com > 5. http://lists.xensource.com/xen-users > 6. mailto:kjw53@cam.ac.uk > 7. mailto:Xen-users@lists.xensource.com > 8. http://lists.xensource.com/xen-users > 9. mailto:Xen-users@lists.xensource.com > 10. http://lists.xensource.com/xen-users > 11. mailto:Xen-users@lists.xensource.com > 12. http://lists.xensource.com/xen-users > 13. mailto:pasik@iki.fi > 14. mailto:kjw53@cam.ac.uk > 15. mailto:Xen-users@lists.xensource.com > 16. http://lists.xensource.com/xen-users > 17. mailto:kjw53@cam.ac.uk > 18. mailto:Xen-users@lists.xensource.com > 19. http://lists.xensource.com/xen-users > 20. mailto:Xen-users@lists.xensource.com > 21. http://lists.xensource.com/xen-users > 22. mailto:Xen-users@lists.xensource.com > 23. http://lists.xensource.com/xen-users > 24. mailto:Xen-users@lists.xensource.com > 25. http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for your help, Pasi. I feel like an idiot. As I said, I bought this hardware just to do Xen. In addition to some expensive graphic cards and such... But I found very little info around the net regarding chipset doing VT-d. And most of the info I found, was a couple of years old. So I just thought that most of the recent motherboards/chipsets was doing this these days... Damn. :\ Sorry for taking up your time to no use. But thanks a lot for helping me figure this out. Now I just have to go earn some more money so I can buy a new motherboard with the specifications I hope to find. :\ Greetings from Norway, Jørn On Tue, Jan 19, 2010 at 9:58 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Tue, Jan 19, 2010 at 09:46:26PM +0100, Jørn Odberg wrote: > > Full xm dmesg output: > > > >  __ __           _____ _ _   ____ > >  \ \/ /___ _ __  |___ /| || | |___ \ > >  \ // _ \ ''_ \   |_ \| || |_  __) | > >  / \ __/ | | | ___) |__  _| / __/ > >  /_/\_\___|_| |_| |____(_) |_|(_)_____| > >                                    >    > > (XEN) Xen version 3.4.2 (root@) (gcc version 4.3.4 (Gentoo 4.3.4 > p1.0, > > pie-10.1.5) ) Fri Jan 15 10:45:24 CET 2010 > > (XEN) Latest ChangeSet: unavailable > > (XEN) Command line: iommu=1 vtd=1 > > (XEN) Video information: > > (XEN) VGA is text mode 80x25, font 8x16 > > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > > (XEN) Disc information: > > (XEN) Found 2 MBR signatures > > (XEN) Found 2 EDD information structures > > (XEN) Xen-e820 RAM map: > > (XEN) 0000000000000000 - 000000000009cc00 (usable) > > (XEN) 000000000009cc00 - 00000000000a0000 (reserved) > > (XEN) 00000000000e4000 - 0000000000100000 (reserved) > > (XEN) 0000000000100000 - 00000000bff70000 (usable) > > (XEN) 00000000bff70000 - 00000000bff7e000 (ACPI data) > > (XEN) 00000000bff7e000 - 00000000bffd0000 (ACPI NVS) > > (XEN) 00000000bffd0000 - 00000000c0000000 (reserved) > > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > > (XEN) 00000000ffe00000 - 0000000100000000 (reserved) > > (XEN) 0000000100000000 - 0000000140000000 (usable) > > (XEN) System RAM: 4095MB (4193328kB) > > (XEN) ACPI: RSDP 000FB280, 0014 (r0 ACPIAM) > > (XEN) ACPI: RSDT BFF70000, 0044 (r1 A_M_I_ OEMRSDT  5000922 > > MSFT      97) > > (XEN) ACPI: FACP BFF70200, 0084 (r2 A_M_I_ OEMFACP  5000922 > > MSFT      97) > > (XEN) ACPI: DSDT BFF70440, 9EBF (r1 A1039 A1039001       1 > INTL > > 20060113) > > (XEN) ACPI: FACS BFF7E000, 0040 > > (XEN) ACPI: APIC BFF70390, 006C (r1 A_M_I_ OEMAPIC  5000922 > > MSFT      97) > > (XEN) ACPI: MCFG BFF70400, 003C (r1 A_M_I_ OEMMCFG  5000922 > > MSFT      97) > > (XEN) ACPI: OEMB BFF7E040, 0089 (r1 A_M_I_ AMI_OEM  5000922 > > MSFT      97) > > (XEN) ACPI: HPET BFF7A300, 0038 (r1 A_M_I_ OEMHPET  5000922 > > MSFT      97) > > (XEN) ACPI: OSFR BFF7A340, 00B0 (r1 A_M_I_ OEMOSFR  5000922 > > MSFT      97) > > (XEN) ACPI: TCPA BFF7A3F0, 0032 (r1 A_M_I_ TBLOEMID       1 > > MSFT      97) > > (XEN) ACPI: SSDT BFF91A70, 0A7C (r1 DpgPmm   CpuPm      12 > INTL > > 20060113) > > (XEN) Domain heap initialised > > (XEN) Processor #0 7:7 APIC version 20 > > (XEN) Processor #1 7:7 APIC version 20 > > (XEN) Processor #2 7:7 APIC version 20 > > (XEN) Processor #3 7:7 APIC version 20 > > (XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23 > > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > > (XEN) XSM Framework v1.0.0 initialized > > (XEN) Using scheduler: SMP Credit Scheduler (credit) > > (XEN) Detected 2666.422 MHz processor. > > (XEN) VMX: Supported advanced features: > > (XEN) - APIC MMIO access virtualisation > > (XEN) - APIC TPR shadow > > (XEN) - Virtual NMI > > (XEN) - MSR direct-access bitmap > > (XEN) HVM: VMX enabled > > (XEN) CPU0: Intel(R) Core(TM)2 Quad CPU   Q9400 @ 2.66GHz > stepping > > 0a > > (XEN) Booting processor 1/1 eip 8c000 > > (XEN) CPU1: Intel(R) Core(TM)2 Quad CPU   Q9400 @ 2.66GHz > stepping > > 0a > > (XEN) Booting processor 2/2 eip 8c000 > > (XEN) CPU2: Intel(R) Core(TM)2 Quad CPU   Q9400 @ 2.66GHz > stepping > > 0a > > (XEN) Booting processor 3/3 eip 8c000 > > (XEN) CPU3: Intel(R) Core(TM)2 Quad CPU   Q9400 @ 2.66GHz > stepping > > 0a > > (XEN) Total of 4 processors activated. > > (XEN) ENABLING IO-APIC IRQs > > (XEN) -> Using new ACK method > > (XEN) checking TSC synchronization across 4 CPUs: passed. > > (XEN) Platform timer is 14.318MHz HPET > > (XEN) Brought up 4 CPUs > > (XEN) I/O virtualisation disabled > > (XEN) *** LOADING DOMAIN 0 *** > > (XEN) Xen kernel: 64-bit, lsb, compat32 > > (XEN) Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x7e6000 > > (XEN) PHYSICAL MEMORY ARRANGEMENT: > > (XEN) Dom0 alloc.:  000000013b000000->000000013c000000 (996433 > pages > > to be allocated) > > (XEN) VIRTUAL MEMORY ARRANGEMENT: > > (XEN) Loaded kernel: ffffffff80200000->ffffffff807e6000 > > (XEN) Init. ramdisk: ffffffff807e6000->ffffffff807e6000 > > (XEN) Phys-Mach map: ffffea0000000000->ffffea00007a2288 > > (XEN) Start info:   ffffffff807e6000->ffffffff807e64b4 > > (XEN) Page tables:  ffffffff807e7000->ffffffff807f0000 > > (XEN) Boot stack:   ffffffff807f0000->ffffffff807f1000 > > (XEN) TOTAL:        ffffffff80000000->ffffffff80c00000 > > (XEN) ENTRY ADDRESS: ffffffff80200000 > > (XEN) Dom0 has maximum 4 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 136kB init memory. > > (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > > (XEN) CPU 0 initialization completed > > (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > > (XEN) CPU 1 initialization completed > > (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > > (XEN) CPU 2 initialization completed > > (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > > (XEN) CPU 3 initialization completed > > > > In the BIOS I could only find "Intel(R) Virtualization Tech    - > > Enabled" , but no setting for VT-d... damn... DAMN! Does that mean I''m > > screwed?!? I bought this motherboard and cpu just to do Xen. > > > > Motherboard: ASUS P5Q Premium, P45, Socket-775. > > CPU: Intel Core 2 Quad Q9400. (Has "Intel Virtualization Technology") > > > > I was under the impression the Intel P45 chipset had "VT-d" ? ... :\ > > > > Am I screwed, or is it only me who screws something up? ;) > > > > Looks bad.. nothing about ACPI DMAR in the log, which is used by VT-d > IOMMU.. > It looks like your chipset/BIOS doesn''t support VT-d. > > This wiki page lists some motherboards/chipsets with IOMMU (VT-d): > http://wiki.xensource.com/xenwiki/VTdHowTo > > I don''t see P45 there.. does Asus claim it supports VT-d ? > > -- Pasi > > > // JÞrn > > > > On Tue, Jan 19, 2010 at 9:35 PM, Pasi KÀrkkÀinen <[1]pasik@iki.fi> > > wrote: > > > > On Tue, Jan 19, 2010 at 09:31:27PM +0100, JÞrn Odberg wrote: > > >   Hello, and thanks for the reply. > > > > > >   I''ve added this to my grub (it may be redundant, but I got > > different > > >   advices, so I added them all;): > > > > > >   title Xen / Gentoo Linux 2.6.31-xen-r10 IOMMU > > >   root (hd0,0) > > >   kernel /boot/xen.gz iommu=1 vtd=1 > > >   module /boot/vmlinuz-2.6.31-xen-r10 root=/dev/md2 > > pciback.permissive > > > > Oh, it looks like you''re not using pv_ops dom0 kernel, but gentoo > kernel > > with > > xenlinux patches from opensuse. > > > > Then you can forget my xen-pciback comment. > > >   xen-pciback.hide=(01:00.0)(08:00.0)(09:00.0) > > >   pciback.hide=(01:00.0)(08:00.0)(09:00.0) > > guestdev=01:00.0,08:00.0,09:00.0 > > >   reassign_resources console=tty0 > > > > > >   And I have installed Xen 3.4.2-r1. > > > > > >   xm dmesg , shows: > > >   (XEN) Command line: iommu=1 vtd=1 > > >   (XEN) VMX: Supported advanced features: > > >   (XEN)Ã*  - APIC MMIO access virtualisation > > >   (XEN)Ã*  - APIC TPR shadow > > >   (XEN)Ã*  - Virtual NMI > > >   (XEN)Ã*  - MSR direct-access bitmap > > >   (XEN) HVM: VMX enabled > > >   (XEN) I/O virtualisation disabled > > > > > > > Please paste the full "xm dmesg", that doesn''t show why it''s > disabled in > > Xen hypervisor. > > > > Did you enable VT-d in BIOS? > > > > -- Pasi > > > > >   // JÃ*ÅŸrn > > > > > >   On Tue, Jan 19, 2010 at 7:19 PM, Pasi KÃ*â*¬rkkÃ*â*¬inen > > <[1][2]pasik@iki.fi> > > >   wrote: > > > > > >    On Tue, Jan 19, 2010 at 02:49:52PM +0100, JÃ*ÅŸrn Odberg > > wrote: > > >    > Ã*  Ã* Hello. > > >    > > > >    > Ã*  Ã* I have this exact same problem myself. > > >    > > > >    > Ã*  Ã* (I have four onboard gigabit network cards, pci > > 05:00.0, 06:00.0, > > >    07:00.0 > > >    > Ã*  Ã* and 08:00.0) > > >    > Ã*  Ã* I tried using pciback.hide=(06:00.0)(07:00.0) . > And > > in dom0, I > > >    now get: > > >    > > > > > > >    In the recent pv_ops dom0 kernels pciback module is now > called > > >    xen-pciback, > > >    so you need to change that to xen-pciback.hide. > > > > > >    -- Pasi > > >    > Ã*  Ã* xen ~ # ifconfig eth1 > > >    > Ã*  Ã* eth1: error fetching interface information: > Device > > not found > > >    > > > >    > Ã*  Ã* And the same for eth2. So it apparently got > > "hidden", or > > >    detached. > > >    > > > >    > Ã*  Ã* But the command "xm pci-list-assignable-devices" > > doesn''t return > > >    anything. > > >    > Ã*  Ã* And when trying "xm pci-detach", I get the same > > error as you > > >    (Cannot > > >    > Ã*  Ã* detach when pci platform does not exist). Even > > though I''ve > > >    compiled in all > > >    > Ã*  Ã* the support I can think of in the kernel. > > >    > > > >    > Ã*  Ã* Running: > > >    > Ã*  Ã* Gentoo 2.6.31-xen-r10 > > >    > Ã*  Ã* xen-3.4.2-r1 > > >    > > > >    > Ã*  Ã* // JÃ**Ã*Åžrn > > >    > > > >    > Ã*  Ã* On Mon, Dec 21, 2009 at 10:22 PM, Kai Wohlfahrt > > >    <[1][2][3]kjw53@cam.ac.uk> > > >    > Ã*  Ã* wrote: > > >    > > > >    > Ã*  Ã*  Ã* Still no luck with that. My grub entry > looks > > like so: > > >    > > > >    > Ã*  Ã*  Ã*  Ã*  Ã* menuentry "Xen-Unstable / Kubuntu > > 9.10 kernel 2.6.31.6 > > >    pvops" { > > >    > > > >    > Ã*  Ã*  Ã*  Ã*  Ã* insmod ext2 > > >    > > > >    > Ã*  Ã*  Ã*  Ã*  Ã* set root=(hd0,1) > > >    > > > >    > Ã*  Ã*  Ã*  Ã*  Ã* multiboot (hd0,1)/boot/xen.gz > > dom0_mem=1048M iommu=force > > >    > > > >    > Ã*  Ã*  Ã*  Ã*  Ã* module > > (hd0,1)/boot/vmlinuz-2.6.31.6-xen > > >    xen-pciback.hide=(01:00.0) > > >    > > > >    > Ã*  Ã*  Ã*  Ã*  Ã* module > > (hd0,1)/boot/initrd.img-2.6.31.6-xen > > >    > > > >    > Ã*  Ã*  Ã*  Ã*  Ã* } > > >    > > > >    > Ã*  Ã*  Ã* but my lspci still looks the same (i.e. it > > still has the line: > > >    01:00.0 > > >    > Ã*  Ã*  Ã* VGA compatible controller: nVidia > Corporation > > G96 [GeForce GT > > >    130M] (rev > > >    > Ã*  Ã*  Ã* a1)). > > >    > Ã*  Ã*  Ã* Using xm pci-detach still gives the same > error > > as well (Error: > > >    Cannot > > >    > Ã*  Ã*  Ã* detach when pci platform does not exist) > > >    > Ã*  Ã*  Ã* Kai > > >    > Ã*  Ã*  Ã* > _______________________________________________ > > >    > Ã*  Ã*  Ã* Xen-users mailing list > > >    > Ã*  Ã*  Ã* [2][3][4]Xen-users@lists.xensource.com > > >    > Ã*  Ã*  Ã* [3][4][5] > http://lists.xensource.com/xen-users > > >    > > > >    > References > > >    > > > >    > Ã*  Ã* Visible links > > >    > Ã*  Ã* 1. mailto:[5][6]kjw53@cam.ac.uk > > >    > Ã*  Ã* 2. mailto:[6][7]Xen-users@lists.xensource.com > > >    > Ã*  Ã* 3. [7][8]http://lists.xensource.com/xen-users > > >    > _______________________________________________ > > >    > Xen-users mailing list > > >    > [8][9]Xen-users@lists.xensource.com > > >    > [9][10]http://lists.xensource.com/xen-users > > > > > >    _______________________________________________ > > >    Xen-users mailing list > > >    [10][11]Xen-users@lists.xensource.com > > >    [11][12]http://lists.xensource.com/xen-users > > > > > > References > > > > > >   Visible links > > >   1. mailto:[13]pasik@iki.fi > > >   2. mailto:[14]kjw53@cam.ac.uk > > >   3. mailto:[15]Xen-users@lists.xensource.com > > >   4. [16]http://lists.xensource.com/xen-users > > >   5. mailto:[17]kjw53@cam.ac.uk > > >   6. mailto:[18]Xen-users@lists.xensource.com > > >   7. [19]http://lists.xensource.com/xen-users > > >   8. mailto:[20]Xen-users@lists.xensource.com > > >   9. [21]http://lists.xensource.com/xen-users > > >  10. mailto:[22]Xen-users@lists.xensource.com > > >  11. [23]http://lists.xensource.com/xen-users > > _______________________________________________ > > Xen-users mailing list > > [24]Xen-users@lists.xensource.com > > [25]http://lists.xensource.com/xen-users > > > > References > > > > Visible links > > 1. mailto:pasik@iki.fi > > 2. mailto:pasik@iki.fi > > 3. mailto:kjw53@cam.ac.uk > > 4. mailto:Xen-users@lists.xensource.com > > 5. http://lists.xensource.com/xen-users > > 6. mailto:kjw53@cam.ac.uk > > 7. mailto:Xen-users@lists.xensource.com > > 8. http://lists.xensource.com/xen-users > > 9. mailto:Xen-users@lists.xensource.com > > 10. http://lists.xensource.com/xen-users > > 11. mailto:Xen-users@lists.xensource.com > > 12. http://lists.xensource.com/xen-users > > 13. mailto:pasik@iki.fi > > 14. mailto:kjw53@cam.ac.uk > > 15. mailto:Xen-users@lists.xensource.com > > 16. http://lists.xensource.com/xen-users > > 17. mailto:kjw53@cam.ac.uk > > 18. mailto:Xen-users@lists.xensource.com > > 19. http://lists.xensource.com/xen-users > > 20. mailto:Xen-users@lists.xensource.com > > 21. http://lists.xensource.com/xen-users > > 22. mailto:Xen-users@lists.xensource.com > > 23. http://lists.xensource.com/xen-users > > 24. mailto:Xen-users@lists.xensource.com > > 25. http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jan 19, 2010 at 10:06:58PM +0100, Jørn Odberg wrote:> Thanks for your help, Pasi. > > I feel like an idiot. As I said, I bought this hardware just to do Xen. In > addition to some expensive graphic cards and such... > But I found very little info around the net regarding chipset doing VT-d. > And most of the info I found, was a couple of years old. So I just thought > that most of the recent motherboards/chipsets was doing this these days... > > Damn. :\ > > Sorry for taking up your time to no use. But thanks a lot for helping me > figure this out. Now I just have to go earn some more money so I can buy a > new motherboard with the specifications I hope to find. :\ >Yeah.. it''s a bit difficult atm. Also many of the consumer motherboards seem to have buggy BIOSes regarding VT-d support.. so even if your motherboard has VT-d support, it doesn''t mean it actually works :) Asus is known to have multiple motherboard models with broken BIOS.. (they have wrong memory ranges in the VT-d DMAR tables). When you get a new motherboard make sure to browse through xen-users and/or xen-devel archives and see what motherboards people have been successfully using..> Greetings from Norway, > JÞrn >Greetings from Finland :) -- Pasi> > On Tue, Jan 19, 2010 at 9:58 PM, Pasi KÀrkkÀinen <[1]pasik@iki.fi> > wrote: > > On Tue, Jan 19, 2010 at 09:46:26PM +0100, JÞrn Odberg wrote: > >   Full xm dmesg output: > > > >   Ã* __Ã*  __Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã*  _____ _Ã*  _Ã* Ã* > Ã*  ____Ã* > >   Ã* \ \/ /___ _ __Ã* Ã*  |___ /| || |Ã*  |___ \ > >   Ã*  \Ã*  // _ \ ''_ \Ã* Ã* Ã*  |_ \| || |_Ã* Ã*  __) | > >   Ã*  /Ã*  \Ã*  __/ | | |Ã*  ___) |__Ã* Ã*  _| / __/ > >   Ã* /_/\_\___|_| |_| |____(_) |_|(_)_____| > >   Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* > Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* > >   (XEN) Xen version 3.4.2 (root@) (gcc version 4.3.4 (Gentoo 4.3.4 > p1.0, > >   pie-10.1.5) ) Fri Jan 15 10:45:24 CET 2010 > >   (XEN) Latest ChangeSet: unavailable > >   (XEN) Command line: iommu=1 vtd=1 > >   (XEN) Video information: > >   (XEN)Ã*  VGA is text mode 80x25, font 8x16 > >   (XEN)Ã*  VBE/DDC methods: V2; EDID transfer time: 1 seconds > >   (XEN) Disc information: > >   (XEN)Ã*  Found 2 MBR signatures > >   (XEN)Ã*  Found 2 EDD information structures > >   (XEN) Xen-e820 RAM map: > >   (XEN)Ã*  0000000000000000 - 000000000009cc00 (usable) > >   (XEN)Ã*  000000000009cc00 - 00000000000a0000 (reserved) > >   (XEN)Ã*  00000000000e4000 - 0000000000100000 (reserved) > >   (XEN)Ã*  0000000000100000 - 00000000bff70000 (usable) > >   (XEN)Ã*  00000000bff70000 - 00000000bff7e000 (ACPI data) > >   (XEN)Ã*  00000000bff7e000 - 00000000bffd0000 (ACPI NVS) > >   (XEN)Ã*  00000000bffd0000 - 00000000c0000000 (reserved) > >   (XEN)Ã*  00000000fee00000 - 00000000fee01000 (reserved) > >   (XEN)Ã*  00000000ffe00000 - 0000000100000000 (reserved) > >   (XEN)Ã*  0000000100000000 - 0000000140000000 (usable) > >   (XEN) System RAM: 4095MB (4193328kB) > >   (XEN) ACPI: RSDP 000FB280, 0014 (r0 ACPIAM) > >   (XEN) ACPI: RSDT BFF70000, 0044 (r1 A_M_I_ OEMRSDTÃ* Ã*  5000922 > >   MSFTÃ* Ã* Ã* Ã* Ã* Ã*  97) > >   (XEN) ACPI: FACP BFF70200, 0084 (r2 A_M_I_ OEMFACPÃ* Ã*  5000922 > >   MSFTÃ* Ã* Ã* Ã* Ã* Ã*  97) > >   (XEN) ACPI: DSDT BFF70440, 9EBF (r1Ã*  A1039 A1039001Ã* Ã* Ã* Ã* > Ã* Ã* Ã*  1 INTL > >   20060113) > >   (XEN) ACPI: FACS BFF7E000, 0040 > >   (XEN) ACPI: APIC BFF70390, 006C (r1 A_M_I_ OEMAPICÃ* Ã*  5000922 > >   MSFTÃ* Ã* Ã* Ã* Ã* Ã*  97) > >   (XEN) ACPI: MCFG BFF70400, 003C (r1 A_M_I_ OEMMCFGÃ* Ã*  5000922 > >   MSFTÃ* Ã* Ã* Ã* Ã* Ã*  97) > >   (XEN) ACPI: OEMB BFF7E040, 0089 (r1 A_M_I_ AMI_OEMÃ* Ã*  5000922 > >   MSFTÃ* Ã* Ã* Ã* Ã* Ã*  97) > >   (XEN) ACPI: HPET BFF7A300, 0038 (r1 A_M_I_ OEMHPETÃ* Ã*  5000922 > >   MSFTÃ* Ã* Ã* Ã* Ã* Ã*  97) > >   (XEN) ACPI: OSFR BFF7A340, 00B0 (r1 A_M_I_ OEMOSFRÃ* Ã*  5000922 > >   MSFTÃ* Ã* Ã* Ã* Ã* Ã*  97) > >   (XEN) ACPI: TCPA BFF7A3F0, 0032 (r1 A_M_I_ TBLOEMIDÃ* Ã* Ã* Ã* Ã* > Ã* Ã*  1 > >   MSFTÃ* Ã* Ã* Ã* Ã* Ã*  97) > >   (XEN) ACPI: SSDT BFF91A70, 0A7C (r1 DpgPmmÃ* Ã* Ã*  CpuPmÃ* Ã* > Ã* Ã* Ã* Ã*  12 INTL > >   20060113) > >   (XEN) Domain heap initialised > >   (XEN) Processor #0 7:7 APIC version 20 > >   (XEN) Processor #1 7:7 APIC version 20 > >   (XEN) Processor #2 7:7 APIC version 20 > >   (XEN) Processor #3 7:7 APIC version 20 > >   (XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI > 0-23 > >   (XEN) Enabling APIC mode:Ã*  Flat.Ã*  Using 1 I/O APICs > >   (XEN) XSM Framework v1.0.0 initialized > >   (XEN) Using scheduler: SMP Credit Scheduler (credit) > >   (XEN) Detected 2666.422 MHz processor. > >   (XEN) VMX: Supported advanced features: > >   (XEN)Ã*  - APIC MMIO access virtualisation > >   (XEN)Ã*  - APIC TPR shadow > >   (XEN)Ã*  - Virtual NMI > >   (XEN)Ã*  - MSR direct-access bitmap > >   (XEN) HVM: VMX enabled > >   (XEN) CPU0: Intel(R) Core(TM)2 Quad CPUÃ* Ã* Ã*  Q9400Ã*  @ > 2.66GHz stepping > >   0a > >   (XEN) Booting processor 1/1 eip 8c000 > >   (XEN) CPU1: Intel(R) Core(TM)2 Quad CPUÃ* Ã* Ã*  Q9400Ã*  @ > 2.66GHz stepping > >   0a > >   (XEN) Booting processor 2/2 eip 8c000 > >   (XEN) CPU2: Intel(R) Core(TM)2 Quad CPUÃ* Ã* Ã*  Q9400Ã*  @ > 2.66GHz stepping > >   0a > >   (XEN) Booting processor 3/3 eip 8c000 > >   (XEN) CPU3: Intel(R) Core(TM)2 Quad CPUÃ* Ã* Ã*  Q9400Ã*  @ > 2.66GHz stepping > >   0a > >   (XEN) Total of 4 processors activated. > >   (XEN) ENABLING IO-APIC IRQs > >   (XEN)Ã*  -> Using new ACK method > >   (XEN) checking TSC synchronization across 4 CPUs: passed. > >   (XEN) Platform timer is 14.318MHz HPET > >   (XEN) Brought up 4 CPUs > >   (XEN) I/O virtualisation disabled > >   (XEN) *** LOADING DOMAIN 0 *** > >   (XEN)Ã*  XenÃ*  kernel: 64-bit, lsb, compat32 > >   (XEN)Ã*  Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x7e6000 > >   (XEN) PHYSICAL MEMORY ARRANGEMENT: > >   (XEN)Ã*  Dom0 alloc.:Ã* Ã*  000000013b000000->000000013c000000 > (996433 pages > >   to be allocated) > >   (XEN) VIRTUAL MEMORY ARRANGEMENT: > >   (XEN)Ã*  Loaded kernel: ffffffff80200000->ffffffff807e6000 > >   (XEN)Ã*  Init. ramdisk: ffffffff807e6000->ffffffff807e6000 > >   (XEN)Ã*  Phys-Mach map: ffffea0000000000->ffffea00007a2288 > >   (XEN)Ã*  Start info:Ã* Ã* Ã* >  ffffffff807e6000->ffffffff807e64b4 > >   (XEN)Ã*  Page tables:Ã* Ã*  ffffffff807e7000->ffffffff807f0000 > >   (XEN)Ã*  Boot stack:Ã* Ã* Ã* >  ffffffff807f0000->ffffffff807f1000 > >   (XEN)Ã*  TOTAL:Ã* Ã* Ã* Ã* Ã* Ã* Ã* Ã* >  ffffffff80000000->ffffffff80c00000 > >   (XEN)Ã*  ENTRY ADDRESS: ffffffff80200000 > >   (XEN) Dom0 has maximum 4 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 136kB init memory. > >   (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > >   (XEN) CPU 0 initialization completed > >   (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > >   (XEN) CPU 1 initialization completed > >   (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > >   (XEN) CPU 2 initialization completed > >   (XEN) xen_pminfo: @acpi_cpufreq_cpu_init,HARDWARE addr space > >   (XEN) CPU 3 initialization completed > > > >   In the BIOS I could only find "Intel(R) Virtualization Tech Ã* Ã* > Ã*  - > >   Enabled" , but no setting for VT-d... damn... DAMN! Does that > mean I''m > >   screwed?!? I bought this motherboard and cpu just to do Xen. > > > >   Motherboard: ASUS P5Q Premium, P45, Socket-775. > >   CPU: Intel Core 2 Quad Q9400. (Has "Intel Virtualization > Technology") > > > >   I was under the impression the Intel P45 chipset had "VT-d" ? ... > :\ > > > >   Am I screwed, or is it only me who screws something up? ;) > > > > Looks bad.. nothing about ACPI DMAR in the log, which is used by VT-d > IOMMU.. > It looks like your chipset/BIOS doesn''t support VT-d. > > This wiki page lists some motherboards/chipsets with IOMMU (VT-d): > [2]http://wiki.xensource.com/xenwiki/VTdHowTo > > I don''t see P45 there.. does Asus claim it supports VT-d ? > > -- Pasi > > >   // JÃ*ÅŸrn > > > >   On Tue, Jan 19, 2010 at 9:35 PM, Pasi KÃ*â*¬rkkÃ*â*¬inen > <[1][3]pasik@iki.fi> > >   wrote: > > > >    On Tue, Jan 19, 2010 at 09:31:27PM +0100, JÃ*ÅŸrn Odberg > wrote: > >    > Ã*  Ã* Hello, and thanks for the reply. > >    > > >    > Ã*  Ã* I''ve added this to my grub (it may be redundant, but > I got > >    different > >    > Ã*  Ã* advices, so I added them all;): > >    > > >    > Ã*  Ã* title Xen / Gentoo Linux 2.6.31-xen-r10 IOMMU > >    > Ã*  Ã* root (hd0,0) > >    > Ã*  Ã* kernel /boot/xen.gz iommu=1 vtd=1 > >    > Ã*  Ã* module /boot/vmlinuz-2.6.31-xen-r10 root=/dev/md2 > >    pciback.permissive > > > >    Oh, it looks like you''re not using pv_ops dom0 kernel, but > gentoo kernel > >    with > >    xenlinux patches from opensuse. > > > >    Then you can forget my xen-pciback comment. > >    > Ã*  Ã* xen-pciback.hide=(01:00.0)(08:00.0)(09:00.0) > >    > Ã*  Ã* pciback.hide=(01:00.0)(08:00.0)(09:00.0) > >    guestdev=01:00.0,08:00.0,09:00.0 > >    > Ã*  Ã* reassign_resources console=tty0 > >    > > >    > Ã*  Ã* And I have installed Xen 3.4.2-r1. > >    > > >    > Ã*  Ã* xm dmesg , shows: > >    > Ã*  Ã* (XEN) Command line: iommu=1 vtd=1 > >    > Ã*  Ã* (XEN) VMX: Supported advanced features: > >    > Ã*  Ã* (XEN)Ã** Ã* - APIC MMIO access virtualisation > >    > Ã*  Ã* (XEN)Ã** Ã* - APIC TPR shadow > >    > Ã*  Ã* (XEN)Ã** Ã* - Virtual NMI > >    > Ã*  Ã* (XEN)Ã** Ã* - MSR direct-access bitmap > >    > Ã*  Ã* (XEN) HVM: VMX enabled > >    > Ã*  Ã* (XEN) I/O virtualisation disabled > >    > > > > >    Please paste the full "xm dmesg", that doesn''t show why it''s > disabled in > >    Xen hypervisor. > > > >    Did you enable VT-d in BIOS? > > > >    -- Pasi > > > >    > Ã*  Ã* // JÃ**Ã*Åžrn > >    > > >    > Ã*  Ã* On Tue, Jan 19, 2010 at 7:19 PM, Pasi > KÃ**â*¬rkkÃ**â*¬inen > >    <[1][2][4]pasik@iki.fi> > >    > Ã*  Ã* wrote: > >    > > >    > Ã*  Ã*  Ã* On Tue, Jan 19, 2010 at 02:49:52PM +0100, > JÃ**Ã*Åžrn Odberg > >    wrote: > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Hello. > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** I have this exact same problem > myself. > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** (I have four onboard gigabit > network cards, pci > >    05:00.0, 06:00.0, > >    > Ã*  Ã*  Ã* 07:00.0 > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** and 08:00.0) > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** I tried using > pciback.hide=(06:00.0)(07:00.0) . And > >    in dom0, I > >    > Ã*  Ã*  Ã* now get: > >    > Ã*  Ã*  Ã* > > >    > > >    > Ã*  Ã*  Ã* In the recent pv_ops dom0 kernels pciback > module is now called > >    > Ã*  Ã*  Ã* xen-pciback, > >    > Ã*  Ã*  Ã* so you need to change that to xen-pciback.hide. > >    > > >    > Ã*  Ã*  Ã* -- Pasi > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** xen ~ # ifconfig eth1 > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** eth1: error fetching interface > information: Device > >    not found > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** And the same for eth2. So it > apparently got > >    "hidden", or > >    > Ã*  Ã*  Ã* detached. > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** But the command "xm > pci-list-assignable-devices" > >    doesn''t return > >    > Ã*  Ã*  Ã* anything. > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** And when trying "xm pci-detach", I > get the same > >    error as you > >    > Ã*  Ã*  Ã* (Cannot > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** detach when pci platform does not > exist). Even > >    though I''ve > >    > Ã*  Ã*  Ã* compiled in all > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** the support I can think of in the > kernel. > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Running: > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Gentoo 2.6.31-xen-r10 > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** xen-3.4.2-r1 > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** // JÃ***Ã**Ã*ÅŸrn > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** On Mon, Dec 21, 2009 at 10:22 PM, > Kai Wohlfahrt > >    > Ã*  Ã*  Ã* <[1][2][3][5]kjw53@cam.ac.uk> > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** wrote: > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** Still no luck with that. My > grub entry looks > >    like so: > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** Ã* Ã** Ã* Ã** menuentry > "Xen-Unstable / Kubuntu > >    9.10 kernel 2.6.31.6 > >    > Ã*  Ã*  Ã* pvops" { > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** Ã* Ã** Ã* Ã** insmod ext2 > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** Ã* Ã** Ã* Ã** set > root=(hd0,1) > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** Ã* Ã** Ã* Ã** multiboot > (hd0,1)/boot/xen.gz > >    dom0_mem=1048M iommu=force > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** Ã* Ã** Ã* Ã** module > >    (hd0,1)/boot/vmlinuz-2.6.31.6-xen > >    > Ã*  Ã*  Ã* xen-pciback.hide=(01:00.0) > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** Ã* Ã** Ã* Ã** module > >    (hd0,1)/boot/initrd.img-2.6.31.6-xen > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** Ã* Ã** Ã* Ã** } > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** but my lspci still looks > the same (i.e. it > >    still has the line: > >    > Ã*  Ã*  Ã* 01:00.0 > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** VGA compatible controller: > nVidia Corporation > >    G96 [GeForce GT > >    > Ã*  Ã*  Ã* 130M] (rev > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** a1)). > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** Using xm pci-detach still > gives the same error > >    as well (Error: > >    > Ã*  Ã*  Ã* Cannot > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** detach when pci platform > does not exist) > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** Kai > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** > _______________________________________________ > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** Xen-users mailing list > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** > [2][3][4][6]Xen-users@lists.xensource.com > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Ã* Ã** > [3][4][5][7]http://lists.xensource.com/xen-users > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > References > >    > Ã*  Ã*  Ã* > > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** Visible links > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** 1. mailto:[5][6][8]kjw53@cam.ac.uk > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** 2. > mailto:[6][7][9]Xen-users@lists.xensource.com > >    > Ã*  Ã*  Ã* > Ã** Ã* Ã** 3. > [7][8][10]http://lists.xensource.com/xen-users > >    > Ã*  Ã*  Ã* > > _______________________________________________ > >    > Ã*  Ã*  Ã* > Xen-users mailing list > >    > Ã*  Ã*  Ã* > [8][9][11]Xen-users@lists.xensource.com > >    > Ã*  Ã*  Ã* > > [9][10][12]http://lists.xensource.com/xen-users > >    > > >    > Ã*  Ã*  Ã* _______________________________________________ > >    > Ã*  Ã*  Ã* Xen-users mailing list > >    > Ã*  Ã*  Ã* [10][11][13]Xen-users@lists.xensource.com > >    > Ã*  Ã*  Ã* > [11][12][14]http://lists.xensource.com/xen-users > >    > > >    > References > >    > > >    > Ã*  Ã* Visible links > >    > Ã*  Ã* 1. mailto:[13][15]pasik@iki.fi > >    > Ã*  Ã* 2. mailto:[14][16]kjw53@cam.ac.uk > >    > Ã*  Ã* 3. mailto:[15][17]Xen-users@lists.xensource.com > >    > Ã*  Ã* 4. [16][18]http://lists.xensource.com/xen-users > >    > Ã*  Ã* 5. mailto:[17][19]kjw53@cam.ac.uk > >    > Ã*  Ã* 6. mailto:[18][20]Xen-users@lists.xensource.com > >    > Ã*  Ã* 7. [19][21]http://lists.xensource.com/xen-users > >    > Ã*  Ã* 8. mailto:[20][22]Xen-users@lists.xensource.com > >    > Ã*  Ã* 9. [21][23]http://lists.xensource.com/xen-users > >    > Ã*  10. mailto:[22][24]Xen-users@lists.xensource.com > >    > Ã*  11. [23][25]http://lists.xensource.com/xen-users > >    _______________________________________________ > >    Xen-users mailing list > >    [24][26]Xen-users@lists.xensource.com > >    [25][27]http://lists.xensource.com/xen-users > > > > References > > > >   Visible links > >   1. mailto:[28]pasik@iki.fi > >   2. mailto:[29]pasik@iki.fi > >   3. mailto:[30]kjw53@cam.ac.uk > >   4. mailto:[31]Xen-users@lists.xensource.com > >   5. [32]http://lists.xensource.com/xen-users > >   6. mailto:[33]kjw53@cam.ac.uk > >   7. mailto:[34]Xen-users@lists.xensource.com > >   8. [35]http://lists.xensource.com/xen-users > >   9. mailto:[36]Xen-users@lists.xensource.com > >  10. [37]http://lists.xensource.com/xen-users > >  11. mailto:[38]Xen-users@lists.xensource.com > >  12. [39]http://lists.xensource.com/xen-users > >  13. mailto:[40]pasik@iki.fi > >  14. mailto:[41]kjw53@cam.ac.uk > >  15. mailto:[42]Xen-users@lists.xensource.com > >  16. [43]http://lists.xensource.com/xen-users > >  17. mailto:[44]kjw53@cam.ac.uk > >  18. mailto:[45]Xen-users@lists.xensource.com > >  19. [46]http://lists.xensource.com/xen-users > >  20. mailto:[47]Xen-users@lists.xensource.com > >  21. [48]http://lists.xensource.com/xen-users > >  22. mailto:[49]Xen-users@lists.xensource.com > >  23. [50]http://lists.xensource.com/xen-users > >  24. mailto:[51]Xen-users@lists.xensource.com > >  25. [52]http://lists.xensource.com/xen-users > > References > > Visible links > 1. mailto:pasik@iki.fi > 2. http://wiki.xensource.com/xenwiki/VTdHowTo > 3. mailto:pasik@iki.fi > 4. mailto:pasik@iki.fi > 5. mailto:kjw53@cam.ac.uk > 6. mailto:Xen-users@lists.xensource.com > 7. http://lists.xensource.com/xen-users > 8. mailto:kjw53@cam.ac.uk > 9. mailto:Xen-users@lists.xensource.com > 10. http://lists.xensource.com/xen-users > 11. mailto:Xen-users@lists.xensource.com > 12. http://lists.xensource.com/xen-users > 13. mailto:Xen-users@lists.xensource.com > 14. http://lists.xensource.com/xen-users > 15. mailto:pasik@iki.fi > 16. mailto:kjw53@cam.ac.uk > 17. mailto:Xen-users@lists.xensource.com > 18. http://lists.xensource.com/xen-users > 19. mailto:kjw53@cam.ac.uk > 20. mailto:Xen-users@lists.xensource.com > 21. http://lists.xensource.com/xen-users > 22. mailto:Xen-users@lists.xensource.com > 23. http://lists.xensource.com/xen-users > 24. mailto:Xen-users@lists.xensource.com > 25. http://lists.xensource.com/xen-users > 26. mailto:Xen-users@lists.xensource.com > 27. http://lists.xensource.com/xen-users > 28. mailto:pasik@iki.fi > 29. mailto:pasik@iki.fi > 30. mailto:kjw53@cam.ac.uk > 31. mailto:Xen-users@lists.xensource.com > 32. http://lists.xensource.com/xen-users > 33. mailto:kjw53@cam.ac.uk > 34. mailto:Xen-users@lists.xensource.com > 35. http://lists.xensource.com/xen-users > 36. mailto:Xen-users@lists.xensource.com > 37. http://lists.xensource.com/xen-users > 38. mailto:Xen-users@lists.xensource.com > 39. http://lists.xensource.com/xen-users > 40. mailto:pasik@iki.fi > 41. mailto:kjw53@cam.ac.uk > 42. mailto:Xen-users@lists.xensource.com > 43. http://lists.xensource.com/xen-users > 44. mailto:kjw53@cam.ac.uk > 45. mailto:Xen-users@lists.xensource.com > 46. http://lists.xensource.com/xen-users > 47. mailto:Xen-users@lists.xensource.com > 48. http://lists.xensource.com/xen-users > 49. mailto:Xen-users@lists.xensource.com > 50. http://lists.xensource.com/xen-users > 51. mailto:Xen-users@lists.xensource.com > 52. http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users