Page 1 of 1
Keyboard mapping goes nuts
Posted: 1. Feb 2016, 15:42
by Gil_T
Hi,
I have a Windows 10 host running Linux Ubuntu 14.04 guest with VB 15.0.14
after an hour or so of running, the keyboard mapping goes nuts and i i cant type. the letters keys are the main keys who are infected, numbers and Ctrl/Alt/Shift keys are fine.
A simple shutdown and start does the trick and fixes the problem, but i had to do it 2 in a few hours of use, and it's really annoying.
Can you please check my logs and see what goes wrong?
Gil
Re: Keyboard mapping goes nuts
Posted: 1. Feb 2016, 16:30
by mpack
The main things that jump out at me from this log are :-
- You are allocating 2GB RAM to a VM on a host which has ~2GB available, i.e. you leave none for the host. This is rarely a good idea. I would decrease this to 1GB.
- You only allocate 12MB of graphics RAM (VRAM). If the guest has a GUI then I would allocate 48MB.
- On a host with resources this limited, it might have been better to install a 32bit guest.
- 00:00:13.224406 VMMDev: Guest Additions information report: Version 4.3.34 r104062 '4.3.34_Ubuntu'. You have the Ubuntu fork version of the GAs installed. Not good. This could easily be it, especially since...
- ...00:00:15.360723 VMMDev: Guest Log: 00:00:00.000506 main Executable: /opt/VBoxGuestAdditions-5.0.14/sbin/VBoxService, there's a hint that you also have the official 5.0.14 GAs installed.
Re: Keyboard mapping goes nuts
Posted: 1. Feb 2016, 16:33
by Gil_T
Thanks for the tips!
Can you please tell me how can i remove the old guest addition version? i installed the new one
Edit:
I removed the old guest version, and try to reinstall the new version, but it doesn't seem to help.
I must be missing something but i don't know that it is, can you please look at the new logs.
Re: Keyboard mapping goes nuts
Posted: 1. Feb 2016, 17:34
by mpack
Sorry, but beyond a certain point your questions are more appropriate for an Ubuntu forum, rather than a VirtualBox one. To me it sounds like your keyboard layout (configured in the guest OS) is being interfered with somehow.
p.s. It's not necessary to give us the hardening log unless we ask for it. Your hardening log shows an exit code of 0, indicating that you don't have an issue with hardening.