* pci pass-through, NIC card
@ 2008-03-27 15:30 Jean Guyader
2008-03-28 11:16 ` Jean Guyader
0 siblings, 1 reply; 7+ messages in thread
From: Jean Guyader @ 2008-03-27 15:30 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
Hi,
I am trying to make the vt-d and pci pass-through work and I have some
problems. I just try to give a NIC to an HVM guest.
When I create the vm the hypervisor goes to an infinite loop,
it displays in loop the message enclosed (console_on_xm_create).
I use xen x86_64, debian etch dom0 with linux-2.6.18.8-xen 32.
The hvm guest is a debian etch 64.
Cheers,
--
Jean Guyader
[-- Attachment #2: console_on_xm_create --]
[-- Type: text/plain, Size: 5540 bytes --]
pciback: vpci: 0000:07:01.0: assign to virtual slot 0
(XEN) printk: 2050 messages suppressed.
(XEN) [VT-D]iommu.c:1465:d0 domain_context_unmap:bus2bridge[7].bus != 0
(XEN) [VT-D]iommu.c:1346:d0 domain_context_mapping:bus2bridge[7].bus != 0
(XEN) [VT-D]iommu.c:883: iommu_page_fault: iommu->reg = ffff828bfff56000
(XEN) [VT-D]iommu.c:855: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Write: 7:0.0 addr 0 REASON c iommu->reg = ffff828bfff56000
(XEN) print_vtd_entries: domain_id = 7fff bdf = 7:0:0 gmfn = 0
(XEN) hg->pgd == NULL
(last message repeat a lot of time cut ....)
e1000: peth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Tx Queue <0>
TDH <ce>
TDT <ce>
next_to_use <ce>
next_to_clean <cb>
buffer_info[next_to_clean]
time_stamp <1f80>
next_to_watch <cb>
jiffies <2071>
next_to_watch.status <0>
(XEN) [VT-D]iommu.c:883: iommu_page_fault: iommu->reg = ffff828bfff56000
(XEN) [VT-D]iommu.c:855: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Read: 7:0.0 addr 13881000 REASON c iommu->reg = ffff828bfff56000
(XEN) print_vtd_entries: domain_id = 7fff bdf = 7:0:0 gmfn = 13881
(XEN) hg->pgd == NULL
(last message repeat a lot of time cut ....)
(XEN) [VT-D]iommu.c:883: iommu_page_fault: iommu->reg = ffff828bfff56000
(XEN) [VT-D]iommu.c:855: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Write: 7:0.0 addr 0 REASON c iommu->reg = ffff828bfff56000
(XEN) print_vtd_entries: domain_id = 7fff bdf = 7:0:0 gmfn = 0
(XEN) hg->pgd == NULL
NETDEV WATCHDOG: peth0: transmit timed out
(XEN) [VT-D]iommu.c:883: iommu_page_fault: iommu->reg = ffff828bfff56000
(XEN) [VT-D]iommu.c:855: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Read: 7:0.0 addr 13881000 REASON c iommu->reg = ffff828bfff56000
(XEN) print_vtd_entries: domain_id = 7fff bdf = 7:0:0 gmfn = 13881
(XEN) hg->pgd == NULL
(last message repeat a lot of time cut ....)
eth0: port 1(peth0) entering disabled state
(XEN) [VT-D]iommu.c:883: iommu_page_fault: iommu->reg = ffff828bfff56000
(XEN) [VT-D]iommu.c:855: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Write: 7:0.0 addr 0 REASON c iommu->reg = ffff828bfff56000
(XEN) print_vtd_entries: domain_id = 7fff bdf = 7:0:0 gmfn = 0
(XEN) hg->pgd == NULL
e1000: peth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
eth0: port 1(peth0) entering learning state
eth0: topology change detected, propagating
eth0: port 1(peth0) entering forwarding state
(XEN) [VT-D]iommu.c:883: iommu_page_fault: iommu->reg = ffff828bfff56000
(XEN) [VT-D]iommu.c:855: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Write: 7:0.0 addr 0 REASON c iommu->reg = ffff828bfff56000
(XEN) print_vtd_entries: domain_id = 7fff bdf = 7:0:0 gmfn = 0
(XEN) hg->pgd == NULL
(XEN) [VT-D]iommu.c:883: iommu_page_fault: iommu->reg = ffff828bfff56000
(XEN) [VT-D]iommu.c:855: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Write: 7:0.0 addr 0 REASON c iommu->reg = ffff828bfff56000
(XEN) print_vtd_entries: domain_id = 7fff bdf = 7:0:0 gmfn = 0
(XEN) hg->pgd == NULL
(XEN) [VT-D]iommu.c:883: iommu_page_fault: iommu->reg = ffff828bfff56000
(XEN) [VT-D]iommu.c:855: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Read: 7:0.0 addr 1336a000 REASON c iommu->reg = ffff828bfff56000
(XEN) print_vtd_entries: domain_id = 0 bdf = 7:0:0 gmfn = 1336a
(XEN) d->pgd = ffff8300ceff2000 virt_to_maddr(hd->pgd) = ceff2000
(XEN) ---- print_vtd_entries 0 ----
(XEN) root_entry = ffff8300cf0bc000
(XEN) root_entry[7] = cf0b2001
(XEN) context = ffff8300cf0b2000
(XEN) context[0] = 202 21e5a0001
(XEN) l4 = ffff83021e5a0000
(XEN) l4_index = 0
(XEN) l4[0] = 21e5a1067
(XEN) l3 = ffff83021e5a1000
(XEN) l3_index = 0
(XEN) l3[0] = 21e5a2067
(XEN) l2 = ffff83021e5a2000
(XEN) l2_index = 99
(XEN) l2[99] = 0
(XEN) l2[99] not present
(XEN) ---- print_vtd_entries 1 ----
(XEN) root_entry = ffff8300cf0bc000
(XEN) root_entry[7] = cf0b2001
(XEN) context = ffff8300cf0b2000
(XEN) context[0] = 202 21e5a0001
(XEN) Unsupported VTD page table level (2)!
(XEN) ---- print_vtd_entries 2 ----
(XEN) root_entry = ffff8300cf0bc000
(XEN) root_entry[7] = cf0b2001
(XEN) context = ffff8300cf0b2000
(XEN) context[0] = 202 21e5a0001
(XEN) Unsupported VTD page table level (2)!
(XEN) ---- print_vtd_entries 3 ----
(XEN) root_entry = ffff8300cf0bc000
(XEN) root_entry[7] = cf0b2001
(XEN) context = ffff8300cf0b2000
(XEN) context[0] = 202 21e5a0001
(XEN) Unsupported VTD page table level (2)!
(XEN) ---- print_vtd_entries 4 ----
(XEN) root_entry = ffff8300cf0bc000
(XEN) root_entry[7] = cf0b2001
(XEN) context = ffff8300cf0b2000
(XEN) context[0] = 202 21e5a0001
(XEN) Unsupported VTD page table level (2)!
(XEN) ---- print_vtd_entries 5 ----
(XEN) root_entry = ffff8300cf0bc000
(XEN) root_entry[7] = cf0b2001
(XEN) context = ffff8300cf0b2000
(XEN) context[0] = 202 21e5a0001
(XEN) Unsupported VTD page table level (2)!
(XEN) ---- print_vtd_entries 6 ----
(XEN) root_entry = ffff8300cf0bc000
(XEN) root_entry[7] = cf0b2001
(XEN) context = ffff8300cf0b2000
(XEN) context[0] = 202 21e5a0001
(XEN) Unsupported VTD page table level (2)!
[-- Attachment #3: dmesg --]
[-- Type: text/plain, Size: 15309 bytes --]
PM: Adding info for pnp:00:01
PM: Adding info for pnp:00:02
PM: Adding info for pnp:00:03
PM: Adding info for pnp:00:04
PM: Adding info for pnp:00:05
PM: Adding info for pnp:00:06
PM: Adding info for pnp:00:07
PM: Adding info for pnp:00:08
PM: Adding info for pnp:00:09
PM: Adding info for pnp:00:0a
PM: Adding info for pnp:00:0b
pnp: PnP ACPI: found 12 devices
xen_mem: Initialising balloon driver.
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
pciback 0000:07:01.0: seizing device
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:03.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:05.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:05:00.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:04:00.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:04:00.3
IO window: 2000-2fff
MEM window: d8000000-d80fffff
PREFETCH window: d8400000-d84fffff
PCI: Bridge: 0000:00:07.0
IO window: 2000-2fff
MEM window: d8000000-d81fffff
PREFETCH window: d8400000-d84fffff
PCI: Bridge: 0000:00:09.0
IO window: 3000-3fff
MEM window: d8200000-d82fffff
PREFETCH window: d8500000-d85fffff
PCI: Bridge: 0000:00:1c.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1e.0
IO window: 4000-4fff
MEM window: d8300000-d83fffff
PREFETCH window: d0000000-d7ffffff
ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 48 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:01.0 to 64
ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 50 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:03.0 to 64
ACPI: PCI Interrupt 0000:00:05.0[A] -> GSI 52 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:05.0 to 64
ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI 54 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:07.0 to 64
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 54 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:04:00.0 to 64
ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 54 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:05:00.0 to 64
PCI: Setting latency timer of device 0000:04:00.3 to 64
ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 56 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:09.0 to 64
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:00:1c.0 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
PM: Adding info for platform:pcspkr
Simple Boot Flag at 0x41 set to 0x1
IA-32 Microcode Update Driver: v1.14a-xen <tigran@veritas.com>
audit: initializing netlink socket (disabled)
audit(1206629745.440:1): initialized
highmem bounce pool size: 64 pages
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: Setting latency timer of device 0000:00:01.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:01.0:pcie00]
PM: Adding info for pci_express:0000:00:01.0:pcie00
Allocate Port Service[0000:00:01.0:pcie01]
PM: Adding info for pci_express:0000:00:01.0:pcie01
PCI: Setting latency timer of device 0000:00:03.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:03.0:pcie00]
PM: Adding info for pci_express:0000:00:03.0:pcie00
Allocate Port Service[0000:00:03.0:pcie01]
PM: Adding info for pci_express:0000:00:03.0:pcie01
PCI: Setting latency timer of device 0000:00:05.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:05.0:pcie00]
PM: Adding info for pci_express:0000:00:05.0:pcie00
Allocate Port Service[0000:00:05.0:pcie01]
PM: Adding info for pci_express:0000:00:05.0:pcie01
PCI: Setting latency timer of device 0000:00:07.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:07.0:pcie00]
PM: Adding info for pci_express:0000:00:07.0:pcie00
Allocate Port Service[0000:00:07.0:pcie01]
PM: Adding info for pci_express:0000:00:07.0:pcie01
PCI: Setting latency timer of device 0000:00:09.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:09.0:pcie00]
PM: Adding info for pci_express:0000:00:09.0:pcie00
Allocate Port Service[0000:00:09.0:pcie01]
PM: Adding info for pci_express:0000:00:09.0:pcie01
PCI: Setting latency timer of device 0000:00:1c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.0:pcie00]
PM: Adding info for pci_express:0000:00:1c.0:pcie00
Allocate Port Service[0000:00:1c.0:pcie02]
PM: Adding info for pci_express:0000:00:1c.0:pcie02
Allocate Port Service[0000:00:1c.0:pcie03]
PM: Adding info for pci_express:0000:00:1c.0:pcie03
PCI: Setting latency timer of device 0000:04:00.0 to 64
Allocate Port Service[0000:04:00.0:pcie10]
PM: Adding info for pci_express:0000:04:00.0:pcie10
Allocate Port Service[0000:04:00.0:pcie11]
PM: Adding info for pci_express:0000:04:00.0:pcie11
PCI: Setting latency timer of device 0000:05:00.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:05:00.0:pcie20]
PM: Adding info for pci_express:0000:05:00.0:pcie20
Allocate Port Service[0000:05:00.0:pcie21]
PM: Adding info for pci_express:0000:05:00.0:pcie21
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI
Copyright (c) 1999-2006 Intel Corporation.
ACPI: PCI Interrupt 0000:07:02.0[A] -> GSI 28 (level, low) -> IRQ 22
e1000: 0000:07:02.0: e1000_probe: (PCI:66MHz:32-bit) 00:0e:0c:d9:48:65
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
Intel(R) PRO/10GbE Network Driver - version 1.0.109-k2
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Xen virtual console successfully installed as xvc0
Event-channel device installed.
ACPI: PCI Interrupt 0000:07:01.0[A] -> GSI 24 (level, low) -> IRQ 23
ACPI: PCI interrupt for device 0000:07:01.0 disabled
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
libata version 2.00 loaded.
ata_piix 0000:00:1f.2: version 2.00
ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 17 (level, low) -> IRQ 24
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x1880 irq 14
scsi0 : ata_piix
PM: Adding info for No Bus:host0
ata1.00: ATA-7, max UDMA/133, 312500000 sectors: LBA48
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
PM: Adding info for No Bus:target0:0:0
Vendor: ATA Model: Maxtor 6Y160M0 Rev: YAR5
Type: Direct-Access ANSI SCSI revision: 05
PM: Adding info for scsi:0:0:0:0
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x1888 irq 15
scsi1 : ata_piix
PM: Adding info for No Bus:host1
ata2.01: ATAPI, max UDMA/66
ata2.01: configured for UDMA/33
PM: Adding info for No Bus:target1:0:1
ATA: abnormal status 0x58 on port 0x177
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: (BMDMA stat 0x46)
ata2.01: tag 0 cmd 0xa0 Emask 0x20 stat 0x40 err 0x0 (host bus error)
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1)
ata2.01: revalidation failed (errno=-5)
ata2: failed to recover some devices, retrying in 5 secs
ata2: soft resetting port
ata2.01: configured for UDMA/33
ata2: EH complete
ATA: abnormal status 0x58 on port 0x177
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: (BMDMA stat 0x46)
ata2.01: tag 0 cmd 0xa0 Emask 0x20 stat 0x40 err 0x0 (host bus error)
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1)
ata2.01: revalidation failed (errno=-5)
ata2: failed to recover some devices, retrying in 5 secs
ata2: soft resetting port
ata2.01: configured for UDMA/33
ata2: EH complete
ATA: abnormal status 0x58 on port 0x177
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: (BMDMA stat 0x46)
ata2.01: tag 0 cmd 0xa0 Emask 0x20 stat 0x40 err 0x0 (host bus error)
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1)
ata2.01: revalidation failed (errno=-5)
ata2: failed to recover some devices, retrying in 5 secs
ata2: soft resetting port
ata2.01: configured for UDMA/33
ata2: EH complete
ATA: abnormal status 0x58 on port 0x177
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata2.01: (BMDMA stat 0x46)
ata2.01: tag 0 cmd 0xa0 Emask 0x20 stat 0x40 err 0x0 (host bus error)
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ATA: abnormal status 0x58 on port 0x177
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1)
ata2.01: revalidation failed (errno=-5)
ata2: failed to recover some devices, retrying in 5 secs
ata2: soft resetting port
ata2.01: configured for UDMA/33
ata2: EH complete
PM: Removing info for No Bus:target1:0:1
SCSI device sda: 312500000 512-byte hdwr sectors (160000 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 312500000 512-byte hdwr sectors (160000 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 < sda5 >
sd 0:0:0:0: Attached scsi disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
SCSI Media Changer driver v0.25
ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 25
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 25, io mem 0xd8604000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
PM: Adding info for usb:usb1
PM: Adding info for No Bus:usbdev1.1_ep00
usb usb1: configuration #1 chosen from 1 choice
PM: Adding info for usb:1-0:1.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
PM: Adding info for No Bus:usbdev1.1_ep81
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20 (level, low) -> IRQ 26
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 26, io base 0x00001800
PM: Adding info for usb:usb2
PM: Adding info for No Bus:usbdev2.1_ep00
usb usb2: configuration #1 chosen from 1 choice
PM: Adding info for usb:2-0:1.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
PM: Adding info for No Bus:usbdev2.1_ep81
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 21 (level, low) -> IRQ 27
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 27, io base 0x00001820
PM: Adding info for usb:usb3
PM: Adding info for No Bus:usbdev3.1_ep00
usb usb3: configuration #1 chosen from 1 choice
PM: Adding info for usb:3-0:1.0
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
PM: Adding info for No Bus:usbdev3.1_ep81
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 22 (level, low) -> IRQ 28
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 28, io base 0x00001840
PM: Adding info for usb:usb4
PM: Adding info for No Bus:usbdev4.1_ep00
usb usb4: configuration #1 chosen from 1 choice
PM: Adding info for usb:4-0:1.0
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
PM: Adding info for No Bus:usbdev4.1_ep81
usb 2-2: new low speed USB device using uhci_hcd and address 2
PM: Adding info for usb:2-2
PM: Adding info for No Bus:usbdev2.2_ep00
usb 2-2: configuration #1 chosen from 1 choice
PM: Adding info for usb:2-2:1.0
PM: Adding info for No Bus:usbdev2.2_ep81
PM: Adding info for usb:2-2:1.1
PM: Adding info for No Bus:usbdev2.2_ep82
input: Avocent Dell 03R874 as /class/input/input0
input: USB HID v1.10 Keyboard [Avocent Dell 03R874] on usb-0000:00:1d.0-2
input: Avocent Dell 03R874 as /class/input/input1
input: USB HID v1.10 Mouse [Avocent Dell 03R874] on usb-0000:00:1d.0-2
usbcore: registered new driver usbhid
/data/work/linux-2.6.18-xen.hg/drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
PM: Adding info for platform:i8042
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
PM: Adding info for serio:serio0
PM: Adding info for serio:serio1
mice: PS/2 mouse device common for all mice
Netfilter messages via NETLINK v0.30.
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
Bridge firewalling registered
Ebtables v2.0 registered
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
Using IPI No-Shortcut mode
ACPI: (supports S0 S1 S4 S5)
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Freeing unused kernel memory: 192k freed
Adding 2650684k swap on /dev/sda5. Priority:-1 extents:1 across:2650684k
EXT3 FS on sda1, internal journal
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
[-- Attachment #4: lspci --]
[-- Type: text/plain, Size: 2899 bytes --]
00:00.0 Host bridge: Intel Corporation 5400 Chipset Memory Controller Hub (rev 20)
00:01.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 1 (rev 20)
00:03.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 3 (rev 20)
00:05.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 5 (rev 20)
00:07.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 7 (rev 20)
00:09.0 PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 9 (rev 20)
00:0f.0 System peripheral: Intel Corporation 5400 Chipset QuickData Technology Device (rev 20)
00:10.0 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
00:10.1 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
00:10.2 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
00:10.3 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
00:10.4 Host bridge: Intel Corporation 5400 Chipset FSB Registers (rev 20)
00:11.0 Host bridge: Intel Corporation 5400 Chipset CE/SF Registers (rev 20)
00:15.0 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
00:15.1 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
00:16.0 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
00:16.1 Host bridge: Intel Corporation 5400 Chipset FBD Registers (rev 20)
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)
00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)
00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)
00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)
00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA IDE Controller (rev 09)
00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)
04:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)
04:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)
05:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)
07:01.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)
07:02.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)
08:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
08:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02)
0a:01.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)
[-- Attachment #5: xmdmesg --]
[-- Type: text/plain, Size: 9064 bytes --]
__ __ _____ _____ _ _ _
\ \/ /___ _ __ |___ / |___ / _ _ _ __ ___| |_ __ _| |__ | | ___
\ // _ \ '_ \ |_ \ |_ \ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
/ \ __/ | | | ___) | ___) |__| |_| | | | \__ \ || (_| | |_) | | __/
/_/\_\___|_| |_| |____(_)____/ \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
(XEN) Xen version 3.3-unstable (t_jeang@uk.xensource.com) (gcc version 4.2.3 (Debian 4.2.3-2)) Thu Mar 27 14:39:56 GMT 2008
(XEN) Latest ChangeSet: Thu Mar 27 09:12:09 2008 +0000 17304:ed67f68ae2a7
(XEN) Command line: com1=115200,8n1 console=com1,vga vtd=1
(XEN) Video information:
(XEN) VGA is text mode 80x25, font 8x16
(XEN) VBE/DDC methods: V2; EDID transfer time: 2 seconds
(XEN) Disc information:
(XEN) Found 1 MBR signatures
(XEN) Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 0000000000099c00 (usable)
(XEN) 0000000000099c00 - 00000000000a0000 (reserved)
(XEN) 00000000000cc000 - 00000000000d0000 (reserved)
(XEN) 00000000000e0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000cff00000 (usable)
(XEN) 00000000cff00000 - 00000000cff0c000 (ACPI data)
(XEN) 00000000cff0c000 - 00000000cff0d000 (ACPI NVS)
(XEN) 00000000cff0d000 - 00000000d0000000 (reserved)
(XEN) 00000000e0000000 - 00000000f0000000 (reserved)
(XEN) 00000000fec00000 - 00000000fec10000 (reserved)
(XEN) 00000000fee00000 - 00000000fee01000 (reserved)
(XEN) 00000000ff000000 - 0000000100000000 (reserved)
(XEN) 0000000100000000 - 0000000230000000 (usable)
(XEN) System RAM: 8190MB (8387172kB)
(XEN) Xen heap: 14MB (14788kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #4 6:15 APIC version 20
(XEN) Processor #1 6:15 APIC version 20
(XEN) Processor #5 6:15 APIC version 20
(XEN) Processor #2 6:15 APIC version 20
(XEN) Processor #6 6:15 APIC version 20
(XEN) Processor #3 6:15 APIC version 20
(XEN) Processor #7 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 9, version 32, address 0xfec86000, GSI 24-47
(XEN) IOAPIC[2]: apic_id 10, version 32, address 0xfec89000, GSI 48-71
(XEN) Enabling APIC mode: Flat. Using 3 I/O APICs
(XEN) Intel VT-d has been enabled
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) iommu_alloc: iommu->reg = ffff828bfff58000 drhd->address = fe71a000
(XEN) iommu_alloc: cap = 4900800c2f0462
(XEN) iommu_alloc: ecap = e01
(XEN) iommu_alloc: iommu->reg = ffff828bfff57000 drhd->address = fe719000
(XEN) iommu_alloc: cap = 900800c2f0462
(XEN) iommu_alloc: ecap = e01
(XEN) iommu_alloc: iommu->reg = ffff828bfff56000 drhd->address = fe716000
(XEN) iommu_alloc: cap = 900800c2f0462
(XEN) iommu_alloc: ecap = e01
(XEN) iommu_alloc: iommu->reg = ffff828bfff55000 drhd->address = fe714000
(XEN) iommu_alloc: cap = 900800c2f0462
(XEN) iommu_alloc: ecap = e01
(XEN) iommu_alloc: iommu->reg = ffff828bfff54000 drhd->address = fe712000
(XEN) iommu_alloc: cap = 900800c2f0462
(XEN) iommu_alloc: ecap = e01
(XEN) iommu_alloc: iommu->reg = ffff828bfff53000 drhd->address = fe710000
(XEN) iommu_alloc: cap = 900800c2f0462
(XEN) iommu_alloc: ecap = e01
(XEN) iommu_alloc: iommu->reg = ffff828bfff52000 drhd->address = fe718000
(XEN) iommu_alloc: cap = 900800c2f0462
(XEN) iommu_alloc: ecap = e01
(XEN) Detected 2800.165 MHz processor.
(XEN) HVM: VMX enabled
(XEN) CPU0: Intel(R) Xeon(R) CPU X5376 @ 2.80GHz stepping 0b
(XEN) Booting processor 1/4 eip 8c000
(XEN) CPU1: Intel(R) Xeon(R) CPU X5376 @ 2.80GHz stepping 0b
(XEN) Booting processor 2/1 eip 8c000
(XEN) CPU2: Intel(R) Xeon(R) CPU X5376 @ 2.80GHz stepping 0b
(XEN) Booting processor 3/5 eip 8c000
(XEN) CPU3: Intel(R) Xeon(R) CPU X5376 @ 2.80GHz stepping 0b
(XEN) Booting processor 4/2 eip 8c000
(XEN) CPU4: Intel(R) Xeon(R) CPU X5376 @ 2.80GHz stepping 0b
(XEN) Booting processor 5/6 eip 8c000
(XEN) CPU5: Intel(R) Xeon(R) CPU X5376 @ 2.80GHz stepping 0b
(XEN) Booting processor 6/3 eip 8c000
(XEN) CPU6: Intel(R) Xeon(R) CPU X5376 @ 2.80GHz stepping 0b
(XEN) Booting processor 7/7 eip 8c000
(XEN) CPU7: Intel(R) Xeon(R) CPU X5376 @ 2.80GHz stepping 0b
(XEN) Total of 8 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) Platform timer overflows in 234 jiffies.
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) Brought up 8 CPUs
(XEN) [VT-D]iommu.c:1324:d32767 context_context_mapping: nested PCI bridge not supported: bdf = 0:7:0 sec_bus = 4 sub_bus = 7
(XEN) [VT-D]iommu.c:1324:d32767 context_context_mapping: nested PCI bridge not supported: bdf = 4:0:0 sec_bus = 5 sub_bus = 6
(XEN) [VT-D]iommu.c:1346:d32767 domain_context_mapping:bus2bridge[7].bus != 0
(XEN) [VT-D]iommu.c:1346:d32767 domain_context_mapping:bus2bridge[7].bus != 0
(XEN) [VT-D]iommu.c:1178:d32767 domain_context_mapping_one:context present:bdf=4:0:3
(XEN) [VT-D]iommu.c:1178:d32767 domain_context_mapping_one:context present:bdf=7:0:0
(XEN) [VT-D]iommu.c:1178:d32767 domain_context_mapping_one:context present:bdf=7:0:1
(XEN) [VT-D]iommu.c:1178:d32767 domain_context_mapping_one:context present:bdf=7:0:2
(XEN) [VT-D]iommu.c:1178:d32767 domain_context_mapping_one:context present:bdf=7:0:3
(XEN) [VT-D]iommu.c:1178:d32767 domain_context_mapping_one:context present:bdf=7:0:4
(XEN) [VT-D]iommu.c:1899: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1903: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1899: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1903: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1899: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1903: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1899: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1903: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1899: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1903: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1899: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1903: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1899: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1903: Interrupt Remapping hardware not found
(XEN) AMD IOMMU: Disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc0100000 -> 0xc0581b28
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000226000000->0000000227000000 (2021601 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: 00000000c0100000->00000000c0581b28
(XEN) Init. ramdisk: 00000000c0582000->00000000c0582000
(XEN) Phys-Mach map: 00000000c0582000->00000000c0d3c384
(XEN) Start info: 00000000c0d3d000->00000000c0d3d4a4
(XEN) Page tables: 00000000c0d3e000->00000000c0d4c000
(XEN) Boot stack: 00000000c0d4c000->00000000c0d4d000
(XEN) TOTAL: 00000000c0000000->00000000c1000000
(XEN) ENTRY ADDRESS: 00000000c0100000
(XEN) Dom0 has maximum 8 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 108kB init memory.
(XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=4
(XEN) ioapic_guest_write: old_entry=000009f1, new_entry=000109f1
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) [VT-D]iommu.c:883: iommu_page_fault: iommu->reg = ffff828bfff52000
(XEN) [VT-D]iommu.c:855: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Read: 0:1f.1 addr cfef9000 REASON 2 iommu->reg = ffff828bfff52000
(XEN) print_vtd_entries: domain_id = 7fff bdf = 0:1f:1 gmfn = cfef9
(XEN) hg->pgd == NULL
(XEN) [VT-D]iommu.c:883: iommu_page_fault: iommu->reg = ffff828bfff52000
(XEN) [VT-D]iommu.c:855: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Read: 0:1f.1 addr cfef9000 REASON 2 iommu->reg = ffff828bfff52000
(XEN) print_vtd_entries: domain_id = 7fff bdf = 0:1f:1 gmfn = cfef9
(XEN) hg->pgd == NULL
(XEN) [VT-D]iommu.c:883: iommu_page_fault: iommu->reg = ffff828bfff52000
(XEN) [VT-D]iommu.c:855: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Read: 0:1f.1 addr cfef9000 REASON 2 iommu->reg = ffff828bfff52000
(XEN) print_vtd_entries: domain_id = 7fff bdf = 0:1f:1 gmfn = cfef9
(XEN) hg->pgd == NULL
(XEN) [VT-D]iommu.c:883: iommu_page_fault: iommu->reg = ffff828bfff52000
(XEN) [VT-D]iommu.c:855: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Read: 0:1f.1 addr cfef9000 REASON 2 iommu->reg = ffff828bfff52000
(XEN) print_vtd_entries: domain_id = 7fff bdf = 0:1f:1 gmfn = cfef9
(XEN) hg->pgd == NULL
[-- Attachment #6: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pci pass-through, NIC card
2008-03-27 15:30 pci pass-through, NIC card Jean Guyader
@ 2008-03-28 11:16 ` Jean Guyader
2008-03-28 17:29 ` Kay, Allen M
0 siblings, 1 reply; 7+ messages in thread
From: Jean Guyader @ 2008-03-28 11:16 UTC (permalink / raw)
To: xen-devel
Jean Guyader wrote:
> Hi,
>
> I am trying to make the vt-d and pci pass-through work and I have some
> problems. I just try to give a NIC to an HVM guest.
>
> When I create the vm the hypervisor goes to an infinite loop,
> it displays in loop the message enclosed (console_on_xm_create).
>
> I use xen x86_64, debian etch dom0 with linux-2.6.18.8-xen 32.
> The hvm guest is a debian etch 64.
>
>
I have the same result with xen-3.2.0.
--
Jean Guyader
^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: pci pass-through, NIC card
2008-03-28 11:16 ` Jean Guyader
@ 2008-03-28 17:29 ` Kay, Allen M
2008-03-28 17:50 ` Jean Guyader
0 siblings, 1 reply; 7+ messages in thread
From: Kay, Allen M @ 2008-03-28 17:29 UTC (permalink / raw)
To: Jean Guyader, xen-devel
Does this happen during xen/dom0 boot time or during HVM guest boot?
Are you using and desktop or server platform? Are you using the latest
BIOS? Some older BIOS does not initialize VT-d HW properly.
Allen
>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com
>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of
>Jean Guyader
>Sent: Friday, March 28, 2008 4:16 AM
>To: xen-devel@lists.xensource.com
>Subject: Re: [Xen-devel] pci pass-through, NIC card
>
>Jean Guyader wrote:
>> Hi,
>>
>> I am trying to make the vt-d and pci pass-through work and I
>have some
>> problems. I just try to give a NIC to an HVM guest.
>>
>> When I create the vm the hypervisor goes to an infinite loop,
>> it displays in loop the message enclosed (console_on_xm_create).
>>
>> I use xen x86_64, debian etch dom0 with linux-2.6.18.8-xen 32.
>> The hvm guest is a debian etch 64.
>>
>>
>
>I have the same result with xen-3.2.0.
>
>--
>Jean Guyader
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pci pass-through, NIC card
2008-03-28 17:29 ` Kay, Allen M
@ 2008-03-28 17:50 ` Jean Guyader
2008-03-28 18:37 ` Kay, Allen M
0 siblings, 1 reply; 7+ messages in thread
From: Jean Guyader @ 2008-03-28 17:50 UTC (permalink / raw)
To: Kay, Allen M; +Cc: xen-devel
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
Kay, Allen M wrote:
> Does this happen during xen/dom0 boot time or during HVM guest boot?
>
> Are you using and desktop or server platform? Are you using the latest
> BIOS? Some older BIOS does not initialize VT-d HW properly.
>
> Allen
>
It's a server platform, I could indeed check if it is the latest bios.
This is happen during the HVM guest boot, all initialisation in dom0 are
ok. The device I tried to pass-through was a pci NIC.
I have tried to pass-through a PCIe NIC and it works better, I mean the
hvm guest boot. The NIC card is well detected by the hvm guest but,
there is still a problem. When I tried to get an ip address from dhcp I
received a storm of "iommu_page_fault" (enclosed the log).
The pci device I try to pass-through is at the address 8:0:0.
I have disable the pci msi in the guest.
Thanks,
--
Jean Guyader
[-- Attachment #2: iommu_page_fault --]
[-- Type: text/plain, Size: 697 bytes --]
(XEN) [VT-D]iommu.c:882: iommu_page_fault: iommu->reg = ffff828bfff57000
(XEN) [VT-D]iommu.c:854: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Read: 8:0.0 addr eb0f000 REASON c iommu->reg = ffff828bfff57000
(XEN) print_vtd_entries: domain_id = 7fff bdf = 8:0:0 gmfn = eb0f
(XEN) hg->pgd == NULL
(XEN) [VT-D]io.c:265:d1 hvm_dpci_eoi:: mirq = 14
(XEN) [VT-D]iommu.c:882: iommu_page_fault: iommu->reg = ffff828bfff57000
(XEN) [VT-D]iommu.c:854: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:839: iommu_fault:DMA Read: 8:0.0 addr eb0f000 REASON c iommu->reg = ffff828bfff57000
(XEN) print_vtd_entries: domain_id = 7fff bdf = 8:0:0 gmfn = eb0f
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: pci pass-through, NIC card
2008-03-28 17:50 ` Jean Guyader
@ 2008-03-28 18:37 ` Kay, Allen M
2008-03-28 18:51 ` Jean Guyader
2008-03-31 16:59 ` Jean Guyader
0 siblings, 2 replies; 7+ messages in thread
From: Kay, Allen M @ 2008-03-28 18:37 UTC (permalink / raw)
To: Jean Guyader; +Cc: Li, Haicheng, You, Yongkang, xen-devel, Han, Weidong
I would assume you see "Intel VT-d has been enabled" in you full log
file, correct?
Given that dom0 devices are working OK - this means VT-d translation is
working correctly for dom0.
The current code maps entire guest memory in VT-d by sharing with p2m
table. The vt-d page fault you are seeing should only happen if the
guest is using some DMA address that is not coverred by the P2m page
table - which is shouldn't have happened.
I have seen this type of fault if the BIOS is not programming VT-d HW
correctly.
Who's the vendor of this Stoakley system? We can try to duplicate the
problem here if we can get hold of the same system.
Allen
>-----Original Message-----
>From: Jean Guyader [mailto:jean.guyader@eu.citrix.com]
>Sent: Friday, March 28, 2008 10:50 AM
>To: Kay, Allen M
>Cc: xen-devel@lists.xensource.com
>Subject: Re: [Xen-devel] pci pass-through, NIC card
>
>Kay, Allen M wrote:
>> Does this happen during xen/dom0 boot time or during HVM guest boot?
>>
>> Are you using and desktop or server platform? Are you using
>the latest
>> BIOS? Some older BIOS does not initialize VT-d HW properly.
>>
>> Allen
>>
>
>It's a server platform, I could indeed check if it is the latest bios.
>
>This is happen during the HVM guest boot, all initialisation
>in dom0 are
>ok. The device I tried to pass-through was a pci NIC.
>
>I have tried to pass-through a PCIe NIC and it works better, I
>mean the
>hvm guest boot. The NIC card is well detected by the hvm guest but,
>there is still a problem. When I tried to get an ip address
>from dhcp I
>received a storm of "iommu_page_fault" (enclosed the log).
>
>The pci device I try to pass-through is at the address 8:0:0.
>
>I have disable the pci msi in the guest.
>
>Thanks,
>
>--
>Jean Guyader
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pci pass-through, NIC card
2008-03-28 18:37 ` Kay, Allen M
@ 2008-03-28 18:51 ` Jean Guyader
2008-03-31 16:59 ` Jean Guyader
1 sibling, 0 replies; 7+ messages in thread
From: Jean Guyader @ 2008-03-28 18:51 UTC (permalink / raw)
To: Kay, Allen M; +Cc: Li, Haicheng, You, Yongkang, xen-devel, Han, Weidong
Kay, Allen M wrote:
> I would assume you see "Intel VT-d has been enabled" in you full log
> file, correct?
>
Yes, there is this line.
> Given that dom0 devices are working OK - this means VT-d translation is
> working correctly for dom0.
>
> The current code maps entire guest memory in VT-d by sharing with p2m
> table. The vt-d page fault you are seeing should only happen if the
> guest is using some DMA address that is not coverred by the P2m page
> table - which is shouldn't have happened.
>
> I have seen this type of fault if the BIOS is not programming VT-d HW
> correctly.
>
> Who's the vendor of this Stoakley system? We can try to duplicate the
> problem here if we can get hold of the same system.
Here, the reference of the machine :
Phoenix TrustedCore(tm) Server
Copyright 1985-2007 Phoenix Technologies Ltd.
All Rights Reserved
Supermicro X7DWE+/X7DWN+ BIOS Rev 1.0
CPU = 2 Processor(s) Detected, Cores per Processor = 4
Intel(R) Xeon(R) CPU X5376 @ 2.80GHz
Intel(R) Xeon(R) CPU X5376 @ 2.80GHz
DRAM Type : DDR2-800, FSB at 1600MHz
8192M System RAM Passed
8192 KB L2 Cache
System BIOS shadowed
Video BIOS shadowed
Fixed Disk 0: Maxtor 6Y160M0
ATAPI CD-ROM: MATSHITADVD-ROM SR-8178
--
Jean Guyader
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pci pass-through, NIC card
2008-03-28 18:37 ` Kay, Allen M
2008-03-28 18:51 ` Jean Guyader
@ 2008-03-31 16:59 ` Jean Guyader
1 sibling, 0 replies; 7+ messages in thread
From: Jean Guyader @ 2008-03-31 16:59 UTC (permalink / raw)
To: Kay, Allen M
Cc: Li, Haicheng, xen-devel, Han, Weidong, Ian Pratt, You, Yongkang,
Keir Fraser
Kay, Allen M wrote:
> I would assume you see "Intel VT-d has been enabled" in you full log
> file, correct?
>
> Given that dom0 devices are working OK - this means VT-d translation is
> working correctly for dom0.
>
> The current code maps entire guest memory in VT-d by sharing with p2m
> table. The vt-d page fault you are seeing should only happen if the
> guest is using some DMA address that is not coverred by the P2m page
> table - which is shouldn't have happened.
>
> I have seen this type of fault if the BIOS is not programming VT-d HW
> correctly.
>
> Who's the vendor of this Stoakley system? We can try to duplicate the
> problem here if we can get hold of the same system.
>
> Allen
>
>> -----Original Message-----
>> From: Jean Guyader [mailto:jean.guyader@eu.citrix.com]
>> Sent: Friday, March 28, 2008 10:50 AM
>> To: Kay, Allen M
>> Cc: xen-devel@lists.xensource.com
>> Subject: Re: [Xen-devel] pci pass-through, NIC card
>>
>> Kay, Allen M wrote:
>>> Does this happen during xen/dom0 boot time or during HVM guest boot?
>>>
>>> Are you using and desktop or server platform? Are you using
>> the latest
>>> BIOS? Some older BIOS does not initialize VT-d HW properly.
>>>
>>> Allen
>>>
>> It's a server platform, I could indeed check if it is the latest bios.
>>
>> This is happen during the HVM guest boot, all initialisation
>> in dom0 are
>> ok. The device I tried to pass-through was a pci NIC.
>>
>> I have tried to pass-through a PCIe NIC and it works better, I
>> mean the
>> hvm guest boot. The NIC card is well detected by the hvm guest but,
>> there is still a problem. When I tried to get an ip address
>>from dhcp I
>> received a storm of "iommu_page_fault" (enclosed the log).
>>
>> The pci device I try to pass-through is at the address 8:0:0.
>>
>> I have disable the pci msi in the guest.
>>
>> Thanks,
>>
May be it fails because, the NIC I tried to pass-through is not a PCie
e1000 card. The MIC card is a 82575EB and it works fine in dom0 with the
igb driver (http://sourceforge.net/project/showfiles.php?group_id=42302).
--
Jean Guyader
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2008-03-31 16:59 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-03-27 15:30 pci pass-through, NIC card Jean Guyader
2008-03-28 11:16 ` Jean Guyader
2008-03-28 17:29 ` Kay, Allen M
2008-03-28 17:50 ` Jean Guyader
2008-03-28 18:37 ` Kay, Allen M
2008-03-28 18:51 ` Jean Guyader
2008-03-31 16:59 ` Jean Guyader
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.