I recently bought a new macbook pro, tht is up to date with Mavericks 10.9.1
I bout Fusion 6 and migrated my VM from my old macbook that was running Fusion 4.
All seemed to go well.
The VM performs awesomely.
The problem is when I put the Macbook to sleep... I get the 'infamous' Sleep Wake Failure when I wake it up, and the macbook is restarted.
I say infamous, as there are many users of mavericks experiencing this for all sorts of causes.
In my case I singled the cause down to my VMware Fusion 6, running a Win7 Pro machine. If this is still running when I sleep the Macbook then I get the Sleep Wake Failure every time I wake the MacBook. If I shutdown or suspend the VM first, then this does not happen.
Please can this be looked at...
I used to work in this way with my old macbook (OSx Lion, Fusion 4) and never had issues sleeping the macbook and resuming.
I can confirm having same issue on MBP Retina 10,1 (mid 2012).
I can single out VMware Fusion because:
- Used Mavericks 10.9.1 for a couple of months with Fusion 5. No reboots.
- Upgraded to Fusion 6 last week. No other system changes. Had several reboots since then. I don't think it is as consistent as Zaudio, but I will investigate further (unless I downgrade to Fusion 5).
It sometimes reboots in my bag when I enter the Wifi-coverage at work. I wonder if the "mini-wake" OSX does when recognizing the wifi is related to Power Nap. But the checkbox says "Enable Power Nap while plugged into a power adapter", doesn't make sense. Would like more insight into that area.
Just a note about my attempt to create a support request for this.
Filled out the online form (with Chrome), which gives the error:
Unable to Complete Your Request
The content is unavailable. Contact information is also available at Support Phone Numbers.
Not very good. Anyway, called the support number listed for Sweden. After multiple selections it informs me that support is open certain hours PST. That's 9 hours from Central European Time.
Seriously VMware, the support form does not work and you have no phone support during the office hours in Europe? Why am I paying for this? I used to recommend VMware software.
I am facing exactly same problem. I even gave back my MBP and asked for a replacement and I have the same problem. I gave different amount of RAM and does not work.
So what is the resolution?? I could have bought Parallel instead?
Same issue here -- Retina MBP, late 2013, with 16 GB of RAM running a Windoze 8.1 VM from the Bootcamp partitition. It doesn't happen all the time, but often enough that it is really frustrating. It is absolutely VMWare doing it, too -- the VM has always been running when it happened. I usually remember to shut off the VM now, so I can go for weeks without a reboot, until I forget, and then it happens.
This really needs to be addressed.
Same for me too on the latest 13" retina macbook pro running wo all software up to date. I can recreate if VMWare is running. If not running the macbook sleeps and wakes fine. It appears to be an issue if the macbook is left closed/sleeping for a while. If I close and reopen a few minutes later it works fine. It also appears to only happen if a virtual machine is open so I suspect there is a strong chance this is linked to the issue with Mavericks where users are noting that having a USB external drive causes a similar issue.
Fingers crossed either a VMware or Apple fix is released soon until them I'm closing VM Ware down before I close my lid which is a bit of a pain but I can't risk corrupting any files.
Same problem here.
MacBook Pro Retina 15-inch, Late 2013
OS X 10.9.2
VMWare Fusion 6.0.2
Guest OSs (same problem with any): Windows 7 x64, Windows Server 2003, Windows Server 2008 R2 32/64, Windows XP, Linux Ubuntu 10 64-bits
If the display sleeps (after turn display off timeout) or closing lid, the computer start but without display. Even if you try using any graphical remote software.
To avoid to force shutdown, I enable "Remote Login", then I login via SSH to my MacBook pro to remote reboot the machine, trying to avoid damage my OS.
password: (Administrator password)
And wait ...
I've been dealing with this problem for months and I've tried every fix I can find online, except uninstalling Mavericks, which seems to be the only real consistent fix known.
VMWare support was no help. After several phone calls and emails, they were having me try the same fixes I was finding online ... they had no clue.
This problem seems to be Mac specific since most forum posters do not mention VMWare.
This problem has killed the Mac experience for me, which was utopia before upgrading to Mavericks soon after it was released.
I see an error report EVERY morning stating the computer has rebooted and VMWare has crashed. I'm now conditioned to close everything important in Windows or I will lose it.
Retina, 15-inch, Early 2013
Processor 2.7 GHz Intel Core i7
Memory 16 GB 1600 MHz DDR3
Graphics NVIDIA GeForce GT 650M 1024 MB
Software OS X 10.9.2 (13C64)
Bootcamp Windows 7 x64
Exact same issue here. Updated to fusion 6.0.3, no avail. Before was doing it randomly, now at least is consistent, it reboots every night
I wonder how f**ed up is my windows file system after so many reboots...
Also, after upgrading to mavericks, performance of the VM degrades in time. At the beginning is super fast (how it should be on a 16g ram 4 core sdd retina mbpro) but after a few hours even opening a new window takes ages...
And there is no rollback, I am going to have to re-install Lion and dump Mavericks in the backyard.
Apple should pay me a full per-hour consultancy fee for the time I am loosing...
I managed to fix this by going to the Virtual Machine Settings, clicking Advanced, and then checking the "Pass power status to VM" checkbox.
I left my VM running overnight with the lid closed and the next day the mac woke from sleep successfully and the VM was suspended.
Hope this helps someone...
Macbook Air 13-inch Mid 2013
OSx Mavericks 10.9.2
VMWare Fusion 6.0.3
Windows 8 x64 Virtual Machine
Hey thanks for this suggestion,
I have applied it to my current VMs and will se if it proves a robust solution. I have been diligently suspending all my VMs prior to closing my lid todate... your solution has hope as a way to automate this should I forget.
This issue ("sleep wake failure") also happens on the new MAC Pro 6,1 late 2013 servers running VMware Fusion (version 6.0.3). I'll have to try that work-around (Pass power status to VM from Settings > Advanced) provided by ofairfoul.
I think I found an solution. I can't remember but I read somewhere to go to Advanced settings and make sure to turn on Pass power status to VM for all VMs. I used get crashes and reboots, but after turning on this setting, I have had ZERO reboot!
Agreed. The fix is working perfectly so far on my Mac Book Pro Laptop and MAC Pro 6,1 trash cans. Previously I could reproduce the issue on demand. The fix was posted by ofairfoulin this same thread we're in now (here). This also works great for running nested ESXi VMs on Fusion. By default the "Pass power status to VM" box is un-ticked on those. Simply checking the box allows me to hibernate my laptop (or server) without issue while Fusion VMs (including nested ESXi) are running.
I also have had zero issues since trying the Pass Power to VM suggestion by ofairfoul as I posted above. Thanks dude for the suggestion; seems we have an interim fix until VMWare come up with something permanent
I suggest then you eliminate another app as the cause then. It's what I did to discover Fusion being my problem. The pass power to VM option certainly seems to resolve mine and others issues with that app. If you search the sleep wake failure globally you will find other apps can also trigger it. JMHO