usb3 pcie passthrough

S

shaling01846

New Member
Jul 29, 2017
6
0
1
42
Hi,
I've been using proxmox for several years now for a home setup. Ever since version 4, I can no longer pass through my intel ivy bridge usb3 controller (asmedia). The error i get is "cannot reset device". Tried stubing etc. The driver is correctly asigned to vfio with stock install anyway. So i gave up thinking this would be impossible with this hardware setup.

But, having just tried kvm on centos 7, all works perfectly. Even usb3 uas without controller resetting and going back to host (this is what happens in proxmox with passing usb device throught rather than whole controller). When guest is switched off, usb3 devices are again available to host os.

My question is why then does it not work on proxmox? I would like to keep running proxmox but need this to work.

Thanks.
 
can you post the output of
Code: 
lspci -k
find /sys/kernel/iommu_groups/ -type l | sort -n -t "/" -k 5
pveversion -v
qm config <VMID>

does anything on the host use this usb controller already before starting the vm ?
does the syslog say anything?
 
Hi,
The host has assigned the xhci_hcd driver to the device. Blacklisting it doesn't work. When I stubbed the device, I still couldn't get it to work, so reverted back to a stock setup as below. I am using a jetway mobile cpu itx motherboard, NF9G-QM77. CentOS doesn't require any mods to make the USB3 controller passthrough to a vm.

Thanks for looking into this.

lspci -k

00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
Subsystem: Intel Corporation 3rd Gen Core processor DRAM Controller
Kernel driver in use: ivb_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
Subsystem: Intel Corporation 3rd Gen Core processor Graphics Controller
Kernel modules: i915
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
Subsystem: Intel Corporation 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: Intel Corporation 7 Series/C216 Chipset Family MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller (rev 04)
Subsystem: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller
Kernel driver in use: serial
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
Subsystem: Intel Corporation 82579LM Gigabit Network Connection
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
Subsystem: Intel Corporation 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: Jetway Information Co., Ltd. 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
Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 (rev c4)
Kernel driver in use: pcieport
Kernel modules: shpchp
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
Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
Subsystem: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller
Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller (rev 04)
Subsystem: Intel Corporation QM77 Express Chipset LPC Controller
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
Subsystem: Intel Corporation 7 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: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
03:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
Kernel driver in use: igb
Kernel modules: igb
03:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
Kernel driver in use: igb
Kernel modules: igb
04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
Subsystem: Intel Corporation 82574L Gigabit Network Connection
Kernel driver in use: e1000e
Kernel modules: e1000e

###################################

find /sys/kernel/iommu_groups/ -type l | sort -n -t "/" -k 5

/sys/kernel/iommu_groups/0/devices/0000:00:00.0
/sys/kernel/iommu_groups/1/devices/0000:00:01.0
/sys/kernel/iommu_groups/2/devices/0000:00:02.0
/sys/kernel/iommu_groups/3/devices/0000:00:14.0
/sys/kernel/iommu_groups/4/devices/0000:00:16.0
/sys/kernel/iommu_groups/4/devices/0000:00:16.3
/sys/kernel/iommu_groups/5/devices/0000:00:19.0
/sys/kernel/iommu_groups/6/devices/0000:00:1a.0
/sys/kernel/iommu_groups/7/devices/0000:00:1b.0
/sys/kernel/iommu_groups/8/devices/0000:00:1c.0
/sys/kernel/iommu_groups/9/devices/0000:00:1c.4
/sys/kernel/iommu_groups/10/devices/0000:00:1c.6
/sys/kernel/iommu_groups/11/devices/0000:00:1d.0
/sys/kernel/iommu_groups/12/devices/0000:00:1f.0
/sys/kernel/iommu_groups/12/devices/0000:00:1f.2
/sys/kernel/iommu_groups/12/devices/0000:00:1f.3
/sys/kernel/iommu_groups/13/devices/0000:03:00.0
/sys/kernel/iommu_groups/14/devices/0000:03:00.1
/sys/kernel/iommu_groups/15/devices/0000:04:00.0


############################
pveversion -v

proxmox-ve: 5.0-16 (running kernel: 4.10.17-1-pve)
pve-manager: 5.0-23 (running version: 5.0-23/af4267bf)
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.4.19-1-pve: 4.4.19-66
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.10.17-1-pve: 4.10.17-16
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-14
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-5
libpve-storage-perl: 5.0-12
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-2
pve-container: 2.0-14
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve2
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

################################

