A number of people have reported extremely slow boot times (on the order of minutes) after upgrading to Fusion 2.0. We have not been able to reproduce this in-house, so as you might imagine it's a bit hard for us to debug. This thread is to concentrate focus and give us a single place to ask questions and provide updates. Note this thread is only for slow boot times, it does not apply to slowness after boot -- that may be a different issue.
If you're seeing slow boots, in addition to trying these, please know what works and what doesn't. In addition to potentially helping you work around the problem, knowing what is effective will help narrow down our search for the cause(s).
Bonus: If you're in the SF Bay area, would it be possible for us to get our hands on your computer? This obviously isn't practical for most people, even those in the area, but being able to see it ourselves would be the fastest way to figure this out.
If you're seeing slow boots, in addition to trying these, please know what works and what doesn't. In addition to potentially helping you work around the problem, knowing what is effective will help narrow down our search for the cause(s).
- What guest OS are you seeing this with? (Note: so far, I believe everyone who's reported this has been running some Windows variant) Be sure to include 32-bit vs 64-bit and service pack level.
- Is this a Boot Camp virtual machine? If it's a normal virtual machine, was it imported from somewhere else (e.g. Boot Camp, Parallels, VPC)?
- Do you have "Allow your Mac to open applications in the virtual machine" set in the virtual machine's Sharing Settings? Try disabling this - this has helped some users.
- Do you have any USB devices (e.g. an iSight) connected to the virtual machine while it boots? Try disconnecting them - this has helped some users.
- Some third-party software may cause slowdowns (I've just heard a report that, for example, Daemon Tools and Boot Camp drivers caused one user problems). Try disabling unnecessary services to see if any of them are responsible.
- Have you upgraded Tools? If you uninstall Tools, does the problem persist?
- Have you upgraded the virtual hardware? If you downgrade the virtual hardware (Virtual Machine > Downgrade Virtual Machine, only doable when the virtual machine is powered off), does the problem persist?
- If you check out All Processes in Activity Monitor in OS X, is anything taking up a lot of CPU? If vmware-vmx is taking up a lot of CPU, please collect a sampling report (select vmware-vmx, then View > Sample Process)
- If you check out the Disk Activity in Activity Monitor in OS X, is there a lot of disk activity during the slow boot?
- If you check out vmware.log (see A Beginner's Guide to VMware Fusion), are there mentions of READs or WRITEs taking a long time to complete?
- System Profiler report (please zip)?
Bonus: If you're in the SF Bay area, would it be possible for us to get our hands on your computer? This obviously isn't practical for most people, even those in the area, but being able to see it ourselves would be the fastest way to figure this out.