VMware Communities
cthree
Contributor
Contributor

Fusion hung on Leopard

My Fusion VM running CentOS5 on a Mac Pro running Leopard has hung.

Console reports:

27/10/07 1:55:38 PM vmware[1805] *** -[NSCFDictionary objectsForKeys:notFoundMarker:]: marker is nil - this will be an exception in applications linked on Leopard.

The vm is running CentOS5. I was compiling PHP 5.2.4. The VM is configured for 1 processor, 1GB RAM.

VMware Fusion is totally unresponsive and had to be killed. FYI.

Reply
0 Kudos
38 Replies
admin
Immortal
Immortal

What version of Fusion is this?

Reply
0 Kudos
cthree
Contributor
Contributor

1.0 and 1.1rc. I have been unable to use VMware at all with Leopard, Time Machine freezes the VMs with scsi errors. I've corrupted and reinstalled about 6 VMs so far this evening. It's starting to bore me.

Reply
0 Kudos
Pelodark
Contributor
Contributor

I have had a similar problem and killed the process to a point where my MacPro hung during reboot. Yikes!! If it's any consolation, Parallels is in a similar situation (killing the process). Something is very wrong and someone needs to step up to the plate real soon.

Reply
0 Kudos
cthree
Contributor
Contributor

I haven't even tried Parallels yet. I am trying to get a VM I use on a web server farm updated to the latest version of PHP and instead spent the entire day dicking around with reinstalling Linux a dozen times and always getting the same result, none. So much for a 15 minute job.

Reply
0 Kudos
Pelodark
Contributor
Contributor

I've given up on the VM stuff for the time being. I fire up another server before I waste any more time and effort trying to do someone else's job.

Reply
0 Kudos
admin
Immortal
Immortal

Continuing discussion from and to concentrate information in one thread.

I did nothing special. I was running 1.0 and it seemed fine running the CentOS5 VM I was running under Tiger. I was compiling the latest PHP and it froze with a spinning beach ball. I hard reset the machine and tried to launch the VM again and fsck found all sorts of problems and when it booted it said some of the RPC libraries were toast starting NFS.

Given that you hard reset the machine, it makes sense that the VM was corrupted. This also applies to your other hangs you describe. The problem is probably whatever caused the hang in the first place.

I upgraded to 1.1RC, got the install done, turned away from it and it was frozen when I got back with a kernel panic related to scsi. I noticed that is coincided with TM activating so I turned it off and hard reset again. Tried to boot, seemed to go ok except now there was a problem loading the network drivers.

To confirm, TM was running during all the hangs (not having played with Leopard yet, how do you know TM is active and at fault)? Can you think of any other possibilities, e.g. do you have File Vault active?

Reply
0 Kudos
yaudet
Contributor
Contributor

Similar situation here; thanks for any assistance you can provide with solving the following:

Used RC1.0 without any issue for since last Beta version and first release; upgraded to RC1.1 after purchasing Leopard. Install went smoothly with successful confirmation message.

However, now unable to launch Fusion other than by launching an application that requires the VM to function (i.e. MS-Excel or Powerpoint for Windows).

Anytime I try to launch Fusion directly, or try to make the VM Library appear, the Fusion application hangs, spinning disks and shows as "application not responding" in the dock.

Also, even after going through the uninstall process, unable to reinstall RC1.0 since the installation process keeps detecting a more recent version and refuses to continue the install process.

Thanks for any assistance in solving this as I've now spent much longer on this than on the Leopard upgrade itself.

Reply
0 Kudos
admin
Immortal
Immortal

However, now unable to launch Fusion other than by launching an application that requires the VM to function (i.e. MS-Excel or Powerpoint for Windows).

To confirm, you mean that launching Fusion via a Windows app kept in the dock does work?

Anytime I try to launch Fusion directly, or try to make the VM Library appear, the Fusion application hangs, spinning disks and shows as "application not responding" in the dock.

What happens if you run a VM directly but not through the docker (e.g. double-click the .vmwarevm bundle in the Finder)?

cthree, does this match up with what you were seeing, or did you have to run a VM for it to hang?

Also, even after going through the uninstall process, unable to reinstall RC1.0 since the installation process keeps detecting a more recent version and refuses to continue the install process.

That's a known issue that was not fixed in time for the release candidate (I assume this will be fixed for the final release). Delete or move /Library/Receipts/Install VMware Fusion.pkg and /Library/Receipts/VMware Fusion.pkg

