GPU Passthrough issue with HD7770 Sapphire Flex

M

mcflym

Renowned Member
Jul 10, 2013
195
9
83
Hi there again,

after solving the most problems regarding SAS-Controller PCI-Passthrough i got a new challenge:

PCI-Passthrough of a GPU. For the first look everything looks nice. The Card is shown up in the VM, but after installing the driver (installation says "successful") and rebooting the start of the Card fails:

gpu_error.jpg

sysinfos1.jpg

sysinfos2.jpg

sysinfos3.jpg

This happens with Windows 7 64Bit and Windows 8.1 64Bit.

Edit: Tried it with Ubuntu and got the following error while booting:
gpu_error_ubuntu.jpg

I think there is something wrong passing this device through?!

But on Ubuntu "lspci" shows the Card and even the HDMI Audio adapter...

This thread http://comments.gmane.org/gmane.comp.emulators.kvm.devel/99420 is talking about a ROM-file... whats abput that, do i need this?

The Proxmox host is showing an IRQ Error:
"IRQ handler type mismatch for IRQ 16
current handler : ehci_hcd:usb1"

My lspci-v shows:

Code: 
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller (rev 06)
        Subsystem: Super Micro Computer Inc Device 0804
        Flags: bus master, fast devsel, latency 0
        Capabilities: [e0] Vendor Specific Information: Len=0c <?>


00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) (prog-if 00 [Normal decode])
        Flags: fast devsel
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 0000e000-0000efff
        Memory behind bridge: f7500000-f75fffff
        Prefetchable memory behind bridge: 00000000e0000000-00000000efffffff
        Capabilities: [88] Subsystem: Intel Corporation Device 2010
        Capabilities: [80] Power Management version 3
        Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [a0] Express Root Port (Slot+), MSI 00
        Capabilities: [100] Virtual Channel
        Capabilities: [140] Root Complex Link
        Capabilities: [d94] #19
        Kernel driver in use: pci-stub


00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
        I/O behind bridge: 0000d000-0000dfff
        Memory behind bridge: f7100000-f72fffff
        Capabilities: [88] Subsystem: Intel Corporation Device 2010
        Capabilities: [80] Power Management version 3
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [a0] Express Root Port (Slot+), MSI 00
        Capabilities: [100] Virtual Channel
        Capabilities: [140] Root Complex Link
        Capabilities: [d94] #19
        Kernel driver in use: pcieport


00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) (prog-if 30 [XHCI])
        Subsystem: Super Micro Computer Inc Device 0804
        Flags: bus master, medium devsel, latency 0, IRQ 35
        Memory at f7600000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: [70] Power Management version 2
        Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
        Kernel driver in use: xhci_hcd


00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) (prog-if 20 [EHCI])
        Subsystem: Super Micro Computer Inc Device 0804
        Flags: bus master, medium devsel, latency 0, IRQ 16
        Memory at f7614000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] Debug port: BAR=1 offset=00a0
        Capabilities: [98] PCI Advanced Features
        Kernel driver in use: ehci_hcd


00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=03, subordinate=04, sec-latency=0
        I/O behind bridge: 0000c000-0000cfff
        Memory behind bridge: f6000000-f70fffff
        Capabilities: [40] Express Root Port (Slot+), MSI 00
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [90] Subsystem: Super Micro Computer Inc Device 0804
        Capabilities: [a0] Power Management version 3
        Capabilities: [100] Advanced Error Reporting
        Kernel driver in use: pcieport


00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
        I/O behind bridge: 0000b000-0000bfff
        Memory behind bridge: f7400000-f74fffff
        Capabilities: [40] Express Root Port (Slot+), MSI 00
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [90] Subsystem: Super Micro Computer Inc Device 0804
        Capabilities: [a0] Power Management version 3
        Capabilities: [100] Advanced Error Reporting
        Kernel driver in use: pcieport


00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
        I/O behind bridge: 0000a000-0000afff
        Memory behind bridge: f7300000-f73fffff
        Capabilities: [40] Express Root Port (Slot+), MSI 00
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [90] Subsystem: Super Micro Computer Inc Device 0804
        Capabilities: [a0] Power Management version 3
        Capabilities: [100] Advanced Error Reporting
        Kernel driver in use: pcieport


