mouse disappears on Linux VM under 3.0.x

[graysky]

I'm running an Arch Linux VM running on VB version 3.0.4 running under an Arch Linux host. The VM boots up just fine and is fully functional, except that the mouse in the VM simply stops working after a while. It seems to be stuck and invisible trapped in the lower right of the screen. If I click w/ the left button nothing seems to happen; if I click w/ the right button, the right-click submenu pops up and all I can do it select one of the options from it (new file, new folder, etc.) The only way I can get the mouse back is to restart the VM. Sending a ctrl+alt+backspace locks up the VM. I have a USB mouse if that matters.

[graysky]

I forgot to add that I haven't experienced this issue under 2.2.4 of VB at all. It began happening w/ the 3.0.x series of VB.

[Michael Thayer]

Could you try out the effect of the following? Switching to a VT using Host + Fx and restarting the X server; and resetting the guest using Host + R? Thanks.

[graysky]

@Michael - I've tried this before... I can HOSTKEY+F1 for example and then issue a gdm restart as root but it ends up in a black screen wo/ a cursor or anything. The VM is then unresponsive to further HOSTKEY+Fx attempts and I can do is force a reboot on the guest.

[Michael Thayer]

What about rebooting with Host + R? By the way, you said that this first started with the 3.0.x series - did you see this issue with earlier 3.0.x releases? Can you see if there is anything special that you do to trigger this? And can you see if installing the Guest Additions from 3.0.4 fixes the problem? (If possible, try the other things before installing the new Additions, as if it is an incompatibility between the two versions, it would help me to have as much information about it as possible).

[graysky]

I will try HOST+R next time it locks again. Yes, it started w/ the 3.0.x series. I believe I tried 3.0.0 which did it, then 3.0.2 which did it, and now 3.0.4 which still does it. I thought long and hard about what I'm doing that triggers the behavior, but all I do is start up my VM, run deluge then minimize the VM and use the host machine. I'll lock the host screen, switch users, etc. Sometimes I return the VM and the mouse is gone as I describe, other times it's just fine.

I'm running the 3.0.4 GA on the guest.

[Michael Thayer]

Ah, I was just wondering because the log you posted contains "Starting VirtualBox version 2.2.4 Guest Additions". I take it you have installed the 3.0.4 ones since then.

[graysky]

@michael - It just did it again! HOST+R worked. I guess I was mistaken about the GA on 3.0.4. I will install them now and test again.

[graysky]

log file on another mouse crash

[graysky]

Just posted an updated VBox.log

[graysky]

After installing the 3.0.4 GA on the VM, the problem is still present :(

[graysky]

If I do a HOST+I to disable mouse integration, I can use the mouse just fine. If I attempt to re-enable the integration mode, it's invisible and unresponsive to movement again!

[Michael Thayer]

Is this still an issue with 3.0.8, and if so, does it make a difference if you limit the guest to a single virtual CPU?

[Florian Baumert]

I have the very same problem, and its still there with 3.0.8. Limiting the guest to one CPU solves the problem for me.

[graysky]

@michael - yeah, it's still present on 3.0.8 for me :(

[Michael Thayer]

@gravsky: did you try limiting the guest to one virtual CPU to see if that makes a difference?

[Florian Baumert]

@michael: after a few days using only one cpu it still works with 3.0.8. Switching back to two cpus triggers the problem after a few minutes. Looking forward to the result graysky has.

[graysky]

Same... but the whole point is to use multi CPUs w/ my VB :)