Hi, I''m having some problems assigning a PCI device to an OpenBSD HVM. The HVM will boot without the pci = line in the configuration but as soon as it is added I get: # xm create hvm_obsd Using config file "/etc/xen/hvm_obsd". Error: Fail to assign device(1:0.0): maybe VT-d is not enabled, or the device is not exist, or it has already been assigned to other domain My system is running Gentoo using the 2.6.21-xen kernel and Xen 3.2.1. I believe that the hardware I am using should support VT-d - a Gigabyte GA-G33M-S2 (i.e. Intel G33 chipset) and a Core 2 Duo E8200 processor. I am also confident that the PCI device has been seized by the pciback driver: # dmesg | grep seizing pciback 0000:01:00.0: seizing device pciback 0000:02:00.0: seizing device pciback 0000:02:01.0: seizing device pciback 0000:03:00.0: seizing device pciback 0000:03:00.1: seizing device pciback 0000:04:00.0: seizing device pciback 0000:04:00.1: seizing device (I''m trying to export a multiport nic exported to the hvm, the actual interfaces are 03.00.0/1 and 04:00.0/1, the rest I think are PCI bridges? I don''t know if I just have to hide the final address or the whole tree but neither way works at the moment.) My suspicion is that the BIOS (using the latest F7f release) for the machine may not be enabling all the virtualisation features of the system as in xm dmesg (full output below) I get (XEN) [VT-D]ACPI DMAR:No DMAR devices found Are there any suggestions for things to try to get this working? I thought even if I didn''t have VT-d I should still be able to export a PCI device to a domU? The other thing that I have noticed is that the /proc/cpuinfo flags do not list vmx when running under xen but if I boot a Knoppix livecd then this capability is reported, is that to be expected? Thanks, James # xm dmesg __ __ _____ ____ _ \ \/ /___ _ __ |___ / |___ \ / | \ // _ \ ''_ \ |_ \ __) | | | / \ __/ | | | ___) | / __/ _| | /_/\_\___|_| |_| |____(_)_____(_)_| (XEN) Xen version 3.2.1 (root@dingwall.me.uk) (gcc version 4.1.2 (Gentoo 4.1.2 p1.1)) Fri May 9 11:24:51 BST 2008 (XEN) Latest ChangeSet: unavailable (XEN) Command line: console=vga vtd=1 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 2 MBR signatures (XEN) Found 2 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009e800 (usable) (XEN) 000000000009f800 - 00000000000a0000 (reserved) (XEN) 00000000000f0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000007f5e0000 (usable) (XEN) 000000007f5e0000 - 000000007f5e3000 (ACPI NVS) (XEN) 000000007f5e3000 - 000000007f5f0000 (ACPI data) (XEN) 000000007f5f0000 - 000000007f600000 (reserved) (XEN) 00000000d0000000 - 00000000e0000000 (reserved) (XEN) 00000000fec00000 - 0000000100000000 (reserved) (XEN) System RAM: 2037MB (2086392kB) (XEN) Xen heap: 14MB (15044kB) (XEN) Domain heap initialised: DMA width 32 bits (XEN) Processor #0 7:7 APIC version 20 (XEN) Processor #1 7:7 APIC version 20 (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) [VT-D]ACPI DMAR:No DMAR devices found (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2666.802 MHz processor. (XEN) HVM: VMX enabled (XEN) CPU0: Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz stepping 06 (XEN) Booting processor 1/1 eip 8c000 (XEN) CPU1: Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz stepping 06 (XEN) Total of 2 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Platform timer overflows in 14998 jiffies. (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 2 CPUs (XEN) xenoprof: Initialization failed. Intel processor model 23 for P6 class family is not supported (XEN) AMD IOMMU: Disabled (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x7082c8 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000007a000000->000000007b000000 (474683 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80200000->ffffffff807082c8 (XEN) Init. ramdisk: ffffffff80709000->ffffffff80bbf200 (XEN) Phys-Mach map: ffffffff80bc0000->ffffffff80f671d8 (XEN) Start info: ffffffff80f68000->ffffffff80f684a4 (XEN) Page tables: ffffffff80f69000->ffffffff80f74000 (XEN) Boot stack: ffffffff80f74000->ffffffff80f75000 (XEN) TOTAL: ffffffff80000000->ffffffff81000000 (XEN) ENTRY ADDRESS: ffffffff80200000 (XEN) Dom0 has maximum 2 VCPUs (XEN) Initrd len 0x4b6200, start at 0xffffffff80709000 (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 100kB init memory. This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I''m having some problems assigning a PCI device to an OpenBSD HVM. The HVM will boot without the pci = line in the configuration but as soon as it is added I get: # xm create hvm_obsd Using config file "/etc/xen/hvm_obsd". Error: Fail to assign device(1:0.0): maybe VT-d is not enabled, or the device is not exist, or it has already been assigned to other domain My system is running Gentoo using the 2.6.21-xen kernel and Xen 3.2.1. I believe that the hardware I am using should support VT-d - a Gigabyte GA-G33M-S2 (i.e. Intel G33 chipset) and a Core 2 Duo E8200 processor. I am also confident that the PCI device has been seized by the pciback driver: # dmesg | grep seizing pciback 0000:01:00.0: seizing device pciback 0000:02:00.0: seizing device pciback 0000:02:01.0: seizing device pciback 0000:03:00.0: seizing device pciback 0000:03:00.1: seizing device pciback 0000:04:00.0: seizing device pciback 0000:04:00.1: seizing device The device I''m trying to export is a multiport nic, the actual interfaces are 03.00.0/1 and 04:00.0/1, the rest I think are PCI bridges? I don''t know if I just have to hide the final address or the whole tree but neither way works at the moment. My suspicion is that the BIOS (using the latest F7f release) for the machine may not be enabling all the virtualisation features of the system as in xm dmesg (full output below) I get (XEN) [VT-D]ACPI DMAR:No DMAR devices found Are there any suggestions for things to try to get this working? I thought even if I didn''t have VT-d I should still be able to export a PCI device to a domU? The other thing that I have noticed is that the /proc/cpuinfo flags do not list vmx when running under xen but if I boot a Knoppix livecd then this capability is reported, is that to be expected? Thanks, James # xm dmesg __ __ _____ ____ _ \ \/ /___ _ __ |___ / |___ \ / | \ // _ \ ''_ \ |_ \ __) | | | / \ __/ | | | ___) | / __/ _| | /_/\_\___|_| |_| |____(_)_____(_)_| (XEN) Xen version 3.2.1 (root@dingwall.me.uk) (gcc version 4.1.2 (Gentoo 4.1.2 p1.1)) Fri May 9 11:24:51 BST 2008 (XEN) Latest ChangeSet: unavailable (XEN) Command line: console=vga vtd=1 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 2 MBR signatures (XEN) Found 2 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009e800 (usable) (XEN) 000000000009f800 - 00000000000a0000 (reserved) (XEN) 00000000000f0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000007f5e0000 (usable) (XEN) 000000007f5e0000 - 000000007f5e3000 (ACPI NVS) (XEN) 000000007f5e3000 - 000000007f5f0000 (ACPI data) (XEN) 000000007f5f0000 - 000000007f600000 (reserved) (XEN) 00000000d0000000 - 00000000e0000000 (reserved) (XEN) 00000000fec00000 - 0000000100000000 (reserved) (XEN) System RAM: 2037MB (2086392kB) (XEN) Xen heap: 14MB (15044kB) (XEN) Domain heap initialised: DMA width 32 bits (XEN) Processor #0 7:7 APIC version 20 (XEN) Processor #1 7:7 APIC version 20 (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) [VT-D]ACPI DMAR:No DMAR devices found (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2666.802 MHz processor. (XEN) HVM: VMX enabled (XEN) CPU0: Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz stepping 06 (XEN) Booting processor 1/1 eip 8c000 (XEN) CPU1: Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz stepping 06 (XEN) Total of 2 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Platform timer overflows in 14998 jiffies. (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 2 CPUs (XEN) xenoprof: Initialization failed. Intel processor model 23 for P6 class family is not supported (XEN) AMD IOMMU: Disabled (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x7082c8 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000007a000000->000000007b000000 (474683 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80200000->ffffffff807082c8 (XEN) Init. ramdisk: ffffffff80709000->ffffffff80bbf200 (XEN) Phys-Mach map: ffffffff80bc0000->ffffffff80f671d8 (XEN) Start info: ffffffff80f68000->ffffffff80f684a4 (XEN) Page tables: ffffffff80f69000->ffffffff80f74000 (XEN) Boot stack: ffffffff80f74000->ffffffff80f75000 (XEN) TOTAL: ffffffff80000000->ffffffff81000000 (XEN) ENTRY ADDRESS: ffffffff80200000 (XEN) Dom0 has maximum 2 VCPUs (XEN) Initrd len 0x4b6200, start at 0xffffffff80709000 (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 100kB init memory. This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi James- AFAIK, the Intel G33 does not support the VT-d extensions for Virtualization. Cheers, Dan James Dingwall wrote:> Hi, > > I''m having some problems assigning a PCI device to an OpenBSD HVM. The > HVM will boot without the pci = line in the configuration but as soon as > it is added I get: > > # xm create hvm_obsd > Using config file "/etc/xen/hvm_obsd". > Error: Fail to assign device(1:0.0): maybe VT-d is not enabled, or the > device is not exist, or it has already been assigned to other domain > > My system is running Gentoo using the 2.6.21-xen kernel and Xen 3.2.1. > I believe that the hardware I am using should support VT-d - a Gigabyte > GA-G33M-S2 (i.e. Intel G33 chipset) and a Core 2 Duo E8200 processor. I > am also confident that the PCI device has been seized by the pciback > driver: >-- Cheers, Daniel Kao, Übermind Seattle, WA dkao@ubermind.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,> AFAIK, the Intel G33 does not support the VT-d extensions for > Virtualization.>From what I can see the G33 codename was bearlake (http://en.wikipedia.org/wiki/List_of_Intel_chipsets) and I think it was this chipset that introduced VT-d. However, it looks like it is only the Q series of this chipset which supports VT-d according to http://sg.vr-zone.com/?i=4013. If this is the case how can I make my PCI device available in the HVM or will I only be able to export to a pv domU?Thanks, James James Dingwall wrote:> Hi, > > I''m having some problems assigning a PCI device to an OpenBSD HVM. The > HVM will boot without the pci = line in the configuration but as soon as > it is added I get: > > # xm create hvm_obsd > Using config file "/etc/xen/hvm_obsd". > Error: Fail to assign device(1:0.0): maybe VT-d is not enabled, or the > device is not exist, or it has already been assigned to other domain > > My system is running Gentoo using the 2.6.21-xen kernel and Xen 3.2.1. > I believe that the hardware I am using should support VT-d - a Gigabyte > GA-G33M-S2 (i.e. Intel G33 chipset) and a Core 2 Duo E8200 processor. I > am also confident that the PCI device has been seized by the pciback > driver: >-- Cheers, Daniel Kao, Übermind Seattle, WA dkao@ubermind.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Your motherboard chipset does not support VT-d. You can only assign a PCI device to an HVM domain if you have VT-d. You can assign a PCI device to a PV domain without VT-d. James Dingwall wrote:> Hi, > > I''m having some problems assigning a PCI device to an OpenBSD HVM. The > HVM will boot without the pci = line in the configuration but as soon as > it is added I get: > > # xm create hvm_obsd > Using config file "/etc/xen/hvm_obsd". > Error: Fail to assign device(1:0.0): maybe VT-d is not enabled, or the > device is not exist, or it has already been assigned to other domain > > My system is running Gentoo using the 2.6.21-xen kernel and Xen 3.2.1. > I believe that the hardware I am using should support VT-d - a Gigabyte > GA-G33M-S2 (i.e. Intel G33 chipset) and a Core 2 Duo E8200 processor. I > am also confident that the PCI device has been seized by the pciback > driver: > > # dmesg | grep seizing > pciback 0000:01:00.0: seizing device > pciback 0000:02:00.0: seizing device > pciback 0000:02:01.0: seizing device > pciback 0000:03:00.0: seizing device > pciback 0000:03:00.1: seizing device > pciback 0000:04:00.0: seizing device > pciback 0000:04:00.1: seizing device > > (I''m trying to export a multiport nic exported to the hvm, the actual > interfaces are 03.00.0/1 and 04:00.0/1, the rest I think are PCI > bridges? I don''t know if I just have to hide the final address or the > whole tree but neither way works at the moment.) > > My suspicion is that the BIOS (using the latest F7f release) for the > machine may not be enabling all the virtualisation features of the > system as in xm dmesg (full output below) I get > > (XEN) [VT-D]ACPI DMAR:No DMAR devices found > > Are there any suggestions for things to try to get this working? I > thought even if I didn''t have VT-d I should still be able to export a > PCI device to a domU? The other thing that I have noticed is that the > /proc/cpuinfo flags do not list vmx when running under xen but if I boot > a Knoppix livecd then this capability is reported, is that to be > expected? > > Thanks, > James > > > > # xm dmesg > __ __ _____ ____ _ > \ \/ /___ _ __ |___ / |___ \ / | > \ // _ \ ''_ \ |_ \ __) | | | > / \ __/ | | | ___) | / __/ _| | > /_/\_\___|_| |_| |____(_)_____(_)_| > > (XEN) Xen version 3.2.1 (root@dingwall.me.uk) (gcc version 4.1.2 (Gentoo > 4.1.2 p1.1)) Fri May 9 11:24:51 BST 2008 > (XEN) Latest ChangeSet: unavailable > (XEN) Command line: console=vga vtd=1 > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds > (XEN) EDID info not retrieved because no DDC retrieval method detected > (XEN) Disc information: > (XEN) Found 2 MBR signatures > (XEN) Found 2 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009e800 (usable) > (XEN) 000000000009f800 - 00000000000a0000 (reserved) > (XEN) 00000000000f0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 000000007f5e0000 (usable) > (XEN) 000000007f5e0000 - 000000007f5e3000 (ACPI NVS) > (XEN) 000000007f5e3000 - 000000007f5f0000 (ACPI data) > (XEN) 000000007f5f0000 - 000000007f600000 (reserved) > (XEN) 00000000d0000000 - 00000000e0000000 (reserved) > (XEN) 00000000fec00000 - 0000000100000000 (reserved) > (XEN) System RAM: 2037MB (2086392kB) > (XEN) Xen heap: 14MB (15044kB) > (XEN) Domain heap initialised: DMA width 32 bits > (XEN) Processor #0 7:7 APIC version 20 > (XEN) Processor #1 7:7 APIC version 20 > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) [VT-D]ACPI DMAR:No DMAR devices found > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 2666.802 MHz processor. > (XEN) HVM: VMX enabled > (XEN) CPU0: Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz stepping 06 > (XEN) Booting processor 1/1 eip 8c000 > (XEN) CPU1: Intel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz stepping 06 > (XEN) Total of 2 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using new ACK method > (XEN) Platform timer overflows in 14998 jiffies. > (XEN) Platform timer is 14.318MHz HPET > (XEN) Brought up 2 CPUs > (XEN) xenoprof: Initialization failed. Intel processor model 23 for P6 > class family is not supported > (XEN) AMD IOMMU: Disabled > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x7082c8 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 000000007a000000->000000007b000000 (474683 pages > to be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff80200000->ffffffff807082c8 > (XEN) Init. ramdisk: ffffffff80709000->ffffffff80bbf200 > (XEN) Phys-Mach map: ffffffff80bc0000->ffffffff80f671d8 > (XEN) Start info: ffffffff80f68000->ffffffff80f684a4 > (XEN) Page tables: ffffffff80f69000->ffffffff80f74000 > (XEN) Boot stack: ffffffff80f74000->ffffffff80f75000 > (XEN) TOTAL: ffffffff80000000->ffffffff81000000 > (XEN) ENTRY ADDRESS: ffffffff80200000 > (XEN) Dom0 has maximum 2 VCPUs > (XEN) Initrd len 0x4b6200, start at 0xffffffff80709000 > (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 100kB init memory. > > This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, > you may review at http://www.amdocs.com/email_disclaimer.asp > > _______________________________________________ > 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