Fusion 6.0.2 and OSx Mavericks 10.9.1 - Sleep Wake failure unless I shutdown or suspend my Win7Pro VM before closing lid

[Zaudio]

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.

Thanks

Simon

[CuriosTiger]

I was seeing this in Mavericks, and wound up reverting to Snow Leopard. Saw it against last night, this time with Fusion 7.0 Pro and Yosemite 10.0.

Just upgraded to Fusion 7.0.1 and Yosemite 10.10.1. Now I'm seeing an extreme slowdown. Researching if this is the same as the interrupt storm bug that was reported elsewhere, and which I'd had to work around in 10.10.

I have not put my computer to sleep since upgrading. Will report back if the corrupt sleep image bug is also still happening.

[msmithers]

Since Yosemite 10.10.1 I haven't had any crashes. Has anyone else found this?

I'm not suggesting it's fixed. I'm just surprised that I've forgotten to pause my VM's lately and that they've still survived with the lid closed and on battery overnight.

[NickTerryUK]

Adding a 'me too'

rMBP 15" (Early 2014), OS X 10.9.5

Linux 14.04 VM

Was utterly stable with Fusion 5.0.5 - no issues at all with sleep/wake up of Mac.

Upgraded to Fusion 7.0.1, Mac now restarts every night at some point. Yesterday it did it in my rucksack as I walked into the house.

[hatertot]

fix the problem please.   I'm on 6.0.5, but if I knew you fixed it in 7 I would upgrade in a heartbeat.

[nopslide]

While this whole situation is pretty ridiculous the pm settings in Re: Fusion 6.0.2 and OSx Mavericks 10.9.1 - Sleep Wake failure unless I shutdown or suspend my Win7P... do mitigate the problem. If you actually have work to get done unlike any osx users at VMWare apparently... I'd suggest just mirroring those power settings and moving on. VMWare is obviously not capable of remedying this issue.

[Paperinick]

Well, somebody has been working on a build with instrumentation for this bug since October 17th. So I am confident progress will be made soon.

[SpikeeFix]

This may be covering old ground, but it seems like this might have something to do with the VM being the active window when closing the MacBook, AS WELL AS Windows automatically installing updates. Thoughts?

[PippoFlash]

Installing the latest Yosemite doesn't fix. I work on a complex VM setup and it takes me a long time to get the VM ready to work again, and last week again, at an appointment with a client, I had to re-do everything in front of him. This is the last time.

I am moving to Parallels, but I DO CLAIM MONEY BACK FOR FUSION 7 UPGRADE.

If someone from Vm-ware is reading this, can you please contact me?

I am a loyal customer since Fusion3, and I upgraded to 7 IN SPITE of this bug, confident you would solve it. But since you are not giving a **** about us, I am moving to the competition, but I do expect vm-ware to refund my latest, useless upgrade.

On vm-ware website there are only paying support tickets, and forms to contact sellers, but there is no way to contact your customer service.

How should I proceed? Whom should I contact?

thank you

Filippo

I have also created a new post here:

Claiming money back for Fusion7 upgrade since bug never resolved by vmware team, and moving to Paral...

If someone else wants his latest upgrade refund and move to parallels lets have our voices heard.

[Paperinick]

Keep us posted if you succeed in getting your money back.

What I've noticed is that in 7.1 release notes the bug is listed as a known issue; I don't know if it's the first time.

VMware Fusion 7 and VMware Fusion 7 Professional Release Notes

Maybe by release 10.23, when HPreg is finally done with vacation time, they might decide to address the issue. :smileylaugh:

[erhudy]

I also frequently experience this issue and have to remember to suspend my Windows 7 VM prior to putting my computer to sleep, or it's not likely to come back. After restarting the system, it usually barfs out something similar to this in the crash reporter:

Date/Time:       2014-12-15 15:53:03 -0500

OS Version:      10.10.1 (Build 14B25)

Architecture:    x86_64

Report Version:  21

Event:           Sleep Wake Failure

Steps:           1

Hardware model:  MacBookPro10,1

Active cpus:     8

================================================================

Code: 0x13006c00                                                                                 

System Profile:

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (7.15.124.12.10)

Bluetooth: Version 4.3.1f2 15015, 3 services, 27 devices, 1 incoming serial ports

Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4

Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020

Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020

USB Device: Hub

USB Device: FaceTime HD Camera (Built-in)

USB Device: Hub

USB Device: Hub

USB Device: Apple Internal Keyboard / Trackpad

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