qm config 99999

boot: d
cores: 2
cpu: kvm64
hostpci0: 00:14.0,pcie=1
ide0: local:iso/debian-live-9.0.1-amd64-xfce.iso,media=cdrom,size=1897152K
machine: q35
memory: 2480
name: liveusb3
net0: virtio=CE:5F:45:76:75:61,bridge=vmbr0
numa: 0
ostype: l26
smbios1: uuid=626926c1-2a04-4e4b-8b32-5075b8bad716
sockets: 1

########################################
qm start 99999

kvm: vfio: Cannot reset device 0000:00:14.0, no available reset mechanism.
kvm: vfio: Cannot reset device 0000:00:14.0, no available reset mechanism.
 
can you try to add a file /etc/modprobe.d/vfio.conf
with the content:
Code: 
options vfio-pci ids=xxxx:yyyy

where xxxx:yyyy is the vendor/pci id you get from the usb device
when executing 'lspci -nn'
(on my host it would be 8086:a12f)

and then restart the host and try again
if you get an error please post the message here
 
Added "options vfio-pci ids=8086:1e31" to "/etc/modprobe.d/vfio.conf"

After reboot, no change here

00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
Subsystem: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller
Kernel driver in use: xhci_hcd

After I start the vm, just as before, vfio-pci driver gets assigned to the device upon startup.

00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
Subsystem: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller
Kernel driver in use: vfio-pci

And still gives the same error,

kvm: vfio: Cannot reset device 0000:00:14.0, no available reset mechanism.
kvm: vfio: Cannot reset device 0000:00:14.0, no available reset mechanism.
 
also what i forgot to mention is that if you modify the /etc/modules files or /etc/modprobe.d/vfio.conf you have to do an initramfs update
Code: 
update-initramfs -u
before rebooting
 
  • Like
Reactions: kwinz
you can also try to add
Code: 
vfio-pci.ids=8086:1e31

to /etc/default/grub
in the line with GRUB_CMDLINE_LINUX_DEFAULT

then do a
Code: 
update-grub

and reboot your host
 
Hi,
Still the kernel xhci_driver claims pci device 00:14.0.

Also tried adding the following to /etc/modprobe.d/xhci_hcd.conf

softdep xhci_hcd pre: vfio_pci

followed by

update-initramfs -u

No change.
 
shaling01846 said:
Hi,
Still the kernel xhci_driver claims pci device 00:14.0.

Also tried adding the following to /etc/modprobe.d/xhci_hcd.conf

softdep xhci_hcd pre: vfio_pci

followed by

update-initramfs -u

No change.
Click to expand...

hmmm no clue as to why it does not work.
does the syslog/journal has any more information?

did you really reboot the host (not the guest) between the steps?
does the guest start despite the error messages?
 
Hi,
The guest does start up despite the message. And after your question, I realised that I hadn't checked if the device appeared in the VM. Well it does and everything plugged into. So it works despite the message. I completely over looked the obvious.

Thanks for you help.
 
shaling01846 said:
Hi,
The guest does start up despite the message. And after your question, I realised that I hadn't checked if the device appeared in the VM. Well it does and everything plugged into. So it works despite the message. I completely over looked the obvious.

Thanks for you help.
Click to expand...
ok, glad that it works :)
 
Hello, I know this thread is more than 2 years old. But I am struggling with the same issue.

Here is what is working on my setup so far:
GPU passthrough using and AMD processor and AMD graphics card.

What I am trying to achieve now:
PCIe passthrough a USB controller on the same VM
link to the product

What I have tried so far:
  • Edit my /etc/modprobe.d/vfio.conf file:
Code: 
options vfio-pci ids=1002:6939,1002:aad8 disable_vga=1
options vfio-pci ids=1b73:1100
First line is for my GPU,
Second line is for the USB controller
  • Edit my /etc/modprobe.d/xhci_hcd.conf file:
Code: 
softdep xhci_hcd pre: vfio_pci

  • Edit my /etc/defaults/grub file:
Code: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet iommu=pt amd_iommu=on video=efifb:off vfio_iommu_type1.allow_unsafe_interrupts=1"
For this one I also tried it changing the /etc/modprobe.d/vfio.conf file adding the following line
Code: 
options vfio_iommu_type1 allow_unsafe_interrupts=1

