I tried to passthrough the Windows MR (Samsung Oddessy Plus) to my Windows guest machine
Long story short, passing through the entire pci is NOT an option in my case.
The windows machine with GPU (nVidia) pass through and 2 USB 2.0 devices set in conf. Which is the mouse and keyboard.
When the guest started, I tried the following command to pass through the MR device.
qm monitor 100
device_add nec-usb-xhci,id=xhci,addr=0x1B,bus=pci.1
device_add usb-host,bus=xhci.0,vendorid=0x045e,productid=0x0659,id=HoloLens
device_add usb-host,bus=xhci.0,vendorid=0x2109,productid=0x0210,id=VIA1
device_add usb-host,bus=xhci.0,vendorid=0x04e8,productid=0x7312,id=Audio
device_add usb-host,bus=xhci.0,vendorid=0x04e8,productid=0x7084,id=STM
device_add usb-host,bus=xhci.0,vendorid=0x2109,productid=0x2210,id=VIA2
The windows picked up the devices and tried to start the MR client but failed with Error code 7-12 (connected to an incompatible USB controller)
As you see the device added is very complicated, a single usb connector has 5 different devices including 2 VIA hubs.
In the host, when I unplug the MR and I got the following dmesg
[ 8308.472031] usb 3-3: USB disconnect, device number 15
[ 8308.472033] usb 3-3.2: USB disconnect, device number 16
[ 8308.474487] usb 3-3.3: USB disconnect, device number 17
[ 8308.487125] usb 4-3: USB disconnect, device number 6
[ 8308.487126] usb 4-3.1: USB disconnect, device number 7
Which I guess the 3-3 is one of the VIA hub, and 4-3 is the other
Under the lsusb at host, the related items are listed below:
Bus 004 Device 009: ID 045e:0659 Microsoft Corp. (= HoloLens)
Bus 004 Device 008: ID 2109:0210 VIA Labs, Inc. (=VIA1)
Bus 003 Device 020: ID 04e8:7312 Samsung Electronics Co., Ltd (=Audio)
Bus 003 Device 019: ID 04e8:7084 Samsung Electronics Co., Ltd (=STM)
Bus 003 Device 018: ID 2109:2210 VIA Labs, Inc. (=VIA2)
Long story short, passing through the entire pci is NOT an option in my case.
The windows machine with GPU (nVidia) pass through and 2 USB 2.0 devices set in conf. Which is the mouse and keyboard.
When the guest started, I tried the following command to pass through the MR device.
qm monitor 100
device_add nec-usb-xhci,id=xhci,addr=0x1B,bus=pci.1
device_add usb-host,bus=xhci.0,vendorid=0x045e,productid=0x0659,id=HoloLens
device_add usb-host,bus=xhci.0,vendorid=0x2109,productid=0x0210,id=VIA1
device_add usb-host,bus=xhci.0,vendorid=0x04e8,productid=0x7312,id=Audio
device_add usb-host,bus=xhci.0,vendorid=0x04e8,productid=0x7084,id=STM
device_add usb-host,bus=xhci.0,vendorid=0x2109,productid=0x2210,id=VIA2
The windows picked up the devices and tried to start the MR client but failed with Error code 7-12 (connected to an incompatible USB controller)
As you see the device added is very complicated, a single usb connector has 5 different devices including 2 VIA hubs.
In the host, when I unplug the MR and I got the following dmesg
[ 8308.472031] usb 3-3: USB disconnect, device number 15
[ 8308.472033] usb 3-3.2: USB disconnect, device number 16
[ 8308.474487] usb 3-3.3: USB disconnect, device number 17
[ 8308.487125] usb 4-3: USB disconnect, device number 6
[ 8308.487126] usb 4-3.1: USB disconnect, device number 7
Which I guess the 3-3 is one of the VIA hub, and 4-3 is the other
Under the lsusb at host, the related items are listed below:
Bus 004 Device 009: ID 045e:0659 Microsoft Corp. (= HoloLens)
Bus 004 Device 008: ID 2109:0210 VIA Labs, Inc. (=VIA1)
Bus 003 Device 020: ID 04e8:7312 Samsung Electronics Co., Ltd (=Audio)
Bus 003 Device 019: ID 04e8:7084 Samsung Electronics Co., Ltd (=STM)
Bus 003 Device 018: ID 2109:2210 VIA Labs, Inc. (=VIA2)