VMware Communities
Thomas_McKane
Contributor
Contributor

Fusion 8.5 on MacOS Sierra Crashing Often

After any of my Windows VM's boot up, they freeze more often than not and I get an error that Windows has stopped responding and needs rebooted.  I sometimes have to reboot 3 times before it will actually boot up and be usable.

This NEVER happened with previous versions of Fusion.

PLEASE FIX THIS BUG

101 Replies
Wilddev
Contributor
Contributor

I am still having this issue on 10.12.2 with Fusion 8.5.3. Happening on a new MBP brought in August. When Fusion crashes, all VMs crash and ask to be restarted. They never restart but freeze after I click the restart button requiring me to force quit to stop my machine from going mad (fans spinning, high load averages). Support log is too big to attach to this (121MB).

Reply
0 Kudos
OJack
Contributor
Contributor

Having same issue as many others, but only with Win10. Win 7 Pro VM don't have any problems. Running MAC OS Sierra (latest) and Fusion Pro 8.5.3.

Unable to get to windows Vm after left running overnight. Have to force quit Fusion and restart to regain control. This has already damaged my VM hard disk once.

Any fix or workaround in sight? It looks like this problem been going on for several months.

Reply
0 Kudos
VK6565
Contributor
Contributor

This thread stopped here so wondering if there was a fix. I got on to VMware Fusion Version 8.5.6 (5234762)

Running on macOS Siera 10.12.4

The system has become extremely unstable and keeps crashing, not to mention the spinning wheel of doom which has become a frequent occurrence. I only run Win 7 Pro on the VM and it was perfectly fine with El Capitan and I suspect its got to do with the combo of VM and Siera.

Anyone still having this problem? Wondering if I should just do a clean install to see if that solves the problem.

Reply
0 Kudos
Mikero
Community Manager
Community Manager

The best way to get help here is to get in touch with support. Send an email to desktop-services@vmware.com or filing a ticket through your MyVMware portal is the way to do that.

The community can help aplenty, but our support team can get issues like these reported to our development team (who mostly do not check these forums).

So, they can help get it fixed for you, and get a bug filed so we don't have this happen again.

For your case, VK6565, I would definitely look at creating a fresh VM and see if the issue persists. If it does, it's our bug. If it does not, there's something wonky in your other VM.

-
Michael Roy - Product Marketing Engineer: VCF
Reply
0 Kudos
pwkoenig
Contributor
Contributor

I've been having this issue since updating to Sierra (10.12.4) for my Windows 7 pro VM running on Fusion (8.5.6) on startup of VM crashes macOS - however I think I just found a work around - I have disabled Accellerated 3D Graphics for this VM -- fingers crossed - VM is up and hasn't crashed yet which was crashing regularly .

This was based on reviewing VM Fusion blog posts.  specifically macOS Sierra and VMware Fusion 8 - VMware Fusion Blog - VMware Blogs

Come on VMWare - get it together and find the issue and provide a resolution! - nothing is "wonky" with our VMs - as this is not a single issue with a single VM - which can easily be determined by the number of responses in this thread.

Reply
0 Kudos
javarithms
Contributor
Contributor

I've been experiencing the same issue as the rest of you. Fortunately, my VMware fusion finally crashed and it generated a crash report (zip file). I opened the VMware.log file, inside the crash report, and looked for any clues of what might have caused the crash. I noticed the panic signals were coming from the | svga | driver. This pointed to the graphic driver being responsible for this whole mess!! Just like user pwkoenig, I disabled the Accelerated 3D Graphics on my VM and so far the it has been behaving.

I suggest if you have a crash report open the vmware.log file and look for the keyword SIGNAL and see what driver/hardware/library is potentially causing it. Here is the pertinent part of my crash report in case anybody wants to see how it looks.

2017-04-20T11:31:11-08:00[+352.100]| svga| W115: Caught signal 6 -- tid 41735 (addr 7FFFA2086D42)

2017-04-20T11:31:11-08:00[+352.106]| svga| I125: SIGNAL: rip 0x7fffa2086d42 rsp 0x7000040fcb88 rbp 0x7000040fcbb0

2017-04-20T11:31:11-08:00[+352.106]| svga| I125: SIGNAL: rax 0x0 rbx 0x6 rcx 0x7000040fcb88 rdx 0x0 rsi 0x6 rdi 0xa307

2017-04-20T11:31:11-08:00[+352.106]| svga| I125:         r8 0x0 r9 0x7fffa1fd7a50 r10 0x8000000 r11 0x206 r12 0xb2f5 r13 0x7ff9bc8c97f0 r14 0x7000040fd000 r15 0x7ff9bc8be800

2017-04-20T11:31:11-08:00[+352.106]| svga| I125: SIGNAL: stack 7000040FCB88 : 0x00007fffa21745bf 0x00007000040fcbd0

2017-04-20T11:31:11-08:00[+352.106]| svga| I125: SIGNAL: stack 7000040FCB98 : 0x0000a3070000b2f5 0x00007000040fcbd0

2017-04-20T11:31:11-08:00[+352.106]| svga| I125: SIGNAL: stack 7000040FCBA8 : 0x0000000000000813 0x00007000040fcbe0

2017-04-20T11:31:11-08:00[+352.106]| svga| I125: SIGNAL: stack 7000040FCBB8 : 0x00007fffa1fec420 0xffffffff040fcb00

2017-04-20T11:31:11-08:00[+352.106]| svga| I125: SIGNAL: stack 7000040FCBC8 : 0x00007ff9bc8c97f0 0x1887e7baffffffdf

2017-04-20T11:31:11-08:00[+352.106]| svga| I125: SIGNAL: stack 7000040FCBD8 : 0x0000000068000000 0x00007000040fcc90

2017-04-20T11:31:11-08:00[+352.106]| svga| I125: SIGNAL: stack 7000040FCBE8 : 0x00007fff9a4b2fbf 0x7363696870617247

2017-04-20T11:31:11-08:00[+352.106]| svga| I125: SIGNAL: stack 7000040FCBF8 : 0x7261776472616820 0x6e756f636e652065

2017-04-20T11:31:11-08:00[+352.106]| svga| I125: Backtrace:

2017-04-20T11:31:11-08:00[+352.106]| svga| I125: Backtrace[0] 00007000040fc560 rip=0000000103ce1590 rbx=00007000040fc568 rbp=00007000040fc5a0 r12=00000001044e7478 r13=00007000040fca68 r14=00007000040fc554 r15=0000000103ce1140

2017-04-20T11:31:11-08:00[+352.106]| svga| I125: Backtrace[1] 00007000040fc5b0 rip=0000000103fce86c rbx=00007000040fcb88 rbp=00007000040fc630 r12=00000001044e7478 r13=00007000040fca68 r14=00000000000001f6 r15=0000000000000006

2017-04-20T11:31:11-08:00[+352.107]| svga| I125: Backtrace[2] 00007000040fc640 rip=00007fffa2167b3a rbx=00007000040fcad0 rbp=00007000040fc640 r12=000000000000b2f5 r13=00007ff9bc8c97f0 r14=00007000040fd000 r15=00007ff9bc8be800

2017-04-20T11:31:11-08:00[+352.107]| svga| I125: SymBacktrace[0] 00007000040fc560 rip=0000000103ce15b7 in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 0000000103870000

2017-04-20T11:31:11-08:00[+352.107]| svga| I125: SymBacktrace[1] 00007000040fc5b0 rip=0000000103fce86c in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 0000000103870000

2017-04-20T11:31:11-08:00[+352.108]| svga| I125: SymBacktrace[2] 00007000040fc640 rip=00007fffa2167b3a in function _sigtramp in object /usr/lib/system/libsystem_platform.dylib loaded at 00007fffa2165000

2017-04-20T11:31:11-08:00[+352.108]| svga| E105: PANIC: Unexpected signal: 6.