00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) (prog-if 20 [EHCI])
        Subsystem: Super Micro Computer Inc Device 0804
        Flags: bus master, medium devsel, latency 0, IRQ 23
        Memory at f7613000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] Debug port: BAR=1 offset=00a0
        Capabilities: [98] PCI Advanced Features
        Kernel driver in use: ehci_hcd


00:1f.0 ISA bridge: Intel Corporation C222 Series Chipset Family Server Essential SKU LPC Controller (rev 05)
        Subsystem: Super Micro Computer Inc Device 0804
        Flags: bus master, medium devsel, latency 0
        Capabilities: [e0] Vendor Specific Information: Len=0c <?>


00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) (prog-if 01 [AHCI 1.0])
        Subsystem: Super Micro Computer Inc Device 0804
        Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 38
        I/O ports at f050 [size=8]
        I/O ports at f040 [size=4]
        I/O ports at f030 [size=8]
        I/O ports at f020 [size=4]
        I/O ports at f000 [size=32]
        Memory at f7612000 (32-bit, non-prefetchable) [size=2K]
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [70] Power Management version 3
        Capabilities: [a8] SATA HBA v1.0
        Kernel driver in use: ahci


00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
        Subsystem: Super Micro Computer Inc Device 0804
        Flags: medium devsel, IRQ 18
        Memory at f7611000 (64-bit, non-prefetchable) [size=256]
        I/O ports at 0580 [size=32]
        Kernel driver in use: i801_smbus


00:1f.6 Signal processing controller: Intel Corporation 8 Series Chipset Family Thermal Management Controller (rev 05)
        Subsystem: Super Micro Computer Inc Device 0804
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at f7610000 (64-bit, non-prefetchable) [size=4K]
        Capabilities: [50] Power Management version 3
        Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-


01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770 GHz Edition] (prog-if 00 [VGA controller])
        Subsystem: PC Partner Limited / Sapphire Technology Device e227
        Flags: fast devsel, IRQ 16
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Memory at f7500000 (64-bit, non-prefetchable) [size=256K]
        I/O ports at e000 [size=256]
        Expansion ROM at f7540000 [disabled] [size=128K]
        Capabilities: [48] Vendor Specific Information: Len=08 <?>
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Legacy Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Capabilities: [150] Advanced Error Reporting
        Capabilities: [270] #19
        Kernel driver in use: pci-stub


01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
        Subsystem: PC Partner Limited / Sapphire Technology Device aab0
        Flags: fast devsel, IRQ 17
        Memory at f7560000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [48] Vendor Specific Information: Len=08 <?>
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Legacy Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Capabilities: [150] Advanced Error Reporting
        Kernel driver in use: pci-stub


02:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05)
        Subsystem: Super Micro Computer Inc Device 0691
        Flags: bus master, fast devsel, latency 0, IRQ 16
        I/O ports at d000 [size=256]
        Memory at f7240000 (64-bit, non-prefetchable) [size=64K]
        Memory at f7200000 (64-bit, non-prefetchable) [size=256K]
        Expansion ROM at f7100000 [disabled] [size=1M]
        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=16 Masked-
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [1e0] #19
        Capabilities: [1c0] Power Budgeting <?>
        Capabilities: [190] #16
        Capabilities: [148] Alternative Routing-ID Interpretation (ARI)
        Kernel driver in use: pci-stub


03:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 03) (prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=03, secondary=04, subordinate=04, sec-latency=0
        I/O behind bridge: 0000c000-0000cfff
        Memory behind bridge: f6000000-f70fffff
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [78] Power Management version 3
        Capabilities: [80] Express PCI/PCI-X Bridge, MSI 00
        Capabilities: [a4] Subsystem: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge
        Capabilities: [100] Virtual Channel


04:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30) (prog-if 00 [VGA controller])
        Subsystem: Super Micro Computer Inc Device 0804
        Flags: bus master, medium devsel, latency 0, IRQ 11
        Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
        Memory at f7000000 (32-bit, non-prefetchable) [size=128K]
        I/O ports at c000 [size=128]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/4 Maskable- 64bit+


05:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
        Subsystem: Super Micro Computer Inc Device 1533
        Flags: bus master, fast devsel, latency 0, IRQ 18
        Memory at f7400000 (32-bit, non-prefetchable) [size=512K]
        I/O ports at b000 [size=32]
        Memory at f7480000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
        Capabilities: [70] MSI-X: Enable+ Count=5 Masked-
        Capabilities: [a0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 00-25-90-ff-ff-f0-04-78
        Capabilities: [1a0] Transaction Processing Hints
        Kernel driver in use: igb


06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
        Subsystem: Super Micro Computer Inc Device 1533
        Flags: bus master, fast devsel, latency 0, IRQ 19
        Memory at f7300000 (32-bit, non-prefetchable) [size=512K]
        I/O ports at a000 [size=32]
        Memory at f7380000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
        Capabilities: [70] MSI-X: Enable+ Count=5 Masked-
        Capabilities: [a0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 00-25-90-ff-ff-f0-04-79
        Capabilities: [1a0] Transaction Processing Hints
        Kernel driver in use: igb

lspci -t:

Code: 
-[0000:00]-+-00.0           +-01.0-[01]--+-00.0
           |            \-00.1
           +-01.1-[02]----00.0
           +-14.0
           +-1a.0
           +-1c.0-[03-04]----00.0-[04]----00.0
           +-1c.2-[05]----00.0
           +-1c.3-[06]----00.0
           +-1d.0
           +-1f.0
           +-1f.2
           +-1f.3
           \-1f.6

I have blacklisted the passthrough hardware in the /etc/modprobe/fbdev-blacklist.conf

Code: 
#SAS Controller
blacklist pci-stub
#Radeon Grafikkarte
blacklist radeon
#Radeon Sound
blacklist snd_hda_intel

But: this error is shown up if i start the VM with die SAS-Controller too (the controller is working und debian).

In this thread somebody got the same error: http://unix.stackexchange.com/quest...e-43-with-kvm-and-libvirt-on-all-amd-hardware

cat /proc/interrupts shows:


" 16: 24 0 0 0 0 0 0 0 IR-IO-APIC-fasteoi ehci_hcd:usb1"

i released usb1 from IRQ16 and started my VM... no error message on host anymore, but VM didn`t worked as well :(

Or what`s about vfio-bind?

The "info pci" of this VM:
Code: 
qm> info pci  Bus  0, device   0, function 0:
    Host bridge: PCI device 8086:1237
      id ""
  Bus  0, device   1, function 0:
    ISA bridge: PCI device 8086:7000
      id ""
  Bus  0, device   1, function 1:
    IDE controller: PCI device 8086:7010
      BAR4: I/O at 0xc1a0 [0xc1af].
      id ""
  Bus  0, device   1, function 2:
    USB controller: PCI device 8086:7020
      IRQ 11.
      BAR4: I/O at 0xc140 [0xc15f].
      id "uhci"
  Bus  0, device   1, function 3:
    Bridge: PCI device 8086:7113
      IRQ 9.
      id ""
  Bus  0, device   2, function 0:
    VGA controller: PCI device 1234:1111
      BAR0: 32 bit prefetchable memory at 0xfd000000 [0xfdffffff].
      BAR2: 32 bit memory at 0xf0070000 [0xf0070fff].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe].
      id ""
  Bus  0, device   3, function 0:
    Class 0255: PCI device 1af4:1002
      IRQ 10.
      BAR0: I/O at 0xc160 [0xc17f].
      id "balloon0"
  Bus  0, device  10, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 0.
      BAR0: I/O at 0xc100 [0xc13f].
      BAR1: 32 bit memory at 0xf0071000 [0xf0071fff].
      id "virtio0"
  Bus  0, device  16, function 0:
    VGA controller: PCI device 1002:683d
      IRQ 11.
      BAR0: 64 bit memory at 0xe0000000 [0xefffffff].
      BAR2: 64 bit memory at 0xf0000000 [0xf003ffff].
      BAR4: I/O at 0xc000 [0xc0ff].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0001fffe].
      id "hostpci0"
  Bus  0, device  18, function 0:
    Ethernet controller: PCI device 1af4:1000
      IRQ 0.
      BAR0: I/O at 0xc180 [0xc19f].
      BAR1: 32 bit memory at 0xf0072000 [0xf0072fff].
      id "net0"

The syslog shows the following after starting the VM:

