![]() ![]() but the sad conclusion is that we still have no idea what's going on, and no idea how (or if) it can be fixed. I could continue telling the story of all the things that we've tried that have failed to lead us towards any sort of solution. That was probably our best chance to make progress on understanding it. We had one Mac here at VMware which encountered a sleep/wake failure or blank screen on wake occasionally, right up until we started investigating it, at which point the problem went away – completely and permanently – despite our very best efforts to avoid making any change that could conceivably alter the problem's reproduction. It doesn't help that the problem seems to be almost impossible to reproduce or to correlate with any specific configurations or actions, and that we really don't get any useful information out of OS X when it happens. We have an extraordinary team of engineers, but we're all pretty well stumped. I can safely say that I've personally expended more effort on this one issue than on any other single problem I've ever worked on at VMware, and I'm just one of the team who've spent time on it. Our support stats show that a small but noteworthy proportion of our install base is affected, so we're very aware that there is a real problem here. Please don't assume that we have been ignoring it. The longer answer is a story of a futile battle to troubleshoot a rare and complicated problem. That said, we still do not understand the root cause of the problem and still cannot reproduce the failure here, so it is not impossible (though I'd consider it unlikely) that we have somehow fixed it without realizing. The short answer: There is no change in which is known to address the OS X sleep/wake issues which seem to correlate with the use of VMware Fusion. Here's a a slightly-reworked excerpt of my previous reply on this topic: VMware has acknowledged this as an actual bug in the past, but no fix has been forthcoming. Suspending all VMs before putting the computer to sleep also prevents the problem from occurring, even if VMware Fusion itself is still running and its various. ![]() Using pmset to disable hibernation entirely DOES work, but with the drawback that the laptop will eventually run out of power while asleep without ever writing the contents of RAM to disk.It has persisted across the last few versions of VMware Fusion (7.x and 8.x at least not sure about 6.x.) Resetting the PRAM or the SMC has no effect. As far as bugs go, this is a pretty severe one. That forces a full reboot, leading to the loss of all open work in all applications across the host and all guests. And when the sleep image gets corrupted, the host OS will kernel panic on resume. But in some cases, Fusion interferes with this process, leading to a corrupted sleep image. The computer restarts, writes the contents from the sleep image back into memory, and you resume where you left off. Waking up from hibernation is where the problem happens. ![]() But after a few hours (or when the battery drops below a certain percentage,) the computer hibernates. When you put a Mac to sleep, it initially enters regular sleep.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |