Opened 11 years ago
Closed 8 years ago
#11999 closed defect (obsolete)
Linux guest: Keyboad stops working due to "atkbd serio0: Spurious NAK on isa0060/serio0. Some program might be trying to access hardware directly."
| Reported by: | nothx | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.2.16 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
I am aware of #7462 and #407 but they don't seem to cover the issue I am encoutering. It hit me for the third time now. At some stage the keyboard just stops working in the Linux 3.8.0 guest. When remotely connecting, dmesg spits
atkbd serio0: Spurious NAK on isa0060/serio0. Some program might be trying to access hardware directly.
I don't know yet how to reproduce this bug and there is a chance that this is not a VirtualBox but a Linux problem. However, I'd be very surprised if it was Linux' only fault.
In any case, it is very annoying as only the mouse remains in a working state and to bring the keyboard back, one needs to reboot the guest. Not very cool.
The VBox.log doesn't seem to contain anything interesting as the messages only deal with networking stuff, i.e. DHCP leases.
Note:
See TracTickets
for help on using tickets.
Please reopen if still relevant with a recent VirtualBox release.