PCI Passthrough throwing strange errors

B

bleomycin

Renowned Member
Mar 20, 2011
49
7
73
I've been running proxmox for some time now with great success passing through 2x M1015 controllers to a VM. Tonight I upgraded the machine replacing the motherboard, cpu and memory. When I launch the VM the M1015's are being passed through to the VM but this error is being thrown, is this something to be concerned about?:

Code: 
kvm: -device pci-assign,host=02:00.0,id=hostpci0,bus=pci.0,addr=0x10: pci-assign: Cannot read from host /sys/bus/pci/devices/0000:02:00.0/romDevice option ROM contents are probably invalid (check dmesg).
Skip option ROM probe with rombar=0, or load from file with romfile=
kvm: -device pci-assign,host=01:00.0,id=hostpci1,bus=pci.0,addr=0x11: Host-side INTx sharing not supported, using MSI instead
Some devices do not work properly in this mode.
kvm: -device pci-assign,host=01:00.0,id=hostpci1,bus=pci.0,addr=0x11: pci-assign: Cannot read from host /sys/bus/pci/devices/0000:01:00.0/rom
Device option ROM contents are probably invalid (check dmesg).
Skip option ROM probe with rombar=0, or load from file with romfile=
TASK OK

Code: 
pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-9
libpve-access-control: 3.0-8
libpve-storage-perl: 3.0-18
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

Code: 
bootdisk: virtio0
cores: 3
hostpci0: 02:00.0
hostpci1: 01:00.0
ide2: none,media=cdrom
memory: 8000
name: zfsbuntu
net0: virtio=96:71:24:8E:66:9E,bridge=vmbr0
ostype: l26
sockets: 1
startup: order=2
virtio0: ssd1:101/zfsbuntu.qcow2,format=qcow2

Code: 
dmesg | grep -e DMAR -e IOMMUACPI: DMAR 00000000ddf176f8 00078 (v01 INTEL      SNB  00000001 INTL 00000001)
Intel-IOMMU: enabled
dmar: IOMMU 0: reg_base_addr fed90000 ver 1:0 cap c9008020660262 ecap f010da
IOMMU 0xfed90000: using Queued invalidation
IOMMU: Setting RMRR:
IOMMU: Setting identity map for device 0000:00:1d.0 [0xddd63000 - 0xddd8f000]
IOMMU: Setting identity map for device 0000:00:1a.0 [0xddd63000 - 0xddd8f000]
IOMMU: Prepare 0-16MiB unity mapping for LPC
IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0x1000000]

Full lspci -v here: http://pastebin.com/9N7MR7Dc
Code: 
01:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)    Subsystem: LSI Logic / Symbios Logic Device 3020
    Flags: bus master, fast devsel, latency 0, IRQ 16
    I/O ports at e000 [size=256]
    Memory at f7ec0000 (64-bit, non-prefetchable) [size=16K]
    Memory at f7e80000 (64-bit, non-prefetchable) [size=256K]
    Expansion ROM at f7e00000 [size=512K]
    Capabilities: [50] Power Management version 3
    Capabilities: [68] Express Endpoint, MSI 00
    Capabilities: [d0] Vital Product Data
    Capabilities: [a8] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [c0] MSI-X: Enable+ Count=15 Masked-
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [138] Power Budgeting <?>
    Capabilities: [150] Single Root I/O Virtualization (SR-IOV)
    Capabilities: [190] Alternative Routing-ID Interpretation (ARI)
    Kernel driver in use: pci-stub


02:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
    Subsystem: LSI Logic / Symbios Logic Device 3020
    Flags: bus master, fast devsel, latency 0, IRQ 17
    I/O ports at d000 [size=256]
    Memory at f7dc0000 (64-bit, non-prefetchable) [size=16K]
    Memory at f7d80000 (64-bit, non-prefetchable) [size=256K]
    Expansion ROM at f7d00000 [size=512K]
    Capabilities: [50] Power Management version 3
    Capabilities: [68] Express Endpoint, MSI 00
    Capabilities: [d0] Vital Product Data
    Capabilities: [a8] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [c0] MSI-X: Enable+ Count=15 Masked-
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [138] Power Budgeting <?>
    Capabilities: [150] Single Root I/O Virtualization (SR-IOV)
    Capabilities: [190] Alternative Routing-ID Interpretation (ARI)
    Kernel driver in use: pci-stub