2017-04-20T11:31:11-08:00[+352.108]| svga| W115:

2017-04-20T11:31:11-08:00[+352.108]| svga| W115+ The core dump limit is set to ZERO; no core dump should be expected

2017-04-20T11:37:03.753-08:00| mouse| W115: Panic in progress... ungrabbing

2017-04-20T11:37:03.753-08:00| mouse| I125: MKS: Release starting (panic).

2017-04-20T11:37:03.754-08:00| mouse| I125: MKS: Release finished (panic).

2017-04-20T11:37:03-08:00[+0.022]| svga| W115: Child process 6060 failed to dump core (status 0x6).

2017-04-20T11:37:03-08:00[+0.023]| svga| W115: Writing monitor corefile "/Users/javarithms/VMware/Windows 7 x64/vmmcores.gz"

2017-04-20T11:37:03-08:00[+0.039]| svga| W115: Dumping core for vcpu-0

2017-04-20T11:37:03-08:00[+0.039]| svga| I125: Beginning monitor coredump

2017-04-20T11:37:03-08:00[+0.390]| svga| I125: End monitor coredump

2017-04-20T11:37:03-08:00[+0.390]| svga| W115: Dumping core for vcpu-1

2017-04-20T11:37:03-08:00[+0.390]| svga| I125: Beginning monitor coredump

2017-04-20T11:37:03-08:00[+0.728]| svga| I125: End monitor coredump

2017-04-20T11:37:03-08:00[+0.728]| svga| W115: Dumping core for vcpu-2

2017-04-20T11:37:03-08:00[+0.728]| svga| I125: Beginning monitor coredump

2017-04-20T11:37:03-08:00[+1.056]| svga| I125: End monitor coredump

2017-04-20T11:37:03-08:00[+1.056]| svga| W115: Dumping core for vcpu-3

2017-04-20T11:37:03-08:00[+1.056]| svga| I125: Beginning monitor coredump

2017-04-20T11:37:03-08:00[+1.392]| svga| I125: End monitor coredump

2017-04-20T11:37:03-08:00[+2.851]| svga| I125: Coredump encountered overflow 5174:5174 (1126 duplicates)

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: Backtrace:

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: Backtrace[0] 00007000040fc070 rip=0000000103ce1590 rbx=00007000040fc078 rbp=00007000040fc0b0 r12=00000001044e7478 r13=00007000040fca68 r14=00007000040fc064 r15=0000000103ce1140

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: Backtrace[1] 00007000040fc0c0 rip=00000001038b1094 rbx=0000000000000001 rbp=00007000040fc5a0 r12=00000001044e7478 r13=00007000040fca68 r14=00000001046ca2c0 r15=0000000000000006

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: Backtrace[2] 00007000040fc5b0 rip=0000000103fce980 rbx=00007000040fcb88 rbp=00007000040fc630 r12=00000001044e7478 r13=00007000040fca68 r14=00000000000001f6 r15=0000000000000006

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: Backtrace[3] 00007000040fc640 rip=00007fffa2167b3a rbx=00007000040fcad0 rbp=00007000040fc640 r12=000000000000b2f5 r13=00007ff9bc8c97f0 r14=00007000040fd000 r15=00007ff9bc8be800

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: SymBacktrace[0] 00007000040fc070 rip=0000000103ce15b7 in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 0000000103870000

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: SymBacktrace[1] 00007000040fc0c0 rip=00000001038b1094 in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 0000000103870000

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: SymBacktrace[2] 00007000040fc5b0 rip=0000000103fce980 in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 0000000103870000

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: SymBacktrace[3] 00007000040fc640 rip=00007fffa2167b3a in function _sigtramp in object /usr/lib/system/libsystem_platform.dylib loaded at 00007fffa2165000

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: Msg_Post: Error

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: [msg.log.error.unrecoverable] VMware Fusion unrecoverable error: (svga)