Reply
0 Kudos
yaudet
Contributor
Contributor

Correct, launching via a Windows app kept in the dock works. Also, as you asked me to check, launching a VM in Finder (.vmwarevm file) also works.

However, launching the Fusion app itself hangs the process... Cannot get to theVM Library step I used to have with RC1.0.

Thanks for the quick response on completing the uninstall, will most likely try going back to RC1.0

Reply
0 Kudos
admin
Immortal
Immortal

However, launching the Fusion app itself hangs the process...

If you haven't already downgraded, what if you start a VM by one of the methods that works, then attempt to open the Virtual Machine Library window? If this fails, you could try deleting or moving ~/Library/Preferences/com.vmware.fusion.plist to clear out the list.

Cannot get to theVM Library step I used to have with RC1.0.

Not sure what you meant by this.

Reply
0 Kudos
yaudet
Contributor
Contributor

Yeah, I guess I could have been clearer: I was refering to the part of launching Fusion where the VM catalog list appears and lets you choose which VM to launch.

However, I completely uninstalled Fusion, re-installed RC1.0, and then re-installed RC1.1, which now launches properly, go figure?

Many thanks for the prompt support, could not have gotten to this point without the complete uninstall info you provided earlier.

Y

Reply
0 Kudos
blackpuma
Contributor
Contributor

If this fails, you could try deleting or moving ~/Library/Preferences/com.vmware.fusion.plist to clear out the list.

I was having problems with Fusion hanging upon startup until I did this specific step.

That did the trick for me.

Reply
0 Kudos
admin
Immortal
Immortal

If this fails, you could try deleting or moving ~/Library/Preferences/com.vmware.fusion.plist to clear out the list.

I was having problems with Fusion hanging upon startup until I did this specific step.

I don't suppose you kept the problematic version?

Reply
0 Kudos
Xipper
Contributor
Contributor

I too had Fusion completely hang. VM is XP SP2 with the latest vmtools installed, was working fine and then stopped resonding and had spinning wheel. After a few minutes the VM display blanked out and VMware was no longer responsive. Tried to quit process for individual VM (using kill) with no luck, tried to force quit with no luck, also tried to kill VMware processes as root with no luck.

I am now being forced to reboot to try and get back to an operable state.

Reply
0 Kudos
Xipper
Contributor
Contributor

Alright, so this is attempt #2 with the same problem. It seemed to be running fine on Friday, the only thing that has changed is the Apple updates for login+keychain that I am aware of.

I had to force power off by holding the power button to get Leopard to shut down. I booted the machine up, loaded my VM and all seemed fine until I right-clicked within an a app and same result. Spinning rainbow wheel, then VM display went black and VMware is now listed as not responding. Force Quit doesn't change anything, none of the Fusion processes seem to quit when requested either via force quit, kill -9 as user or root, etc.

Off to reboot again.

Reply
0 Kudos
Xipper
Contributor
Contributor

Slight update. I noticed that my TM disk (Time Machine) was getting a lot of IO when these problems were occuring. I went ahead and disabled TM for the folder containing my VM, almost immediatley the hung VM window closed. I then rebooted the machine, confirmed TM was still disabled for the VM folders. Started my VM and so far it is working fine, up and running ~30 minutes where it was crashing within 2 minutes previously.

I am guessing that TM is locking those files while it tries to back them up or otherwise causing a conflict. Fusion isn't able to delete the files as it closes to it hangs on attempt to stop the processes.

I'll attempt to enable TM again and test results.

Reply
0 Kudos
KSo
Contributor
Contributor

I have exactly same problem as you do.

After i disabled Time Machine completely, Fusion has not crashed anymore.

Please test and report to here, disable Time Machine (put it to OFF) and see if the Fusion crashes.

Thanks.

Reply
0 Kudos
hoosiermac
Contributor
Contributor

What if you disable TM from backing up the Virtual Machines folder? I came here for the same issues and am going to see if this fixes the problem of Fusion hanging.

I also notice that since I use a TM Server on Leopard Server that the backup partition stays on the desktop after Fusion hangs.

Reply
0 Kudos
dshold
Contributor
Contributor

I have had the same hanging problem I've excluded my Virtual Machines directory - as well as the Applications/VMWare directory and Library/Application Support//VMWare. So far - I haven't seen the same hanging.

Reply
0 Kudos