Mouse/Keyboard/Touchpad is NOT working to access the Guest VM when USB Controller changed 3.1 to 2.0
Article ID: 315600
Updated On:
Products
VMware Desktop Hypervisor
Issue/Introduction
Symptoms:
Unable to interreact to Guest OS through Keyboard/Mouse/Touchpad
Unable to interreact to Guest OS through Keyboard/Mouse/Touchpad
Cause
Windows Maintained guidelines for USB from Windows 8.1 not to support UHCI and has stopped further development/shipping of UHCI drivers on newer development(ARM-based windows). Since the virtual keyboard/mouse/touchpad is connected with UHCI in absence of xHCI all devices connected with UHCI may not work
UHCI is a legacy device and requires IO space for the device to work correctly on Linux we might provide IO support and all Linux-based system which ships UHCI driver may work. On top of that ARM system ready is throwing errors because of exposer of UHCI controller so we might drop USB 2.0 on an ARM-based platform(discussion is in progress)
UHCI is a legacy device and requires IO space for the device to work correctly on Linux we might provide IO support and all Linux-based system which ships UHCI driver may work. On top of that ARM system ready is throwing errors because of exposer of UHCI controller so we might drop USB 2.0 on an ARM-based platform(discussion is in progress)
Resolution
Use USB Compatibility > 3.0
Workaround:
Disable uhci by providing “usb.uhci.present = 0” in the configuration file if user want to use USB 2.0 as USB compatibility
Workaround:
Disable uhci by providing “usb.uhci.present = 0” in the configuration file if user want to use USB 2.0 as USB compatibility
Additional Information
Impact/Risks:
This issue will have an impact on the Virtual Machine Guest OS or VMs itself.
This issue will have an impact on the Virtual Machine Guest OS or VMs itself.
Feedback
Yes
No
Powered by
