Link to home
Start Free TrialLog in
Avatar of scott4381
scott4381

asked on

VMWare Player 5.0.1 hanging on Windows 7 64-bit

Hello all,
I am running VMWare Player 5.0.1 on Windows 7 Ultimate 64-bit.  Just built the computer, 32GB RAM, Intel Core i7-3750K processor, so it's got plenty of power.  Quite often, when I start up one of my VMs or go back to a VM that's already open, the VM guest will seem to freeze and I can't even move the mouse outside of the VM window - not even Ctrl+Alt works.  Usually I can do Ctrl-Alt-Del however to get to task manager, but even then I can't scroll and select properly to shutdown VMWare Player.  I usually just have to wait a couple of minutes until it unfreezes.  It seems to work better after a reboot (of the host desktop).  I have more than enough RAM free and the CPU isn't pinned either.  Anyone got any ideas of what I can look for to troubleshoot this?  The Windows Event Logs show nothing useful.  Thanks!!!
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

what specifications, how much memory and cpu have you assigned to the VM?
Avatar of scott4381
scott4381

ASKER

hanccocka: I have had this happen with several VMs, but the one that it occurred with today has 4GB RAM, 2 CPU cores, 200GB HD.  It's a Linux VM.  But I have seen this happen with Windows VMs as well.
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I've requested that this question be deleted for the following reason:

Not enough information to confirm an answer.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
hanccocka's reponse led me to reducing the vCPUs (to only 1 vCPU on each VM) which seems to have been the fix as far as I can tell.