I had made a previous post a while back about the mouse being choppy while using the VMware console with Server 2008. I stated in that post that as of that writing, there was no fix for 2008 R2. There appears to be a fix now, however. The server I’m running is ESX 4.1.0-348481 (which is the RTM of ESX 4.1 Update 1). To get the mouse choppiness to stop, open up Device Manager and select the display adapter. Update the driver and manually choose the location of the driver (which is located in C:\Program Files\Common Files\VMware\Drivers\video). After selecting that location and clicking “Next”, it automatically found the proper driver and installed it, and after a reboot, the mouse choppiness was fixed. I had already enabled hardware acceleration for the adapter, so if you update the driver and are still having issues, ensure you’ve enabled hardware acceleration. I’m also running the latest version of VMware Tools on this machine, so if this directory doesn’t exist, or this doesn’t work for you, make sure VMware Tools are up to date.
One of the best things about virtualization is the ability to take snapshots of virtual machines while running or while powered off. This saves countless hours spent taking backups of VM’s prior to upgrades or critical reconfigurations. If the change causes problems, simply revert back to the snapshot that you took beforehand.
It is best practice not to keep snapshots for an extended period of time, as delta (change) files related to the snapshot begin to grow and can become unstable at some point (I’ve had instances where my VMware server glitched out and ate up all storage space in my datastore by creating snapshot files). This being the case, it is best to purge unneeded snapshots as soon as you’re certain you don’t need them anymore. However, what if you have dozens or hundreds of VMs and don’t remember which ones have snapshots? You could click on each VM and see if there are any snapshots associated with it, or you can use this technique I just discovered this morning to view all snapshots in your datacenter. This is only applicable to vSphere 4.0+.
Open the vSphere Client and browse to Home –> Inventory –> Hosts and Clusters (in the top navigation pane). Select the name of your datacenter in the left-hand pane. Click the “Storage Views” tab. For View, select “Reports”. Ensure that “Show all Virtual Machines” is selected from the dropdown menu directly below the “Reports” button. There should be a column that says “Snapshot Space”. If not, right-click the title columns and select “Snapshot Space” to add that column. Then click the “Snapshot Space” column to sort it by size. You can ignore VMs that have a Snapshot Space of a few bytes or a few KBytes. Look out for ones that have a few GB of Snapshot Space. These are the VMs you need to remove snapshots from. Picture below has key areas circled.
I use VMware ESX/ESXi on a daily basis. While I use LogMeIn as my remote management software for all computers in my environment, the vSphere Client also provides a console view to access my VMs. Sometimes it’s more convenient to use the vSphere console, when performing tasks like modifying settings on the fly or inserting ISO files.
The VMware Tools application that should be installed on all VMs provides a number of enhancements, including support to allow for smooth mouse movement. However, I found that my Windows Server 2008 VMs were having very choppy mouse movements, even with the VMware Tools installed. The solution for this is to set the hardware acceleration for the video adapter of the VM to “Full”.
To do this, open the Display Resolution settings by right-clicking on the desktop and selecting “Personalize”. Then select “Display Settings”. In the Display Settings window, click “Advanced Settings”, click the “Troubleshoot” tab, click “Change Settings”, then move the Hardware Acceleration slider all the way to the right, then click “Ok”. You will be prompted to reboot. After you reboot, your mouse movements should nice and smooth.
This only works on 2008, not 2008 R2. Feel free to try this on previous versions of Windows if you’re having mouse issues, although this setting is usually in place by default, but it’s a confirmed bug with 2008 R2.