VMware Fusion 2 Beta Fails to Start
May 9, 2008 | 3 Comments
I have been using VMware Fusion 1.x for quite some time now but recently I decided to upgrade to version 2 Beta. I downloaded VMware-Fusion-2.0.0-89933.dmg and installed it over VMware Fusion 1.1.2. After successfully installing the software I was able to use it without indications of potential problems to come. However, today when I attempted to launch VMware Fusion the program simply bounced up and down a few times on the dock but failed to open. I tried to open the application multiple times but without luck. I wanted to post my experience on VMware Communities but it is currently down for maintenance.
Yesterday, I remember accessing my boot camp partition that has Windows Vista Business Edition installed. The application attempted to install VMware Tools soon after the first login however the process was painfully slow and it seemed liked the virtual machine had froze so I forced it to shutdown by using the “Shutdown Guest” feature. I turned on the guest once again but this time I selected to boot into safe mode and perform a clean shutdown of the guest OS.
Next I opened a virtual machine running Windows XP Professional (SP3) but again the installation of VMware Tools was painfully slow. This time I allowed the system to finish the installation.
Lastly I created a virtual machine to run Ubuntu Linux 8.x. The procedure went as expected but I opted not to install VMware Tools as it was getting a bit late.
I suspended the state of both the Windows XP and Ubuntu Linux virtual machines before I quit the application and shut down the computer. Today I cannot access any virtual machines. VMware Fusion 2 Beta fails to start. Sometimes I can briefly take a glimpse at some of the virtual machine configuration settings but then the application quits a few seconds thereafter.
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 3 GB
Bus Speed: 800 MHz
Boot ROM Version: MBP31.0070.B07
SMC Version: 1.16f10
Sudden Motion Sensor:
State: Enabled
System Software Overview:
System Version: Mac OS X 10.5.2 (9C7010)
Kernel Version: Darwin 9.2.2
Boot Volume: MacHD
Boot Mode: Normal
Computer Name: user00-mbk
User Name: user00 (user00)
Time since boot: 3:59
After attempting to launch VMware Fusion multiple times I noticed the following entries in the console utility.
5/9/08 9:02:37 PM [0x0-0x39039].com.vmware.fusion[828] *** Memory Leak *** DUIDocument: 3 instance(s) leaked
5/9/08 9:02:37 PM [0x0-0x39039].com.vmware.fusion[828] *** Memory Leak *** PLLibraryEntry: 1 instance(s) leaked
5/9/08 9:02:37 PM com.apple.launchd[498] ([0x0-0x39039].com.vmware.fusion[828]) Exited with exit code: 255
5/9/08 9:05:14 PM com.apple.launchd[498] (0x1087f0.Locum[827]) Exited: Terminated
5/9/08 9:05:50 PM com.apple.launchd[498] (0x108a90.Locum[841]) Exited: Terminated
So I attempted to launch VMware Fusion directly but instead I received a message in a terminal window (beach ball continuosly spins).
Last login: Fri May 9 17:52:20 on console
/Applications/VMware\ Fusion.app/Contents/MacOS/vmware ; exit;
user00-mbk:~ user00$ /Applications/VMware\ Fusion.app/Contents/MacOS/vmware ; exit;
Using log file /Users/user00/Library/Logs/VMware Fusion/vmware-vmfusion.log
Cannot load message dictionary “/Library/Application Support/VMware Fusion/messages/en/tip_list.vmsg”.
Could not open /proc/net/dev
SGMAC: XXX: SGHostEnumerate not yet implemented
ASSERT bora/lib/disklib/sparseChecker.c:1716 bugNr=167956
VMware Fusion Error:
VMware Fusion unrecoverable error: (vmfusion)
ASSERT bora/lib/disklib/sparseChecker.c:1716 bugNr=167956
A log file is available in “/Users/user00/Library/Logs/VMware Fusion/vmware-vmfusion.log”. Please request support and include the contents of the log file.
To collect data to submit to VMware support, run “/Library/Application Support/VMware Fusion/vm-support.tool”.
We will respond on the basis of your support entitlement.
Press “Enter” to continue…
Comments
You must be logged in to post a comment.