2017-04-20T11:37:03-08:00[+3.602]| svga| I125+ Unexpected signal: 6.

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: [msg.panic.haveLog] A log file is available in "/Users/javarithms/VMware/Windows 7 x64/vmware.log". 

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: [msg.panic.requestSupport.withoutLog] You can request support. 

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: [msg.panic.requestSupport.vmSupport.apple.menu]

2017-04-20T11:37:03-08:00[+3.602]| svga| I125+ To collect data to submit to VMware support, choose "Collect Support Information" from the "Help" menu.

2017-04-20T11:37:03-08:00[+3.602]| svga| I125+ You can also run "VMware Fusion Problem Reporter.tool" inside the VMware Fusion application bundle directly.

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: [msg.panic.response] We will respond on the basis of your support entitlement.

2017-04-20T11:37:03-08:00[+3.602]| svga| I125: ----------------------------------------

2017-04-20T11:37:03-08:00[+20.310]| svga| I125: Exiting

Reply
0 Kudos
killcreak
Contributor
Contributor

macOS Sierra 10.12.4 host + Fusion 8.5.6 + Windows 10 guest - guest hangs frequently for 5-10 seconds freezing the host as well. Frequent crashes too. Looks related to copy & paste inside guest (even selecting text inside guest). None of the "disable this or that" solutions worked.

It's so bad that I am completely abandoning Fusion for the moment.

Reply
0 Kudos
VK6565
Contributor
Contributor

I tried to recreate the VM on Siera using Fusion 8.5.6 (5234762) and the issues continued to persist rendering the system unusable (Unable to find valid peer process ....)

I tried to reinstall Siera + Fusion 8.5.6 (5234762) and saw no improvement at all (built from scratch) - same issues

Downgraded to El Capitan ( 10.11.6) and installed Fusion 8.5.6 (5234762) - it seems to be holding up just fine with the exception of the typically high energy impact. Lets see if it continues to hold up for a couple of days at minimum. Being more concerned on getting this running, did not attempt to debug much but will have to try upgrading to Siera next week and see if the issues reoccur.

Reply
0 Kudos
Mikero
Community Manager
Community Manager

Hi there,

Have you filed a ticket with support?

They're our best resource for getting a fix and getting bugs triaged to our developers, and we're very interested in making sure you're running ok and that our software performs as users expect.

Drop us a note and we can work to get you sorted or file a bug or +1 an existing bug with our development team.

Thanks

-
Michael Roy - Product Marketing Engineer: VCF
Reply
0 Kudos
stefanhaupt
Contributor
Contributor

My understanding from other comments in the thread was that this was escalated to developers.

I currently manage and await either 10.12.5 or 8.5.7… ;->

I would very much like to help but currently I am unable as I do not have much time to spare.

But thanks for the update!

Reply
0 Kudos
beccoblu
Contributor
Contributor

it persists. just tested. fresh installed vm, ok for 24 hours, then it's again the same mess. vmware guys, this is becoming ridiculous.

Reply
0 Kudos
beccoblu
Contributor
Contributor

ok. I got some support from VMware team.

and so far things seem to go better. aka: in last 60 minutes I had no crash (in past few hours I could not go 10 minutes without one or two app faults).

the advice I received was:

- disable graphic acceleration (ok, we talked about it already in this thread)

- move work files on local drive. I was working directly on vmware shared folder (a mac os folder synced via dropbox). I copied it onto desktop and... whoa, something seems to have changed

i'll keep in touch if there is some news...

Reply
0 Kudos
mjlongo
Contributor
Contributor

I joined to respond to this thread in particular.  I am running Sierra 10.12.4 and Vmware Fusion 8.5.6 (5234762).  I have turned off 3D Acceleration per the previous suggestions.  My VM is Windows 7 x64 running on my local hard drive.  Mine starts up and runs on a second monitor and is set to fit to that monitor screen size (full screen). I've tried running non-full screen to no avail.  I have "Pass power status to VM" checked.  I have the power management within the Windows 7 machine to be completely off. i.e.:  "Turn display off" = never and "Put computer to sleep" = never.  On El Capitan, my Vmware never once crashed and always worked perfectly fine.  Once I upgraded to Sierra, the VM will crash with the never-ending pinwheel every morning that I come back into work. When upgrading to Sierra, I made no changes to VMware Fusion at all.  The rest of the mac will run but as soon as I hover over my VM, pinwheel of death!

