"Fatal Error in Virtual Machine Monitor"

U

uesjd

Bit poster
I get this error fairly frequently -- actually, come to think of it, I get it every time I start a Virtual Machine for the first time after booting OS X. If I then restart the Virtual Machine, it usually works fine the second time. The dialog box that reports this error asks to send a log to Parallels, and each time it happens I allow it to be sent.

What does this error mean? Is there anything I can do to fix it, or is it a bug that Parallels has to fix in the next RC (or full release)?
 
I've only seen it once, and it was the one time I upgraded Parallels to a new version and forgot to reboot before starting it up.

My only guess to a fix would be to uninstall/reinstall Parallels and see if it goes away.
 
uesjd said:
Anyone? Am I the only person who gets this error?:confused:
Click to expand...
I get this error all the time when trying to run copy-protected business software. It was fixed in 3120 but is re-broken in 3150. I have allowed numerous bug reports to be sent automatically and have also written a longer descriptive note to beta@parallels.com. I need this fixed before release, because this is software I must run or drag around an old, extra, heavy, windows box to do so.

Crashes occurring on 15" MacBook Pro Core 2 Duo 2.33; 2048 of RAM, 1024 to Parallels, and began when I upgraded and installed the new Parallels tools.

Phil K
 
I'm now using 3150 but it happened with 3120 also. And I have allowed numerous bug reports to be sent automatically in both versions.
 
psyfil said:
I get this error all the time when trying to run copy-protected business software. It was fixed in 3120 but is re-broken in 3150. I have allowed numerous bug reports to be sent automatically and have also written a longer descriptive note to beta@parallels.com. I need this fixed before release, because this is software I must run or drag around an old, extra, heavy, windows box to do so.

Crashes occurring on 15" MacBook Pro Core 2 Duo 2.33; 2048 of RAM, 1024 to Parallels, and began when I upgraded and installed the new Parallels tools.

Phil K
Click to expand...

I don't even get that far - it happens to me while trying to start Windows.

I'll try reinstalling Parallels.
 
You must log in or register to reply here.
Back
Top