Opened 4 years ago
Last modified 3 years ago
#20499 new defect
mouse and keyboard stop working after a few seconds
Reported by: | madires | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 6.1.24 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description ¶
Host: Debian 10, 64 bit, custom 5.10.x kernel Guests: Win 7 Pro 32 bit, Win 10 Pro 64 bit, possibly other versions too Affected VirtualBox versions: 6.1.24 and 6.1.26
After powering on a windows VM the VM stops reacting to mouse clicks or keyboard input. With Guest Additions installed the mouse pointer still moves. The VirtualBox app window won't refresh. I have to destroy the VM window to resume normal operation. When I start the Windows VM in safe mode mouse and keyboard work fine. Another observation is that the Remote Display is affected too (RDP client connects, changes size to VM's resolution, but black window) and works only when VM is started in safe mode. A downgrade of VirtualBox 6.1.22 resolves all issues.
Change History (7)
by , 4 years ago
comment:1 by , 4 years ago
Hi madires,
Does the issue specific only to Windows guest? Have you tried with another guest types? When you do VirtualBox downgrade (when things are back to normal), do you also downgrade the additions?
comment:2 by , 4 years ago
Yes, as far as I was able to check. I've tested also Linux guests (console only, no X11) and keyboard input worked fine with VirtualBox 6.1.24 and 6.1.26. The version of the guest additions doesn't seem to have any impact. For example, a Windows 7 Pro guest runs without any problems with guest additions 6.1.26 and VirtualBox 6.1.22.
comment:3 by , 4 years ago
Same problems also with 6.1.28. :( BTW, menu item "ACPI Shutdown" doesn't work either.
comment:5 by , 3 years ago
Did you try the same VM with audio disabled? From the log you have a very unusual VM config, namely using ALSA. Most people use PulseAudio.
comment:6 by , 3 years ago
Bingo! After changing the host audio driver to "Null Audio Driver" the keyboard/mouse input issues are gone. Thanks for the hint! I prefer using plain ALSA since I don't like PulseAudio. The "OSS Audio Driver" works also (I think I'll use this one as temporary work-around). Apparently the issues are caused by the interworking with the ALSA driver.
VBox.log file