Issues when plugging in PCIe devices.

J

Jackster

Active Member
Nov 12, 2014
23
0
41
Hi all.

Pretty new to Proxmox (use to use it on a server 6-7 years ago but just ran a load of Linux containers back then).


I have a new setup at home so I can have multiple server OS' running for different stuff I need to run.

One of the servers I run needs USB3 and a GPU so I added one of each and set my motherboard to only use the integrated iGPU.
On boot, Proxmox starts but there is no network?

Here is the kernel for the boot with just a GPU in.
https://pastebin.com/ZLuG9REn

I have removed these devices and on boot have these errors in the console.
Code: 
root@proxmox:~# journalctl -p err -b
-- Logs begin at Tue 2020-05-05 17:04:26 BST, end at Tue 2020-05-05 17:12:30 BST. --
May 05 17:04:26 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)
May 05 17:04:26 proxmox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190703/psparse-531)
May 05 17:04:26 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)
May 05 17:04:26 proxmox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20190703/psparse-531)
May 05 17:04:26 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)
May 05 17:04:26 proxmox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190703/psparse-531)
May 05 17:04:26 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)
May 05 17:04:26 proxmox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190703/psparse-531)
May 05 17:04:26 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)
May 05 17:04:26 proxmox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20190703/psparse-531)
May 05 17:04:26 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)
May 05 17:04:26 proxmox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190703/psparse-531)
May 05 17:04:26 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)
May 05 17:04:26 proxmox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190703/psparse-531)
May 05 17:04:26 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)
May 05 17:04:26 proxmox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20190703/psparse-531)
May 05 17:04:26 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)
May 05 17:04:26 proxmox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190703/psparse-531)
May 05 17:04:26 proxmox kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)
May 05 17:04:26 proxmox kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20190703/psparse-531)
May 05 17:04:29 proxmox iscsid[982]: iSCSI daemon with pid=983 started!
May 05 17:04:53 proxmox kernel: kvm [1356]: vcpu1, guest rIP: 0xfffff80045462ff2 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop
May 05 17:04:53 proxmox kernel: kvm [1356]: vcpu1, guest rIP: 0xfffff80045462ff2 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop
May 05 17:04:53 proxmox kernel: kvm [1356]: vcpu1, guest rIP: 0xfffff80045462ff2 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop
May 05 17:04:53 proxmox kernel: kvm [1356]: vcpu1, guest rIP: 0xfffff80045462ff2 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop
May 05 17:04:53 proxmox kernel: kvm [1356]: vcpu1, guest rIP: 0xfffff80045462ff2 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop
May 05 17:04:53 proxmox kernel: kvm [1356]: vcpu1, guest rIP: 0xfffff80045462ff2 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop
May 05 17:04:53 proxmox kernel: kvm [1356]: vcpu1, guest rIP: 0xfffff80045462ff2 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop
May 05 17:04:53 proxmox kernel: kvm [1356]: vcpu1, guest rIP: 0xfffff80045462ff2 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop
May 05 17:04:53 proxmox kernel: kvm [1356]: vcpu1, guest rIP: 0xfffff80045462ff2 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop
May 05 17:04:53 proxmox kernel: kvm [1356]: vcpu1, guest rIP: 0xfffff80045462ff2 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop


Any ideas?
 
