Mouse Pointer Integration Error

[AzJazz]

Hi -

I am running a WinXP Pro SP3 Guest under Win7x64 SP1.

I have a new Asus Sabertooth Z77 motherboard, and I installed Win7x64 and VBox 4.2.6 from scratch, and installed my WinXP guest from scratch.

I have a problem where I frequently see the following error during VM startup:

The virtual machine reports that the guest OS does not support mouse pointer integration.
The mouse still seems to work OK after that, but my custom cursors are all lost when this happens.

I never saw this problem on my previous Asus P6T Deluxe V2 motherboard.

How do I fix this problem?

Thanks,

AzJazz

[Perryg]

Make sure that the guest additions are installed/properly installed in the guest

[AzJazz]

Hi, Perryg - I already installed the Guest Additions when I've had this problem. Is there a way to find out if they are "installed properly"?

[mpack]

Post the VM log file, as a .zip attachment. The VM log file is called "VBox.log", and can be found in the "Logs" subfolder of your VM folder.

[AzJazz]

Here's a VM log where I saw the mouse error.

[mpack]

The log says that you do have GAs installed, but it also says that the VM is suspended, not shut down. I suggest shutting down the VM properly (not saved state), then restart. Also, I suggest setting the guest RAM to 1GB. A 32bit XP VM has no use for 3GB RAM.

How did you install the GAs? If it wasn't done in safe mode then I suggest turning off 3D acceleration.

[AzJazz]

Originally, I did do the GA install for 3D acceleration in Safe Mode. I read elsewhere that the mouse problems were due to the 3D acceleration, so I uninstalled the GA in Safe Mode, then reinstalled the GA in normal mode, with 3D acceleration turned off.

I'll lower my memory settings, though I expect that won't have any effect on this issue.

Though the mouse problem may be related to restoring a saved VM, I have also seen this error during a normal boot-up. I have also saved VMs & restored them for weeks without the mouse issues on my old motherboard.

[AzJazz]

I created a new VM, without turning on 3D acceleration, and I still see this error - primarily when restoring a "saved" VM (but, not always).

Has anyone found a solution to this?

AzJazz