Serial ATA Device: APPLE SSD SD256E, 251 GB

Model: MacBookPro10,1, BootROM MBP101.00EE.B05, 4 processors, Intel Core i7, 2.7 GHz, 16 GB, SMC 2.3f36

Network Service: Wi-Fi, AirPort, en0

Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In

Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB

[PippoFlash]

I managed to get a refund for the fusion 7 upgrade. I have been called by a representative and they fixed it for me. Still Parallels feels like a toy compared to Fusion, as son as they fix the issue I'll be back on Fusion. Cheers guys.

[stevenkan]

Happy New Year from Win7/64 running on Fusion 7.1.0 on 10.10.1 on a mid-2014 MBP 15" Retina with NVIDIA GeForce GT 750M. I, too have been seeing this prob

****** rebooting *******

problem. I looked at the Problem Report, and it shows that it happened at 8:56 PM last night:

Date/Time:       2015-01-06 20:56:53 -0800

OS Version:      10.10.1 (Build 14B25)

Architecture:    x86_64h

Report Version:  21

Event:           Sleep Wake Failure

Steps:           6

And that's exactly 10800 seconds (3 hours) after I closed the lid. Not surprisingly, I have standby delay 10800 in my pmset, so that's when the machine attempted to hibernate.

I can't use gfxstatus to force integrated gfx because I run an external monitor when I'm at work, so I'm going to try hibernatemode = 0 right now. We'll see if that helps. If I don't report back, it's because I've thrown the machine out the window.

[PippoFlash]

Really sorry to say so... but I got contacted by a very helpful VmWare customer care guy, and managed to get a refund for the Fusion 7 upgrade.

I moved to Parallels, which feels like a toy compared to Fusion, but I can finally close the lid of my Mac without being afraid, at the next appointment, of having to say to a client "ops sorry my VM just rebooted".

As soon as this bug will be fixed I will move back to Fusion, no question.

PS

I have hibernation switched off, forced gfx, changed all sort of settings, at no avail. Still random reboots when lid is closed. Sometimes yes, sometimes not. Attached to the plug or in battery mode, nothing consistent.

Good luck!

[Zaudio]

Sorry you never managed to get a workaround to work for you.

The pmset settings I posted a good while back (basically hibernatemode = 0) have worked for me and I've not had a single KP since. That is many months now.

So there must be another factor in the setup where we differ. I never messed with the graphics card settings... using whatever the default was.

Simon

[PippoFlash]

It did work for a while, then strangely enough it started again. I tried all combinations. Until one day I realized I should invest my time differently.

I am happy it worked for you. I like Fusion far more than Parallels...

But now I have a machine that can actually hibernate...

[WGeerts]

I had exactly the same problems on identical MBP 11,3 /VMware 7.1.0 and with this pmset this morning it wake up correct. Thanks for the clarifications and instructions!

[Paperinick]

Today my Mac builtin screen stopped working.

Now I am suspecting that this has always been an hardware issue.

I will likely take it to an Apple Store and keep you posted.

[msmithers]

I haven't had the crash since the Yosemite 10.10.2 update. (I'm running Fusion 7.1.0.)

Anyone else had a crash since then?

[rdsharma]

Yes, I still have issues with waking from sleep daily and about once a week my computer will freeze up. (10.10.2/7.1.0)

[Paperinick]

On October 24th 2014 HPReg was telling us that he was working on an instrumented build.

On November 12th, he was working on other bugs and taking a vacation.

It's February 12th 2015 and still no traces of an instrumented build (like it's the only option to observe this obscure bug!).

In the meanwhile... two days ago went to the Apple store and got a new MacBook Pro, identical to the one I have. I installed Windows 7 on bootcamp, installed VMWare, put the laptop to sleep for the day and *bam* got a Kernel Panic.

This story that VMWare is unable to repro the bug "in-house" is starting to smell a bit like BS.

Dear VMWare engineers, if you want to repro the bug, these are the steps:

1) go to an Apple store, there's one conveniently located in Palo Alto downtown, and buy a MacBook Pro, 15" with NVidia (the "$2,500" model)
2) install Windows on a bootcamp partition

3) install VMWare and import the bootcamp partition as VM (install the tools, etc.)

4) close the lid and leave it closed for a few hours.

5) turn on the lid and enjoy the kernel panic.

If the competing products were slightly better, I would have already arranged for a refund. Instead I am stuck in the "remember to turn off the VM before closing the lid" mode.

Thanks