OF COURSE every time I made a modification in the grub file I executed the command updage-grub and every time I made a modification is a /etc/modprobe.d/*.conf file I executed the command update-initramfs -u -k all

What I haven't tried:

I haven't tried blacklisting the xhci_hcd driver as I might need it later on the host.

Strange behaviour:

Most of the time when I start the VM, everything crashes, the host is unaccessible and the VM as well.
But one or two times, the host was not accessible anymore, but the VM was working. I cannot say at which step though and cannot confirm the USB controller was available for the VM.
 
i would be helpful if you would also post the info i requested above (ioummu groups, lspci, etc.)
 
lspci -k
Code: 
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex
        Subsystem: ASUSTeK Computer Inc. Family 17h (Models 00h-0fh) Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit
        Subsystem: ASUSTeK Computer Inc. Family 17h (Models 00h-0fh) I/O Memory Management Unit
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
        Kernel driver in use: pcieport
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
        Kernel driver in use: pcieport
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
        Kernel driver in use: pcieport
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
        Kernel driver in use: pcieport
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
        Subsystem: ASUSTeK Computer Inc. FCH SMBus Controller
        Kernel driver in use: piix4_smbus
        Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
        Subsystem: ASUSTeK Computer Inc. FCH LPC Bridge
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
        Kernel driver in use: k10temp
        Kernel modules: k10temp
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller (rev 01)
        Subsystem: ASMedia Technology Inc. 400 Series Chipset USB 3.1 XHCI Controller
        Kernel driver in use: xhci_hcd
01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller (rev 01)
        Subsystem: ASMedia Technology Inc. 400 Series Chipset SATA Controller
        Kernel driver in use: ahci
        Kernel modules: ahci
01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge (rev 01)
        Kernel driver in use: pcieport
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
        Kernel driver in use: pcieport
02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
        Kernel driver in use: pcieport
02:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
        Kernel driver in use: pcieport
02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
        Kernel driver in use: pcieport
02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
        Kernel driver in use: pcieport
06:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10)
        Subsystem: Fresco Logic FL1100 USB 3.0 Host Controller
        Kernel driver in use: xhci_hcd
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
        Kernel driver in use: r8169
        Kernel modules: r8169
08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] (rev f1)
        Subsystem: PC Partner Limited / Sapphire Technology Radeon R9 380 Nitro 4G D5
        Kernel driver in use: vfio-pci
        Kernel modules: amdgpu
08:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Tonga HDMI Audio [Radeon R9 285/380]
        Subsystem: PC Partner Limited / Sapphire Technology Radeon R9 285/380 HDMI Audio
        Kernel driver in use: vfio-pci
        Kernel modules: snd_hda_intel
09:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function
        Subsystem: ASUSTeK Computer Inc. Zeppelin/Raven/Raven2 PCIe Dummy Function
09:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor
        Subsystem: ASUSTeK Computer Inc. Family 17h (Models 00h-0fh) Platform Security Processor
        Kernel driver in use: ccp
        Kernel modules: ccp
09:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] USB 3.0 Host controller
        Subsystem: ASUSTeK Computer Inc. USB 3.0 Host controller
        Kernel driver in use: xhci_hcd
0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function
        Subsystem: ASUSTeK Computer Inc. Zeppelin/Renoir PCIe Dummy Function
0a:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
        Subsystem: ASUSTeK Computer Inc. FCH SATA Controller [AHCI mode]
        Kernel driver in use: ahci
        Kernel modules: ahci
0a:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller
        Subsystem: ASUSTeK Computer Inc. Family 17h (Models 00h-0fh) HD Audio Controller
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel

root@pitland:~# find /sys/kernel/iommu_groups/ -type l | sort -n -t "/" -k 5
Code: 
/sys/kernel/iommu_groups/0/devices/0000:00:01.0
/sys/kernel/iommu_groups/1/devices/0000:00:01.3
/sys/kernel/iommu_groups/2/devices/0000:00:02.0
/sys/kernel/iommu_groups/3/devices/0000:00:03.0
/sys/kernel/iommu_groups/4/devices/0000:00:03.1
/sys/kernel/iommu_groups/5/devices/0000:00:04.0
/sys/kernel/iommu_groups/6/devices/0000:00:07.0
/sys/kernel/iommu_groups/7/devices/0000:00:07.1
/sys/kernel/iommu_groups/8/devices/0000:00:08.0
/sys/kernel/iommu_groups/9/devices/0000:00:08.1
/sys/kernel/iommu_groups/10/devices/0000:00:14.0
/sys/kernel/iommu_groups/10/devices/0000:00:14.3
/sys/kernel/iommu_groups/11/devices/0000:00:18.0
/sys/kernel/iommu_groups/11/devices/0000:00:18.1
/sys/kernel/iommu_groups/11/devices/0000:00:18.2
/sys/kernel/iommu_groups/11/devices/0000:00:18.3
/sys/kernel/iommu_groups/11/devices/0000:00:18.4
/sys/kernel/iommu_groups/11/devices/0000:00:18.5
/sys/kernel/iommu_groups/11/devices/0000:00:18.6
/sys/kernel/iommu_groups/11/devices/0000:00:18.7
/sys/kernel/iommu_groups/12/devices/0000:01:00.0
/sys/kernel/iommu_groups/12/devices/0000:01:00.1
/sys/kernel/iommu_groups/12/devices/0000:01:00.2
/sys/kernel/iommu_groups/12/devices/0000:02:00.0
/sys/kernel/iommu_groups/12/devices/0000:02:04.0
/sys/kernel/iommu_groups/12/devices/0000:02:05.0
/sys/kernel/iommu_groups/12/devices/0000:02:06.0
/sys/kernel/iommu_groups/12/devices/0000:02:07.0
/sys/kernel/iommu_groups/12/devices/0000:06:00.0
/sys/kernel/iommu_groups/12/devices/0000:07:00.0
/sys/kernel/iommu_groups/13/devices/0000:08:00.0
/sys/kernel/iommu_groups/13/devices/0000:08:00.1
/sys/kernel/iommu_groups/14/devices/0000:09:00.0
/sys/kernel/iommu_groups/15/devices/0000:09:00.2
/sys/kernel/iommu_groups/16/devices/0000:09:00.3
/sys/kernel/iommu_groups/17/devices/0000:0a:00.0
/sys/kernel/iommu_groups/18/devices/0000:0a:00.2
/sys/kernel/iommu_groups/19/devices/0000:0a:00.3
 
pveversion -v
Code: 
proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve)
pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e)
pve-kernel-helper: 6.1-6
pve-kernel-5.3: 6.1-5
pve-kernel-5.3.18-2-pve: 5.3.18-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-13
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-4
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-21
pve-docs: 6.1-6
pve-edk2-firmware: 2.20191127-1
pve-firewall: 4.0-10
pve-firmware: 3.0-6
pve-ha-manager: 3.0-8
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-3
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-6
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

qm config 201
Code: 
bios: ovmf
bootdisk: scsi0
cores: 6
cpu: host
efidisk0: local-lvm:vm-201-disk-1,size=4M
hostpci0: 08:00,pcie=1,x-vga=1
hostpci1: 06:00,pcie=1
machine: q35
memory: 8192
name: windows
net0: virtio=02:96:f5:d6:8a:d7,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
sata0: local:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K
scsi0: local-lvm:vm-201-disk-0,size=64G
scsihw: virtio-scsi-pci
smbios1: uuid=693e7d04-595c-4a10-9676-8a92b6ee89e5
sockets: 1
virtio0: proxmox-lvm:201/vm-201-disk-0.raw,cache=writeback,size=200G
vmgenid: 107b7b1a-7769-402c-a4ef-9a3978068447
 
simonpit said:
hostpci1: 06:00,pcie=1
Click to expand...
no wonder your machine crashes, it is together with many other devices in an iommu group
(e.g. your sata controller, pcie root ports, network, etc)

simonpit said:
/sys/kernel/iommu_groups/12/devices/0000:01:00.0
/sys/kernel/iommu_groups/12/devices/0000:01:00.1
/sys/kernel/iommu_groups/12/devices/0000:01:00.2
/sys/kernel/iommu_groups/12/devices/0000:02:00.0
/sys/kernel/iommu_groups/12/devices/0000:02:04.0
/sys/kernel/iommu_groups/12/devices/0000:02:05.0
/sys/kernel/iommu_groups/12/devices/0000:02:06.0
/sys/kernel/iommu_groups/12/devices/0000:02:07.0
/sys/kernel/iommu_groups/12/devices/0000:06:00.0
/sys/kernel/iommu_groups/12/devices/0000:07:00.0
Click to expand...

you could try to passthrough a different usb controller (this seems to be in its own group)
/sys/kernel/iommu_groups/16/devices/0000:09:00.3

just note that it uses different usb ports then (maybe also only a header on the mainboard)
 
Ok, I understand the problem,
is it possible to change the group of the 06:00 device so that is will be alone ?
 
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