Code: 
mpt2sas1: removing handle(0x000e), sas_addr(0x4433221107000000)mpt2sas1: sending message unit reset !!
mpt2sas1: message unit reset: SUCCESS
mpt2sas 0000:02:00.0: PCI INT A disabled
pci-stub 0000:02:00.0: claimed by stub
pci-stub 0000:02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
pci-stub 0000:02:00.0: restoring config space at offset 0xc (was 0x0, writing 0xf7d00000)
pci-stub 0000:02:00.0: restoring config space at offset 0x7 (was 0x4, writing 0xf7d80004)
pci-stub 0000:02:00.0: restoring config space at offset 0x5 (was 0x4, writing 0xf7dc0004)
pci-stub 0000:02:00.0: restoring config space at offset 0x4 (was 0x1, writing 0xd001)
pci-stub 0000:02:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
pci-stub 0000:02:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100003)
sd 0:0:0:0: [sda] Synchronizing SCSI cache
sd 0:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
mpt2sas0: removing handle(0x0009), sas_addr(0x4433221103000000)
sd 0:0:1:0: [sdb] Synchronizing SCSI cache
sd 0:0:1:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
mpt2sas0: removing handle(0x000a), sas_addr(0x4433221104000000)
sd 0:0:2:0: [sdc] Synchronizing SCSI cache
sd 0:0:2:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
mpt2sas0: removing handle(0x000b), sas_addr(0x4433221106000000)
sd 0:0:3:0: [sdd] Synchronizing SCSI cache
sd 0:0:3:0: [sdd] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
mpt2sas0: removing handle(0x000c), sas_addr(0x4433221105000000)
sd 0:0:4:0: [sde] Synchronizing SCSI cache
sd 0:0:4:0: [sde] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
mpt2sas0: removing handle(0x000d), sas_addr(0x4433221107000000)
mpt2sas0: sending message unit reset !!
mpt2sas0: message unit reset: SUCCESS
mpt2sas 0000:01:00.0: PCI INT A disabled
pci-stub 0000:01:00.0: claimed by stub
pci-stub 0000:01:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
pci-stub 0000:01:00.0: restoring config space at offset 0xc (was 0x0, writing 0xf7e00000)
pci-stub 0000:01:00.0: restoring config space at offset 0x7 (was 0x4, writing 0xf7e80004)
pci-stub 0000:01:00.0: restoring config space at offset 0x5 (was 0x4, writing 0xf7ec0004)
pci-stub 0000:01:00.0: restoring config space at offset 0x4 (was 0x1, writing 0xe001)
pci-stub 0000:01:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
pci-stub 0000:01:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100003)
device tap101i0 entered promiscuous mode
vmbr0: port 2(tap101i0) entering forwarding state
pci-stub 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pci-stub 0000:02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
pci-stub 0000:02:00.0: restoring config space at offset 0xc (was 0x0, writing 0xf7d00000)
pci-stub 0000:02:00.0: restoring config space at offset 0x7 (was 0x4, writing 0xf7d80004)
pci-stub 0000:02:00.0: restoring config space at offset 0x5 (was 0x4, writing 0xf7dc0004)
pci-stub 0000:02:00.0: restoring config space at offset 0x4 (was 0x1, writing 0xd001)
pci-stub 0000:02:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
pci-stub 0000:02:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100003)
assign device: host bdf = 2:0:0
pci-stub 0000:02:00.0: Invalid ROM contents
pci-stub 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci-stub 0000:01:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
pci-stub 0000:01:00.0: restoring config space at offset 0xc (was 0x0, writing 0xf7e00000)
pci-stub 0000:01:00.0: restoring config space at offset 0x7 (was 0x4, writing 0xf7e80004)
pci-stub 0000:01:00.0: restoring config space at offset 0x5 (was 0x4, writing 0xf7ec0004)
pci-stub 0000:01:00.0: restoring config space at offset 0x4 (was 0x1, writing 0xe001)
pci-stub 0000:01:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
pci-stub 0000:01:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100003)
assign device: host bdf = 1:0:0
IRQ handler type mismatch for IRQ 16
current handler: ehci_hcd:usb1
Pid: 3476, comm: kvm veid: 0 Not tainted 2.6.32-26-pve #1
Call Trace:
 [<ffffffff810f23f7>] ? __setup_irq+0x3e7/0x440
 [<ffffffffa0519c90>] ? kvm_assigned_dev_intr+0x0/0xf0 [kvm]
 [<ffffffff810f2534>] ? request_threaded_irq+0xe4/0x1e0
 [<ffffffffa051f38d>] ? kvm_vm_ioctl+0xfed/0x10d0 [kvm]
 [<ffffffff8144fbd1>] ? pci_conf1_read+0xc1/0x120
 [<ffffffff814517e3>] ? raw_pci_read+0x23/0x40
 [<ffffffff812a08ea>] ? pci_read_config+0x25a/0x280
 [<ffffffffa051d83a>] ? kvm_dev_ioctl+0xaa/0x4c0 [kvm]
 [<ffffffff811b45fa>] ? vfs_ioctl+0x2a/0xa0
 [<ffffffff81220076>] ? read+0x166/0x210
 [<ffffffff811b4c2e>] ? do_vfs_ioctl+0x7e/0x570
 [<ffffffff8119fd56>] ? vfs_read+0x116/0x190
 [<ffffffff811b516f>] ? sys_ioctl+0x4f/0x80
 [<ffffffff8100b182>] ? system_call_fastpath+0x16/0x1b
