Unable to communicate with hypervisor! -any way to diagnois and fix

D

davidpitkin

Bit poster
Hi,

I have a MBP and almost 95% of the time when I attempt to start my instance of Parallels Desktop I receive what is now for me the dreaded unable to communicate with hypervisor (UTCWH).

I have attempted to install the beta, adjust settings uninstall and reinstall all in vain, UTCWH haunts me.

Does anyone know what I can do to check the status of the hypervisor?
 
I had this among several problems. I reinstalled OSX and the problems all went away. Yes, it's a drastic solution, but it worked. I'm still looking for the exact problem. (I have a backup image to play with).

Specifically, I uninstalled Parallels, backed up the disk, did a clean install of OSX, updated it from the apple site, used the migration assistant to grab everything it could from the original image, migrated by hand the developer stuff the assistant didn't find, and was back in business.
 
Okay, I tried a permission fix from Disk Utility and a reboot.

What else should be running, any other way to see if the hypervisor is able to communicate?
 
I'm having the same problem

I bought a new Mac Pro with 2GB of ram and 2.66 GHz processors.
Parallels was the first software I installed. I get the dreaded "Unable to communicate with hypervisor" message every time.

After reading on this forum, I tried build 1848 -- same problem. I installed the beta build 1862 -- same problem.

I have installed and reinstalled Parallels, with many reboots, and I have downloaded the packages several times. I am stumped.
 
Thanks.

I found that thread on my own, and with the "sudo nvram bootargs=...." workaround, I am now able to install Win XP. I expect I'll have to fiddle around with the network settings.

I am eagerly awaiting a version of Parallels which does not require disabling the the 64-bit support on my Mac.
 
I find I have to start Windows twice most of the time; and after I have been using Parallels all day Windows won't start at all and I have to reboot my Mac.
 
You must log in or register to reply here.
Back
Top