Search

Language:  
Search for:

Available article translations:

Mouse cursor is invisible in virtual machine

APPLIES TO:
  • Parallels Desktop 10 for Mac
  • Parallels Desktop 9 for Mac

Symptoms

I would like to connect one mouse directly to the virtual machine and use it exclusively for controlling it while other mouse is used to control the Mac.

There is a problem: when virtual machine gains focus from ‘indirectly’ connected (shared) mouse and then subsequently loses it, the mouse which is connected directly is no longer visible inside virtual machine’s window.

So I can use directly connected mouse to control the virtual machine but the problem is that the cursor is invisible. This setup works only when 2 devices control same cursor but when I try to desynchronize (make 2 cursors – 1 in virtual machine and 1 in Mac), the cursor in virtual machine becomes invisible and never returns

Cause

This type of configuration is not officially supported.

Resolution

  1. Shut Down virtual machine.

  2. Open Virtual Machine configuration
  3. Go to Hardware > Boot Order > and paste in Boot Flags box:

      video.hw_pointer=0
    

In Windows guests there still will be situations where cursor becomes invisible. Also there may be occasional screen flickering. In summary, the above solution will work fine when using virtual machine for simple tasks such as document processing, but heavier use (like games or 3D software) may make system unstable.

NOTE t:he above solution will not work for Mac OS and Linux OS guests.

There is only one hardware cursor in Mac OS and it is used in vrtual machine in normal mode. In case you want to use separate mouse and keyboard directly in OS X virtual machine, guest OS X draws the cursor in its own frame buffer, which causes slow performance, especially for 10.10 OS X guests. Therefore separate mouse connected directly in guest OS X, may run slow or misbehave. There is no way around for it.

Search words:

slow mouse

invisible cursor

separate mouse

PD




1e5db16426987d561060acdf56d947b4 48e7cf384e3b46432e32e6040476f122 33c4522b6fa9ca8e050f19b889fb58f1 fb0e3c3e2247964007f03acae43ffd0d

FEEDBACK
Was this article helpful?
Tell us how we may improve it.
Yes No