I tried all of the Sierra updates and all of the VMware updates arriving at the versions I am running now.  I've tried the various settings that have been offered within this thread to no avail.   Once in a crash state, checking Activity Monitor shows that VMWare Fusion has stopped responding.  Attempting to kill the process in Activity Monitor always fails.  So, I've tried to kill the VMWare process within Terminal and that does indeed stop Vmware Fusion.  But, if Vmware Fusion is started up again, the exact same pinwheel issue comes back and typically will cause my mac to hang in other areas.  Another avenue I went down was to completely power off the Windows 7 VM, then completely exit VMWare Fusion.  Completely exit all running apps on the Mac leaving the mac in a very "clean" state and then go home for the night.  The next morning, I startup VMware Fusion again, relaunch the Windows 7 VM and the same pinwheel issue will occur.   So it seems to be an issue with extended sleep.

The only thing that works once I've hit a crashed VMware Fusion is hard powering off my MAC (via the power button) and allowing it to startup again.  (Just finished that process right before joining and posting here!) Once I do that, the system runs perfectly fine all day long.  Even works fine if I hit the Ctrl-Option-Eject and lock the mac for awhile say over lunchtime or something like that.  Sad fact is, this has become my every-day routine since moving to Sierra.  I was forced to move to Sierra after some issues with Safari as well as needing to be on higher levels of work-related apps so moving back to El Capitan is really not my desired solution but may be my only one of this issue with VMware Fusion continues. 

Reply
0 Kudos
rgdjong
Contributor
Contributor

Is there a fix yet? Already tried disabling shared folders and energy saving options. Any more options that I can try? Better to have a real fix anyway as this is very annoying.

I am running Fusion 8.5.8 on Macbook Pro Touch with macOS 10.12.8. System hangs at irregular intervals and mostly returns back to normal operation. Every once in a while it says that is has encountered an error and needs to restart my Windows 2012 VM or it just entirely hangs my Macbook which then gets restarted.

Reply
0 Kudos
TECH198
Hot Shot
Hot Shot

Well solution then seems never let Sierra sleep when fusion runs..

Reply
0 Kudos
rgdjong
Contributor
Contributor

Contacted VMware Support and they gave me a solution. Have not had any problems after this. Just add below line to the .vmx file for any VM that you are experiencing these kind of problems with.

mks.enableGLBasicRenderer = "FALSE"

They promised me that this issue will be fixed in the next release of Fusion.

charlus
Contributor
Contributor

I've been experiencing the same issue on my Fusion 8.5.8 (and also on previous versions). This was happening from time to time but today it happened at least 5 times in a row after a few minutes of use of the Windows XP VM on my mac running Sierra 10.12.5. Everytime leading to a total freeze of both the host & guest systems and needing a hard reboot by holding the power button.

This is really unacceptable since it's been happening for a while now.

Thanks for sharing your tip, I've added the line to my .vmx file and now I'm crossing fingers ...

tm8747a
Contributor
Contributor

I tried mks.enableGLBasicRenderer = "FALSE" and that didn't seem to fix things for me. I then disabled the Accelerate 3D Graphics option and that seems to have stopped the crashing for me.

Reply
0 Kudos
hurbis
Contributor
Contributor

Unsable!!! Crashes all the time!!! I have been worried about it. Worried to lost some work that I spent a day developing.

The VMWare Fusion never was stable. It`s a shame!

Reply
0 Kudos
WallyTgoat
Contributor
Contributor

tm8747a

When you say disabled "Accelerate 3D Graphics option" are you referring to "mks.enable3d = “FALSE”? 

I entered this and when the vm starts I get an error starting "FALSE" is not a valid option.

thanks in advance.

Reply
0 Kudos