Keyboard stops working with Windows 7 Pro 64 bit host

[Ntropia]

When pausing and resuming the virtual machine, the keyboard doesn't work anymore (mouse is fine).

HOST
- Debian GNU/Linux 8.3 (jessie)
- kernel SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 GNU/Linux
- VirtualBox 5.0.14-105127~Ubuntu~trusty + Extensions - 5.0.14r105127
- USB keyboard and mouse

GUEST
- Windows 7 Professional 64bit
- Guest Additions 5.0.14

I can reproduce this systematically by doing a fresh reboot, press Host-P twice and freeze the keyboard.
When this happens, the only way to fix it is to reload all kernel modules (rmmod/modprobe vboxpci vboxnetadp vboxnetflt vboxdrv).

This is the output of the dmesg when removing the modules (first line), reloading them and starting the Windows 7 VM:

Code: Select all

[244394.552002] VBoxPciLinuxLinuxUnload           #### MODULES REMOVED HERE
[244403.317015] vboxdrv: Found 8 processor cores          #### MODULES INSERTED HERE
[244403.332556] vboxdrv: TSC mode is Invariant, tentative frequency 3591308426 Hz
[244403.332559] vboxdrv: Successfully loaded version 5.0.14 (interface 0x00240000)
[244403.333052] VBoxPciLinuxInit
[244403.333921] vboxpci: IOMMU not found (not registered)
[244403.335421] VBoxNetAdp: Successfully started.
[244403.336932] VBoxNetFlt: Successfully started.
[244411.056467] SUPR0GipMap: fGetGipCpu=0x3            #### VM STARTED HERE
[244411.528534] usb 4-1.1: reset high-speed USB device number 9 using ehci-pci
[244411.833023] restoring control 00000000-0000-0000-0000-000000000001/2/3
[244412.075413] vboxdrv: ffffffffa1150020 VMMR0.r0
[244412.167532] vboxdrv: ffffffffa0f16020 VBoxDDR0.r0
[244412.168600] vboxdrv: ffffffffa00e0020 VBoxDD2R0.r0
[244412.217840] vboxdrv: ffffffffa00f0020 VBoxEhciR0.r0

I'm writing here to make sure there isn't something obvious that I'm missing before reporting what looks like a bug.
I'll be happy to provide further details if required.

Thanks!

[mpack]

USB keyboard?

If you have one, then remove the blank USB filter from your VM settings - or any other filter which could potentially match your keyboard.

[Ntropia]

I initially thought so myself, and I checked but I have no filters active (see attached).

Everything works fine when I first boot the VM. The problem shows up only after resuming the VM from a pause:

Code: Select all

VBoxManage controlvm $VM pause

Since it never happened until I've updated from 5.0.12 to 5.0.14, I suspect there's something wrong going on.

[mpack]

Well, I have no experience with Linux hosts myself, so hopefully someone will come along who does.

In the meantime it would be useful to have a VM log file (any affected VM will do): with the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[michaln]

What does "keyboard stops working" mean exactly? No keyboard input on the host? No input in the VM?

Any idea what 'usb 4-1.1' in the dmesg excerpt refers to?

[robertwork]

I have the same problem with 5.1.10. Requires a shutdown to fix it (reboot/restart will not cut it).

[socratis]

Same problem (?), same troubleshooting methods. Read the thread from the beginning and answer the questions that have been asked so far. Do not be afraid to go into details. And when you do provide details, please be accurate. For example, you mentioned a "shutdown to fix it". Who's shutdown? Guest? Host? Both? You see what I mean, right?

[robertwork]

Same problem (?), same troubleshooting methods. Read the thread from the beginning and answer the questions that have been asked so far. Do not be afraid to go into details. And when you do provide details, please be accurate. For example, you mentioned a "shutdown to fix it". Who's shutdown? Guest?

Yes

Host? Both? You see what I mean, right?

It seems to be random, AFAICT. Sometimes when a machine is paused via the command line, it will stop accepting keystrokes. Most of the time, it works.

My host is a Debian laptop. Guest is Win10. My other guest, another Debian machine, does not seem to suffer from this problem, for some reason.

I should also mention that the scripts to pause the machines were written due to a problem with VirtualBox due to docking and undocking the host laptop. I pause the VM prior to undocking, and resume after undocking. This is a workaround to a problem where the guests will crash (both Win10 and Debian crash equally) if the laptop is undocked without pausing. The same goes for the docking sequence: pause, dock, and then resume.