Opened 14 years ago
Closed 9 years ago
#5947 closed defect (obsolete)
Extensive use of os/2 guest damages linux host
| Reported by: | James Moe | Owned by: | |
|---|---|---|---|
| Component: | guest additions | Version: | VirtualBox 3.1.2 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Linux |
Description (last modified by )
opensuse v11.1
host linux 2.6.27.39-0.2-default x86_64
guest os/2 v4.52
guest winXP sp3
After protracted use of the os/2 guest, winxp guest, and linux host, strange things start to happen for one user. Mainly the keyboard response in the os/2 guest becomes erratic, particularly the numeric keypad stops working; the NumLock is ignored; os/2 must be powered off to restore keyboard function, not just restarted.
In other cases the keyboard acts erratically for guests and hosts alike. Other times the mouse actions are scrambled. And sometimes both the mouse and keyboard become unresponsive requiring a system restart.
Unfortunately the person who uses the host/guests is reluctant about notifying me about these problems so I do not have much detail.
I am presuming it is the os/2 guest that is causing the problems. Another host uses the winXP guest quite extensively without any of these types of issues. The os/2 user copies and pastes data a lot from the guest to the winxp guest (not directly since that does not work).
I note that no updates have been made to the os/2 guest additions since at least v3.0.2.
See also issue #5552.
Attachments (3)
Change History (8)
by , 14 years ago
| Attachment: | VBox.log-os2 added |
|---|
comment:1 by , 14 years ago
comment:3 by , 14 years ago
It just keeps getting better...
Now, instead of partial or erratic keyboard function, VirtualBox completely takes down linux: a complete system freeze. Only a hard reset is possible. No keyboard. No mouse. No activity whatsoever.
comment:5 by , 9 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → obsolete |
| Status: | new → closed |
I was incorrect regarding the windows-only user. There are keyboard problems there as well. Notably the initial sign of degradation is that the caps lock becomes inverted, i.e., the caps lock must be ON to get lower case letters. Continued use will degrade the keyboard to non-functionality. The degradation affects linux use as well.
The workaround is to shut down windows VM, and log off the linux user. After logging on, the keyboard is restored to normal function.
Further on the os/2 front: The num lock for the keypad becomes inverted. It must be OFF to get numbers from the keypad. Powering down the os/2 VM resolves the problem.