Opened 9 years ago
Last modified 8 years ago
#14113 new defect
Ubuntu guest loses keyboard sporadically
Reported by: | DO | Owned by: | |
---|---|---|---|
Component: | RDP | Version: | VirtualBox 4.3.28 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Linux |
Description
Host: ubuntu 14.04 Guest: ubuntu 12.04
Sporadically guest loses keyboard, xev doesn't show keyboard events, etc. The only way to fix this issue is to restart guest. Save/reload doesn't help.
I'm using the Microsoft Remote Desktop (Win7) as client. If I close it and reconnect to the guest the keyboard still doesn't work.
Attachments (2)
Change History (10)
by , 9 years ago
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Terribly sorry, it seems that the logging was removed from the keyboard code in the 4.3 series. I have added it back in: you can get the updated builds of VirtualBox from the Testbuilds page.
comment:3 by , 9 years ago
"The requested URL /download/testcase/VirtualBox-4.3.27-100331-Linux_amd64.run was not found"
comment:4 by , 9 years ago
I've installed 4.3.x revision 100516, but there is no keyboard related information in the logs.
comment:5 by , 9 years ago
Proper log group is not dev_kbd
but gui
, it seems.
You can also tweak this for a running VM with
VBoxManage debugvm "VM Name" log --release "+gui.l3"
and turn off again with -gui.l3
comment:6 by , 9 years ago
Actually it is dev_kbd.e.f
, not dev_kbd.e.l3
as I initially wrote. Sorry.
comment:7 by , 8 years ago
I am having this same issue with a CentOS 7.1 host and Linux Mint 17.2 guest while accessing the guest over RDP. The only solution is to restart the guest. I followed the instructions above for extra debug information and the keypresses are showing in the log despite not showing up on the guest.
My version is: 5.0.10 r104061
$ tail vbox/bluebox/Logs/VBox.log 00:20:51.396508 ps2kPutEventWrapper: key code 00000004 00:20:51.396561 ps2kInsertQueue: inserted 0x1C into queue 00007f99da093b24 00:20:51.525573 ps2kPutEventWrapper: key code 80000004 00:20:51.525622 ps2kInsertQueue: inserted 0xF0 into queue 00007f99da093b24 00:20:51.525630 ps2kInsertQueue: inserted 0x1C into queue 00007f99da093b24 00:20:53.804854 ps2kPutEventWrapper: key code 00000004 00:20:53.804895 ps2kInsertQueue: inserted 0x1C into queue 00007f99da093b24 00:20:53.924568 ps2kPutEventWrapper: key code 80000004 00:20:53.924610 ps2kInsertQueue: inserted 0xF0 into queue 00007f99da093b24 00:20:53.924617 ps2kInsertQueue: inserted 0x1C into queue 00007f99da093b24
by , 8 years ago
comment:8 by , 8 years ago
I've attached the full log file in case that is helpful and can do further investigation if needed.
Would you be able to do a bit of further investigation? If you run the following command line commands:
and then start your virtual machine with this environment variable set:
then you should get information about all key presses sent by the emulated PS/2 keyboard to the virtual machine added to the log file. This should tell you whether the problem is in the guest system or on the host side.