please post the vm config, the output of 'lscpi -k' after boot and the iommu groups (ls /sys/kernel/iommu_groups/*/devices/)
 
Code: 
balloon: 2048
bootdisk: sata0
cores: 6
ide2: local:iso/Windows10.iso,media=cdrom
memory: 6144
name: NAS
net0: virtio=56:73:EA:7A:93:90,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
sata0: VM1:vm-100-disk-0,size=32G
sata2: local-lvm:vm-100-disk-0,size=20G
scsi4: /dev/disk/by-id/ata-TOSHIBA_HDWE150_Y64BK51BF57D,size=4883770584K
scsi5: /dev/disk/by-id/ata-TOSHIBA_HDWN160_78P9Y01AFAXG,size=5860522584K
scsi6: /dev/disk/by-id/ata-SAMSUNG_HD153WI_S1UVJ1BZ400308,size=1500297682432
scsihw: virtio-scsi-pci
smbios1: uuid=4738f979-04a5-4685-80e2-904b0de4dd44
sockets: 1
usb0: host=0951:161a,usb3=1
vmgenid: 60026bce-053d-4a1a-9f4f-3e3accc9ebf0

Code: 
balloon: 1024
bootdisk: scsi0
cores: 4
ide2: local:iso/Server2019.iso,media=cdrom
memory: 4095
name: CCTV
net0: virtio=CA:3E:C2:35:DF:C1,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: VM1:vm-101-disk-0,size=45G
scsi2: /dev/disk/by-id/ata-ST1000DL002-9TT153_W1V022GY,size=976762584K
scsi7: /dev/disk/by-id/ata-WDC_WD40PURZ-85TTDY0_WD-WCC7K6TPEASX,size=3907018584K
scsihw: virtio-scsi-pci
smbios1: uuid=5d3069f8-03b3-4d57-81da-51808216263d
sockets: 1
usb0: host=0951:161a,usb3=1
vmgenid: d7a7a134-7d8d-470c-a173-c306a06947aa

Code: 
root@proxmox:~# lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller
        Kernel driver in use: ivb_uncore
        Kernel modules: ie31200_edac
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
        Kernel driver in use: i915
        Kernel modules: i915
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
        Subsystem: Micro-Star International Co., Ltd. [MSI] 7 Series/C210 Series Chipset Family USB xHCI Host Controller
        Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
        Subsystem: Micro-Star International Co., Ltd. [MSI] 7 Series/C216 Chipset Family MEI Controller
        Kernel driver in use: mei_me
        Kernel modules: mei_me
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
        Subsystem: Micro-Star International Co., Ltd. [MSI] 7 Series/C216 Chipset Family USB Enhanced Host Controller
        Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
        Subsystem: Micro-Star International Co., Ltd. [MSI] 7 Series/C216 Chipset Family High Definition Audio Controller
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4)
        Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
        Kernel driver in use: pcieport
00:1c.6 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 7 (rev c4)
        Kernel driver in use: pcieport
00:1c.7 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 (rev c4)
        Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
        Subsystem: Micro-Star International Co., Ltd. [MSI] 7 Series/C216 Chipset Family USB Enhanced Host Controller
        Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation Z77 Express Chipset LPC Controller (rev 04)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Z77 Express Chipset LPC Controller
        Kernel driver in use: lpc_ich
        Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
        Subsystem: Micro-Star International Co., Ltd. [MSI] 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode]
        Kernel driver in use: ahci
        Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
        Subsystem: Micro-Star International Co., Ltd. [MSI] 7 Series/C216 Chipset Family SMBus Controller
        Kernel driver in use: i801_smbus
        Kernel modules: i2c_i801
02:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Killer E220x Gigabit Ethernet Controller
        Kernel driver in use: alx
        Kernel modules: alx
03:00.0 IDE interface: ASMedia Technology Inc. ASM1061 SATA IDE Controller (rev 01)
        Subsystem: Micro-Star International Co., Ltd. [MSI] ASM1061 SATA IDE Controller
        Kernel driver in use: ahci
        Kernel modules: ahci, pata_acpi
04:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire Controller (rev 01)
        Subsystem: Micro-Star International Co., Ltd. [MSI] VT6315 Series Firewire Controller
        Kernel driver in use: firewire_ohci
        Kernel modules: firewire_ohci
root@proxmox:~#



There is nothing in /sys/kernel/iommu_groups/
 
oh so i believe i misunderstood you (i thought you wanted to passthrough a pcie device to a vm)
but maybe the nic names changed when you plugged in the additionale devices

can you post your /etc/network/interfaces and the output of 'ip link' ?
 
I want to passthrough a GPU and another PCIe device.
They are currently not plugged in as I need the server to be on. Less downtime the better xD

Code: 
auto lo
iface lo inet loopback

iface enp2s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.200
        netmask 255.255.255.0
        gateway 192.168.1.1
        bridge_ports enp2s0
        bridge_stp off
        bridge_fd 0
        dns-nameservers 1.1.1.1 8.8.8.8
        ip route add default via 192.168.1.1

iface enp3s0 inet manual

Code: 
root@proxmox:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether d4:3d:7e:b3:3e:9b brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether d4:3d:7e:b3:3e:9b brd ff:ff:ff:ff:ff:ff
4: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr100i0 state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether f2:72:75:cd:52:6f brd ff:ff:ff:ff:ff:ff
5: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether de:db:18:de:22:34 brd ff:ff:ff:ff:ff:ff
6: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 42:22:ed:f4:7d:36 brd ff:ff:ff:ff:ff:ff
7: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP mode DEFAULT group default qlen 1000
    link/ether de:db:18:de:22:34 brd ff:ff:ff:ff:ff:ff
8: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr101i0 state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether ae:58:e8:75:6c:11 brd ff:ff:ff:ff:ff:ff
9: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 12:34:83:b9:ca:7a brd ff:ff:ff:ff:ff:ff
10: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether c2:0e:85:f4:ba:8a brd ff:ff:ff:ff:ff:ff
11: fwln101i0@fwpr101p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP mode DEFAULT group default qlen 1000
    link/ether 12:34:83:b9:ca:7a brd ff:ff:ff:ff:ff:ff
root@proxmox:~#
 
yeah ok what i guess is happening is that when you plug in the other pcie devices, the nic 'enp2s0' renames to something
different and now the network config is wrong

you can only solve this by plugging in the new devices, hop on the console and check with 'ip link' what the current name is and update the interfaces file accordingly
 
Thank you @dcsapak

It changed to enp4s0 so I updated the interfaces config in both places it links to that and it now works.
 
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