Ubuntu
libvirt package

speed mismatch trying to attach xbox sensor to windows 10 guest vm

Bug #1890062 reported by Marietto
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Distro: Ubuntu 20.04

MachineType: I9 9900k + 32 gb + geforce 2080ti

I tried to pass through two xbox sensors to a windows 10 guest os with virt-manager and I got this error message :

Error trying to start domain : internal error : qemu unexpectedly closed the monitor :

warning : host does not support requested feature. MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 12]

qemu unexpectedly closed the monitor :
warning : host does not support requested feature. MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 13]

qemu unexpectedly closed the monitor :
warning : host does not support requested feature. MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 12]

qemu unexpectedly closed the monitor :
warning : host does not support requested feature. MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 132]

qemu-system-x86_64: -device usb-host,hostbus=2,hostaddr=3,id=hostdev4,bus=usb.0,port=4 : warning : speed mismatch trying to attach usb device "Xbox NUI Sensor" (super speed) to bus "usb.0",port "4" (full high speed)

qemu-system-x86_64: -device usb-host,hostbus=2,hostaddr=3,id=hostdev4,bus=usb.0,port=4 : failed to open host usb device 2:3

Revision history for this message
Marietto (marietto2008) wrote :

update : I forgot to change the USB 2 with 3. Now the error is gone,but the kinect sensor is not detected by Windows 10. Attached images...

Revision history for this message
Marietto (marietto2008) wrote :

as u can see the kinects sensor are recognized correctly.

Revision history for this message
Marietto (marietto2008) wrote :

but windows 10 does not see them.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi,
FYI the VMX warnings are correct and not related.
I wanted to say that you need the right USB-Host but your found that yourself in comment #1.

When the devices are really passed through then it is up to the guest to handle them.
Once thing I could recommend - since USB can hot-plug - is attach/detach them from the guest.
And while (after & before) doing so run something like devcon or usbview.

See
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/usbview
https://docs.microsoft.com/en-us/windows/win32/api/setupapi/nf-setupapi-setupdigetclassdevsw?redirectedfrom=MSDN
https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/devcon

e.g. "devcon hwids =usb"

Is the USB3 controller showing up correctly at all (down at the bottom of your device manager)?
If not the devices attached to it would be missing as well.

Changed in libvirt (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.]

Changed in libvirt (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.