Code: 
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:52 proxmox pvedaemon[9200]: start VM 109: UPID:proxmox:000023F0:0018B56C:5336BAE0:qmstart:109:root@pam:[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:52 proxmox pvedaemon[4587]: <root@pam> starting task UPID:proxmox:000023F0:0018B56C:5336BAE0:qmstart:109:root@pam:[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:52 proxmox kernel: pci-stub 0000:01:00.0: restoring config space at offset 0x1 (was 0x100400, writing 0x100003)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:52 proxmox kernel: pci-stub 0000:01:00.1: restoring config space at offset 0x1 (was 0x100400, writing 0x100403)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:52 proxmox kernel: device tap109i0 entered promiscuous mode[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:52 proxmox kernel: vmbr1: port 4(tap109i0) entering forwarding state[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: pci-stub 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: pci-stub 0000:01:00.0: restoring config space at offset 0x1 (was 0x100400, writing 0x100003)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: assign device: host bdf = 1:0:0[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: IRQ handler type mismatch for IRQ 16[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: current handler: ehci_hcd:usb1[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: Pid: 9205, comm: kvm veid: 0 Not tainted 2.6.32-27-pve #1[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: Call Trace:[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffff810f2477>] ? __setup_irq+0x3e7/0x440[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffffa0469c90>] ? kvm_assigned_dev_intr+0x0/0xf0 [kvm][/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffff810f25b4>] ? request_threaded_irq+0xe4/0x1e0[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffffa046f38d>] ? kvm_vm_ioctl+0xfed/0x10d0 [kvm][/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffff8144fe31>] ? pci_conf1_read+0xc1/0x120[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffff81451a43>] ? raw_pci_read+0x23/0x40[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffff812a0b1a>] ? pci_read_config+0x25a/0x280[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffffa046d83a>] ? kvm_dev_ioctl+0xaa/0x4c0 [kvm][/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffff811b45aa>] ? vfs_ioctl+0x2a/0xa0[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffff812202a6>] ? read+0x166/0x210[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffff811b4bde>] ? do_vfs_ioctl+0x7e/0x5a0[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffff8119fe86>] ? vfs_read+0x116/0x190[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffff811b514f>] ? sys_ioctl+0x4f/0x80[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: [<ffffffff8100b182>] ? system_call_fastpath+0x16/0x1b[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: pci-stub 0000:01:00.0: irq 40 for MSI/MSI-X[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: pci-stub 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: pci-stub 0000:01:00.1: restoring config space at offset 0x1 (was 0x100400, writing 0x100403)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:53 proxmox kernel: assign device: host bdf = 1:0:1[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:54 proxmox kernel: pci-stub 0000:01:00.0: restoring config space at offset 0x1 (was 0x100400, writing 0x100403)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:54 proxmox kernel: pci-stub 0000:01:00.1: restoring config space at offset 0x1 (was 0x100400, writing 0x100403)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:54 proxmox pvedaemon[4587]: <root@pam> end task UPID:proxmox:000023F0:0018B56C:5336BAE0:qmstart:109:root@pam: OK[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:54 proxmox kernel: pci-stub 0000:01:00.0: irq 40 for MSI/MSI-X[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:56 proxmox ntpd[2869]: Listen normally on 15 tap109i0 fe80::d1:7cff:feca:1449 UDP 123[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:21:56 proxmox ntpd[2869]: peers refreshed[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:22:03 proxmox kernel: tap109i0: no IPv6 routers present[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:22:06 proxmox kernel: pci-stub 0000:01:00.0: irq 40 for MSI/MSI-X[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 29 13:22:07 proxmox kernel: pci-stub 0000:01:00.0: irq 40 for MSI/MSI-X[/FONT][/COLOR]

pci-stub 0000:01:00.0 = AMD HD7770
pci-stub 0000:01:00.1 = AMD HD Audio

Maybe somebody got the same error in the past and knows what i have to do now?

I tried a lot but for now i am done with it... :(

Or maybe somebody got a GPU Passthrough working with proxmox, so tell me about the model.
 
Last edited:
Is there a way to get the vfio thing working on proxmox? Or is this the way proxmox is doing the passthrough already?

Should i buy another video card for testing? Which model?

Thanks
 
spirit said:
vfio can be done with kernel 3.10,
then in vm.conf

hostpci0: xxxx,driver=vfio
Click to expand...

thanks for your help!

But i get the same error. Maybe syslog helps?

Code: 
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:23 proxmox pvedaemon[70657]: start VM 109: UPID:proxmox:00011401:01181206:533997E3:qmstart:109:root@pam:[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:23 proxmox kernel: pci-stub 0000:01:00.0: restoring config space at offset 0x1 (was 0x100400, writing 0x100003)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:23 proxmox kernel: pci-stub 0000:01:00.1: restoring config space at offset 0x1 (was 0x100400, writing 0x100403)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:23 proxmox kernel: device tap109i0 entered promiscuous mode[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:23 proxmox kernel: vmbr1: port 4(tap109i0) entering forwarding state[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:23 proxmox kernel: pci-stub 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:23 proxmox kernel: pci-stub 0000:01:00.0: restoring config space at offset 0x1 (was 0x100400, writing 0x100003)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: assign device: host bdf = 1:0:0[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: IRQ handler type mismatch for IRQ 16[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: current handler: ehci_hcd:usb1[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: Pid: 70662, comm: kvm veid: 0 Not tainted 2.6.32-27-pve #1[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: Call Trace:[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffff810f2477>] ? __setup_irq+0x3e7/0x440[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffffa042fc90>] ? kvm_assigned_dev_intr+0x0/0xf0 [kvm][/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffff810f25b4>] ? request_threaded_irq+0xe4/0x1e0[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffffa043538d>] ? kvm_vm_ioctl+0xfed/0x10d0 [kvm][/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffff8144fe31>] ? pci_conf1_read+0xc1/0x120[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffff81451a43>] ? raw_pci_read+0x23/0x40[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffff812a0b1a>] ? pci_read_config+0x25a/0x280[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffffa043383a>] ? kvm_dev_ioctl+0xaa/0x4c0 [kvm][/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffff811b45aa>] ? vfs_ioctl+0x2a/0xa0[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffff812202a6>] ? read+0x166/0x210[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffff811b4bde>] ? do_vfs_ioctl+0x7e/0x5a0[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffff8119fe86>] ? vfs_read+0x116/0x190[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffff811b514f>] ? sys_ioctl+0x4f/0x80[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: [<ffffffff8100b182>] ? system_call_fastpath+0x16/0x1b[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel:  alloc irq_desc for 42 on node -1[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel:  alloc kstat_irqs on node -1[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: alloc irq_2_iommu on node -1[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: pci-stub 0000:01:00.0: irq 42 for MSI/MSI-X[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: pci-stub 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: pci-stub 0000:01:00.1: restoring config space at offset 0x1 (was 0x100400, writing 0x100403)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: assign device: host bdf = 1:0:1[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: pci-stub 0000:01:00.0: restoring config space at offset 0x1 (was 0x100400, writing 0x100403)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: pci-stub 0000:01:00.1: restoring config space at offset 0x1 (was 0x100400, writing 0x100403)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox pvedaemon[2991]: <root@pam> end task UPID:proxmox:00011401:01181206:533997E3:qmstart:109:root@pam: OK[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:24 proxmox kernel: pci-stub 0000:01:00.0: irq 42 for MSI/MSI-X[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:27 proxmox ntpd[2698]: Listen normally on 15 tap109i0 fe80::8013:87ff:fe87:b75d UDP 123[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:27 proxmox ntpd[2698]: peers refreshed[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:28 proxmox kernel: EXT4-fs (sda1): Unaligned AIO/DIO on inode 4980739 by kvm; performance will be poor.[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:28 proxmox pvedaemon[70682]: starting vnc proxy UPID:proxmox:0001141A:01181438:533997E8:vncproxy:109:root@pam:[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:28 proxmox pvedaemon[2989]: <root@pam> starting task UPID:proxmox:0001141A:01181438:533997E8:vncproxy:109:root@pam:[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:28 proxmox pvedaemon[2989]: <root@pam> successful auth for user 'root@pam'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:33 proxmox kernel: tap109i0: no IPv6 routers present[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:36 proxmox kernel: pci-stub 0000:01:00.0: irq 42 for MSI/MSI-X[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Mar 31 18:29:37 proxmox kernel: pci-stub 0000:01:00.0: irq 42 for MSI/MSI-X[/FONT][/COLOR]
 
Hi,
I found doc here:
https://bbs.archlinux.org/viewtopic.php?id=162768

seem that is require more flag (x-vga=on)
-device vfio-pci,host=07:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on

also need
-M q35 to enable pci-express in vm

so it don't work currently with proxmox.

Don't have time to work in this for now, q35 will require a lot of work.
 
spirit said:
Hi,
I found doc here:
https://bbs.archlinux.org/viewtopic.php?id=162768

seem that is require more flag (x-vga=on)
-device vfio-pci,host=07:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on

also need
-M q35 to enable pci-express in vm

so it don't work currently with proxmox.

Don't have time to work in this for now, q35 will require a lot of work.
Click to expand...

Ok, one last question then:

When do you think will it be available (or never?) and is there any other option to get a GPU-passthrough working on proxmox?

Thank you!
 
mcflym said:
Ok, one last question then:

When do you think will it be available (or never?) and is there any other option to get a GPU-passthrough working on proxmox?

Thank you!
Click to expand...

Well, I think we'll give some love when the final 3.10 redhat kernel will be released.
Currently we are working on proxmox firewall feature, and it's take a lot of time.

But I think in some months, no problemo. (Beta testers will be needed ;)
 
spirit said:
Well, I think we'll give some love when the final 3.10 redhat kernel will be released.
Currently we are working on proxmox firewall feature, and it's take a lot of time.

But I think in some months, no problemo. (Beta testers will be needed ;)
Click to expand...

Please let me know as soon as you are start developing this feature! :) (I'm planning to set up a Windows-Gaming-VM in order to use Steam in home streaming).

Don't forget me ;)

Thanks!
 
mcflym said:
Please let me know as soon as you are start developing this feature! :) (I'm planning to set up a Windows-Gaming-VM in order to use Steam in home streaming).

Don't forget me ;)

Thanks!
Click to expand...

Sure no problem. Can you fill a proxmox bugzilla ? like this, I won't forget it ;)
 
I think that shouldn't be a problem :) i will create a topic in bugzilla then ;)

Gesendet von meinem XT890 mit Tapatalk
 
Some news about it?

No Status-Update on bugzilla... will it ever discovered by the developer? :)
 
mcflym said:
Some news about it?

No Status-Update on bugzilla... will it ever discovered by the developer? :)
Click to expand...

Hi, I'm going to push soon qemu q35 machine model. (to be able to support pci-e device inside guest).
But we are a bit busy with pve-firewall for the moment.
after q35 support, we need to add support for vfio-vga support.
And it should work.
(we need kernel 3.10 + vfio + vfio-vga + q35 machine model)
 
Well, that sounds good! But i am not so deep into Linux to compile (that is necessary for testing the git things?) the new modules... or is there a easy way for Linux dummies like me?

Thanks!

Gesendet von meinem XT890 mit Tapatalk
 
spirit said:
qemu q35 model (for pcie) + vfio support are already done in git repository.
It's just need a little work to add support for vfio-vga.

So I think it should be ready soon ;)


(Help is welcome to test it)
Click to expand...

Saw on git.proxmox.com:

"add pcie and x-vga passthrough"

and

"add pci multifunction support"

How can i test this great sh** :D ?
 
mcflym said:
Saw on git.proxmox.com:

"add pcie and x-vga passthrough"

and

"add pci multifunction support"

How can i test this great sh** :D ?
Click to expand...

Ok, indeed, all should be ready . I think you need to test gpu passthrough ?

you need to compile yourself packages from proxmox git currently, at least :

- last pve-kernel-3.10 from git
- last qemu-server from git

(maybe they are also other dependencies like pve-firewall,I'm not sure about it)

then vm config file

Code: 
machine: q35
hostpci0: host=00:00.0,x-vga=on,pcie=1

replace 00:00.0 by your vga card pci addres. (do an lspci).


or if you have gpu+audio on the same card (00:00.0 and 00:00.1 for example)

Code: 
machine: q35
hostpci0: host=00:00,x-vga=on,pcie=1

(remove the .0 , it'll passthrough for each sub function)


that's all !

(of course, boot on 3.10 kernel,and follow config like in https://pve.proxmox.com/wiki/Pci_passthrough)
 
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