Stefan Bauer
2008-Oct-25 16:09 UTC
[Xen-users] VTd - PCI Passthrough - VMError: fail to assign device
Dear Users,
Debian Etch 2.6.18.8-xen from xensource.com with Xen 3.3.0 on AMD64:
After i want to start the HVM i get:
VmError: fail to assign device(1:0.0): maybe it has already been
assigned to other domain, or maybe it doesn''t exist.
[2008-10-25 19:59:30 2460] DEBUG (__init__:1072)
XendDomainInfo.destroy: domid=5
[2008-10-25 19:59:30 2460] DEBUG (__init__:1072)
XendDomainInfo.destroyDomain(5)
[2008-10-25 19:59:30 2460] DEBUG (__init__:1072) No device model
[2008-10-25 19:59:30 2460] DEBUG (__init__:1072) Releasing devices
[2008-10-25 19:59:30 2460] ERROR (__init__:1072) Domain construction
failed
Traceback (most recent call last):
File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 92, in
create
vm.start()
File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 424, in
start
XendTask.log_progress(0, 30, self._constructDomain)
File "//usr/lib64/python/xen/xend/XendTask.py", line 209, in
log_progress
retval = func(*args, **kwds)
File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 2103, in
_constructDomain
raise VmError("fail to assign device(%x:%x.%x): maybe it has"
VmError: fail to assign device(1:0.0): maybe it has already been
assigned to other domain, or maybe it doesn''t exist.
I want to passthrough a PCI-E graphiccard to a windows 2000 hvm-guest:
01:00.0 is the correct pci-id from lspci output:
After the pci device is hidden, lspci doesnt show it anymore as expected.
Please see details below:
/boot/grub/menu.lst
title Debian 2.6.18.8-xen
root (hd0,1)
kernel /boot/xen-3.3.0.gz console=vga max_loop=128 dom0_mem=512M
iommu=1 vtd=1
module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda2 ro
pciback.hide=(01:00.0)
module /boot/initrd.img-2.6.18.8-xen
/etc/xen/win2k
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 512
name = "win2k"
acpi=0
pci = [ ''01:00.0'' ]
... and a few other things ...
xm dmesg
__ __ _____ _____ ___
\ \/ /___ _ __ |___ / |___ / / _ \
\ // _ \ ''_ \ |_ \ |_ \| | | |
/ \ __/ | | | ___) | ___) | |_| |
/_/\_\___|_| |_| |____(_)____(_)___/
(XEN) Xen version 3.3.0 (root@) (gcc version 4.1.2 20061115
(prerelease) (Debian 4.1.1-21)) Sat Oct 25 12:58:03 CEST 2008
(XEN) Latest ChangeSet: unavailable
(XEN) Command line: console=vga max_loop=128 dom0_mem=512M iommu=1 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 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 000000000009e000 (usable)
(XEN) 000000000009e000 - 00000000000a0000 (reserved)
(XEN) 00000000000ce000 - 00000000000d0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000be4b0000 (usable)
(XEN) 00000000be4b0000 - 00000000be4c9000 (ACPI data)
(XEN) 00000000be4c9000 - 00000000be4cc000 (ACPI NVS)
(XEN) 00000000be4cc000 - 00000000c0000000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec10000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ff000000 - 0000000100000000 (reserved)
(XEN) System RAM: 3044MB (3117368kB)
(XEN) ACPI: RSDP 000F5E00, 0024 (r2 PTLTD )
(XEN) ACPI: XSDT BE4BD887, 00B4 (r1 LENOVO TC-2R 60400D0 LTP
0)
(XEN) ACPI: TCPA BE4C8AD9, 0032 (r2 LENOVO TC-2R 60400D0 PTL
0)
(XEN) ACPI: FACP BE4C8B0B, 00F4 (r3 INTEL 60400D0 PTL
3)
(XEN) ACPI: DSDT BE4C0F80, 7AE5 (r1 INTEL BEARLAKE 60400D0 MSFT
100000E)
(XEN) ACPI: FACS BE4CBFC0, 0040
(XEN) ACPI: DMAR BE4C8BFF, 0110 (r1 Intel OEMDMAR 60400D0 LOHR
1)
(XEN) ACPI: SLIC BE4C8D0F, 0176 (r1 LENOVO TC-2R 60400D0 LTP
0)
(XEN) ACPI: MCFG BE4C8E85, 003C (r1 PTLTD MCFG 60400D0 LTP
0)
(XEN) ACPI: HPET BE4C8EC1, 0038 (r1 PTLTD HPETTBL 60400D0 LTP
1)
(XEN) ACPI: APIC BE4C8EF9, 0068 (r1 PTLTD APIC 60400D0 LTP
0)
(XEN) ACPI: BOOT BE4C8F61, 0028 (r1 PTLTD $SBFTBL$ 60400D0 LTP
1)
(XEN) ACPI: ASF! BE4C8F89, 0077 (r16 CETP CETP 60400D0 PTL
1)
(XEN) ACPI: SSDT BE4BF1CA, 025F (r1 PmRef Cpu0Tst 3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BF124, 00A6 (r1 PmRef Cpu7Tst 3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BF07E, 00A6 (r1 PmRef Cpu6Tst 3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BEFD8, 00A6 (r1 PmRef Cpu5Tst 3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BEF32, 00A6 (r1 PmRef Cpu4Tst 3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BEE8C, 00A6 (r1 PmRef Cpu3Tst 3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BEDE6, 00A6 (r1 PmRef Cpu2Tst 3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BED40, 00A6 (r1 PmRef Cpu1Tst 3000 INTL
20050228)
(XEN) ACPI: SSDT BE4BD93B, 1405 (r1 PmRef CpuPm 3000 INTL
20050228)
(XEN) Xen heap: 14MB (14688kB)
(XEN) Domain heap initialised
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 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) Intel VT-d has been enabled
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2327.540 MHz processor.
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz stepping 0b
(XEN) Booting processor 1/1 eip 8c000
(XEN) CPU1: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz stepping 0b
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000
(XEN) [VT-D]iommu.c:744: iommu_fault_status: Fault Overflow
(XEN) [VT-D]iommu.c:729: iommu_fault:DMA Write: 0:2.0 addr 200200000
REASON 5 iommu->reg = ffff828bfff57000
(XEN) print_vtd_entries: iommu = ffff8300bd6ad180 bdf = 0:2:0 gmfn 200200
(XEN) root_entry = ffff8300bc9e0000
(XEN) root_entry[0] = b9cd6001
(XEN) context = ffff8300b9cd6000
(XEN) context[10] = 101_be4a6001
(XEN) l3 = ffff8300be4a6000
(XEN) l3_index = 8
(XEN) l3[8] = 0
(XEN) l3[8] not present
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x52fecc
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 00000000b8000000->00000000b9000000 (126976 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80200000->ffffffff8052fecc
(XEN) Init. ramdisk: ffffffff80530000->ffffffff80a98c00
(XEN) Phys-Mach map: ffffffff80a99000->ffffffff80b99000
(XEN) Start info: ffffffff80b99000->ffffffff80b994a4
(XEN) Page tables: ffffffff80b9a000->ffffffff80ba5000
(XEN) Boot stack: ffffffff80ba5000->ffffffff80ba6000
(XEN) TOTAL: ffffffff80000000->ffffffff81000000
(XEN) ENTRY ADDRESS: ffffffff80200000
(XEN) Dom0 has maximum 2 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 108kB init memory.
(XEN) domctl.c:635:d0 XEN_DOMCTL_test_assign_device: 1:0:0 already
assigned, or non-existent
(XEN) domctl.c:635:d0 XEN_DOMCTL_test_assign_device: 1:0:0 already
assigned, or non-existent
xm info
host : xen64
release : 2.6.18.8-xen
version : #2 SMP Sat Oct 25 12:57:40 CEST 2008
machine : x86_64
nr_cpus : 2
nr_nodes : 1
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 2327
hw_caps :
bfebfbff:20100800:00000000:00000140:0000e3fd:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 3044
free_memory : 2469
node_to_cpu : node0:0-1
node_to_memory : node0:2469
xen_major : 3
xen_minor : 3
xen_extra : .0
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.2 20061115 (prerelease)
(Debian 4.1.1-21)
cc_compile_by : root
cc_compile_domain :
cc_compile_date : Sat Oct 25 12:58:03 CEST 2008
xend_config_format : 4
xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 512 2 r-----
7.7
Help is greatly appreciated
--
Stefan
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Todd Deshane
2008-Oct-25 18:26 UTC
Re: [Xen-users] VTd - PCI Passthrough - VMError: fail to assign device
Some questions and comments inline. On Sat, Oct 25, 2008 at 12:09 PM, Stefan Bauer <stefan.bauer@cubewerk.de> wrote:> Debian Etch 2.6.18.8-xen from xensource.com with Xen 3.3.0 on AMD64:> VmError: fail to assign device(1:0.0): maybe it has already been > assigned to other domain, or maybe it doesn''t exist.<snip>> File "//usr/lib64/python/xen/xend/XendDomainInfo.py", line 2103, in > _constructDomain > raise VmError("fail to assign device(%x:%x.%x): maybe it has" > VmError: fail to assign device(1:0.0): maybe it has already been > assigned to other domain, or maybe it doesn''t exist. >> I want to passthrough a PCI-E graphiccard to a windows 2000 hvm-guest: > 01:00.0 is the correct pci-id from lspci output: >This type of thing should work.> After the pci device is hidden, lspci doesnt show it anymore as expected. >This is actually not expected, or at least I don''t usually see it that way. Here are some things to check. look in /sys/bus/pci/drivers/pciback to see if it has the 01:00.0 device. Also notice this error in your output <snip>> (XEN) I/O virtualisation enabled > (XEN) I/O virtualisation for PV guests disabled > (XEN) [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 > (XEN) [VT-D]iommu.c:744: iommu_fault_status: Fault Overflow > (XEN) [VT-D]iommu.c:729: iommu_fault:DMA Write: 0:2.0 addr 200200000 > REASON 5 iommu->reg = ffff828bfff57000 > (XEN) print_vtd_entries: iommu = ffff8300bd6ad180 bdf = 0:2:0 gmfn > 200200 > (XEN) root_entry = ffff8300bc9e0000 > (XEN) root_entry[0] = b9cd6001 > (XEN) context = ffff8300b9cd6000 > (XEN) context[10] = 101_be4a6001 > (XEN) l3 = ffff8300be4a6000 > (XEN) l3_index = 8 > (XEN) l3[8] = 0 > (XEN) l3[8] not present<snip>> (XEN) domctl.c:635:d0 XEN_DOMCTL_test_assign_device: 1:0:0 already > assigned, or non-existent > (XEN) domctl.c:635:d0 XEN_DOMCTL_test_assign_device: 1:0:0 already > assigned, or non-existentI would suggest, trying xen-unstable and if these errors still exist, maybe there is a bug. Did you boot back into normal linux (without the hiding) to see that the device comes back? As I mentioned above, I would expect the lspci to show it in both cases. Hope that helps with some troubleshooting steps. Cheers, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Stefan Bauer
2008-Oct-25 20:39 UTC
Re: [Xen-users] VTd - PCI Passthrough - VMError: fail to assign device
Todd Deshane schrieb:> look in /sys/bus/pci/drivers/pciback to see if it has the 01:00.0 device.cat /sys/bus/pci/drivers/pciback/slots give me: 0000:01:00.0 which seems to be fine :>> Also notice this error in your output > <snip> >> (XEN) I/O virtualisation enabled >> (XEN) I/O virtualisation for PV guests disabled >> (XEN) [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff57000 >> (XEN) [VT-D]iommu.c:744: iommu_fault_status: Fault Overflow >> (XEN) [VT-D]iommu.c:729: iommu_fault:DMA Write: 0:2.0 addr 200200000 >> REASON 5 iommu->reg = ffff828bfff57000 >> (XEN) print_vtd_entries: iommu = ffff8300bd6ad180 bdf = 0:2:0 gmfn >> 200200 >> (XEN) root_entry = ffff8300bc9e0000 >> (XEN) root_entry[0] = b9cd6001 >> (XEN) context = ffff8300b9cd6000 >> (XEN) context[10] = 101_be4a6001 >> (XEN) l3 = ffff8300be4a6000 >> (XEN) l3_index = 8 >> (XEN) l3[8] = 0 >> (XEN) l3[8] not present > <snip>Ouch, looks like a serious problem. Are there some other kernel boot options to get rid of this problem?> I would suggest, trying xen-unstable and if these errors still exist, maybe > there is a bug.I''m gonna try to bring up some testing environment to track this problem down.> Did you boot back into normal linux (without the hiding) to see that the > device comes back?If i remove the pciback.hide=(01:00.0) line, lspci shows that nvidia gfx-card. Regards -- Stefan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users