pci-stub 0000:01:00.0: irq 33 for MSI/MSI-X
pci-stub 0000:01:00.0: Invalid ROM contents
pci-stub 0000:02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
pci-stub 0000:02:00.0: restoring config space at offset 0xc (was 0x0, writing 0xf7d00001)
pci-stub 0000:02:00.0: restoring config space at offset 0x7 (was 0x4, writing 0xf7d80004)
pci-stub 0000:02:00.0: restoring config space at offset 0x5 (was 0x4, writing 0xf7dc0004)
pci-stub 0000:02:00.0: restoring config space at offset 0x4 (was 0x1, writing 0xd001)
pci-stub 0000:02:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
pci-stub 0000:02:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100003)
pci-stub 0000:01:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
pci-stub 0000:01:00.0: restoring config space at offset 0xc (was 0x0, writing 0xf7e00001)
pci-stub 0000:01:00.0: restoring config space at offset 0x7 (was 0x4, writing 0xf7e80004)
pci-stub 0000:01:00.0: restoring config space at offset 0x5 (was 0x4, writing 0xf7ec0004)
pci-stub 0000:01:00.0: restoring config space at offset 0x4 (was 0x1, writing 0xe001)
pci-stub 0000:01:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
pci-stub 0000:01:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100403)
pci-stub 0000:01:00.0: irq 33 for MSI/MSI-X
EXT4-fs (sdl1): Unaligned AIO/DIO on inode 2883587 by kvm; performance will be poor.
tap101i0: no IPv6 routers present
pci-stub 0000:02:00.0: irq 33 for MSI/MSI-X
pci-stub 0000:02:00.0: irq 33 for MSI/MSI-X
pci-stub 0000:01:00.0: irq 41 for MSI/MSI-X
pci-stub 0000:01:00.0: irq 41 for MSI/MSI-X
pci-stub 0000:01:00.0: irq 41 for MSI/MSI-X

Thanks!
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back