I also have 5.0.2 crashing with ubuntu looks like a crash in vmware tools something to do with unity. If I start ubuntu in restricted mode or a confined syession of say software update only then I have no issue.
I have osx 10.8.2 on macbook pro with retina display running latest Ubuntu 12 64 bit vmware runnning vmware fusion 5 format VM.
2012-11-11T07:01:59.201Z| vcpu-1| I120: GuestRpc: Channel 1, guest application toolbox-dnd.
2012-11-11T07:01:59.249Z| vcpu-1| I120: TOOLS call to unity.launchmenu.open failed.
2012-11-11T07:01:59.249Z| vcpu-1| I120: TOOLS call to unity.launchmenu.open failed.
2012-11-11T07:01:59Z[+0.885]| svga| W110: Caught signal 11 -- tid 4560109568
2012-11-11T07:01:59Z[+0.886]| svga| I120: SIGNAL: eip 0x7fff90da7a50 esp 0x10fcdb890 ebp 0x10fcdb890
2012-11-11T07:01:59Z[+0.886]| svga| I120: SIGNAL: eax 0x193d880 ebx 0x1028f1a00 ecx 0xfffffffffffe2880 edx 0x0 esi 0x1242d5780 edi 0x125c13000
2012-11-11T07:01:59Z[+0.886]| svga| I120: r8 0x10fcdb700 r9 0x0 r10 0x125493000 r11 0x125493000 r12 0x780000 r13 0x10e500000 r14 0x125493000 r15 0x10c09e9b8
2012-11-11T07:01:59Z[+0.886]| svga| I120: SIGNAL: stack 10FCDB890 : 0x0fcdb920 0x00000001 0x000cd29f 0x00000002
2012-11-11T07:01:59Z[+0.886]| svga| I120: SIGNAL: stack 10FCDB8A0 : 0x00762000 0x00000000 0x0396a818 0x00000001
2012-11-11T07:01:59Z[+0.886]| svga| I120: SIGNAL: stack 10FCDB8B0 : 0x00000000 0x00000000 0x02856800 0x00000001
2012-11-11T07:01:59Z[+0.886]| svga| I120: SIGNAL: stack 10FCDB8C0 : 0x23b55780 0x00000001 0x028f1a00 0x00000001
2012-11-11T07:01:59Z[+0.886]| svga| I120: SIGNAL: stack 10FCDB8D0 : 0x00780000 0x00000000 0x000b0266 0x00000002
2012-11-11T07:01:59Z[+0.886]| svga| I120: SIGNAL: stack 10FCDB8E0 : 0x00000000 0x00000000 0x060f1e00 0x00000001
2012-11-11T07:01:59Z[+0.886]| svga| I120: SIGNAL: stack 10FCDB8F0 : 0x00000000 0x00000000 0x0396b9b8 0x00000001
2012-11-11T07:01:59Z[+0.886]| svga| I120: SIGNAL: stack 10FCDB900 : 0x0d600000 0x00000001 0x00000008 0x00000000
2012-11-11T07:01:59Z[+0.886]| svga| I120: Backtrace:
2012-11-11T07:01:59Z[+0.886]| svga| I120: Backtrace 000000010fcdb290 rip=0000000100512bed rbx=0000000000000000 rbp=000000010fcdb2b0 r12=00000001005129c0 r13=000000010fcdb700 r14=000000010fcdb7d8 r15=000000000000000b
2012-11-11T07:01:59Z[+0.886]| svga| I120: Backtrace 000000010fcdb2c0 rip=00000001001b7dce rbx=0000000000000080 rbp=000000010fcdb330 r12=000000000000000b r13=000000010fcdb700 r14=000000010fcdb7d8 r15=000000000000000b
2012-11-11T07:01:59Z[+0.886]| svga| I120: Backtrace 000000010fcdb340 rip=00007fff90da88ea rbx=000000010fcdb7d8 rbp=000000010fcdb340 r12=0000000000780000 r13=000000010e500000 r14=0000000125493000 r15=000000010c09e9b8
2012-11-11T07:01:59Z[+0.886]| svga| I120: SymBacktrace 000000010fcdb290 rip=0000000100512bed in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 0000000100000000
2012-11-11T07:01:59Z[+0.886]| svga| I120: SymBacktrace 000000010fcdb2c0 rip=00000001001b7dce in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx loaded at 0000000100000000
2012-11-11T07:01:59Z[+0.886]| svga| I120: SymBacktrace 000000010fcdb340 rip=00007fff90da88ea in function _sigtramp in object /usr/lib/system/libsystem_c.dylib loaded at 00007fff90da6000
2012-11-11T07:01:59Z[+0.886]| svga| I120: Unexpected signal: 11.
2012-11-11T07:01:59Z[+0.886]| svga| W110:
So looks like a toos backward compatability issue. Any ideas on how to resolve ?
In the meantime, please try this: With your VM powered off, go into the Virtual Machine > Settings, then choose Display, and turn off the Accelerate 3D Graphics option. Then close the Settings window and try to power on your VM.
Hi carlonzo, and welcome to the VMware Communities!
Your crash is the same as zzzebra's and several others we've seen in the last day or so, and the same workaround should get you going again: With your VM powered off, go into the Virtual Machine > Settings, then choose Display, and turn off the Accelerate 3D Graphics option. Then close the Settings window and try to power on your VM.
We'll continue to investigate through our internal bug report, and hopefully we'll soon figure out how to fix this problem.
Can you provide more information on the "DOS environment" that you saw? If it happens again, it'd be great if you could take a screen shot or photo, or record anything that it has on the screen.
It looks like you have not yet installed the "MacBook Air and MacBook Pro Update 2.0" offered through Apple Software Update. Please avoid that update for now, as it is known to cause problems with Fusion 5.0.1 and Fusion 5.0.2. If you are offered the update, you should decline it.
I have no idea about the blank screen issue. It's a bizarre looking screen shot, for sure...
I also am experiencing issues after upgrading from the previous, stable Fusion 5.01 to 5.02. I read the previous articles and disabled the 3D Graphics accelerator and Windows 7 (64-bit Professional) no longer crashes, however, I now receive the error message upon a reboot indicating that the Windows Group Policy Client service did not start. While reviewing Windows services, all options for this particular servce are grayed out and I have spent the last 2 hours scoruing various forums and the Internet in general on how to resolve this issue.
Not how I planned to spend 3 hours this AM resolving issues with a minor maintenance release.
If anyone has any ideas on how I can resolve the Windows Group Policy Client service, they would truly be appreciated.
As stated above, the Fusion 5.01 release was very stable and I regret upgrading to 5.02. I would suggest that others hold off until these issues have been resolved.
Hi millekj, and welcome to the VMware Communities!
I know that this has been a painful experience, and I regret that you've encountered so much trouble.
Just to correct the record: We believe the trigger for this crash to be a Mac OS update, MacBook Air and MacBook Pro Update 2.0, which was released on Apple Software Update at about the same time as Fusion 5.0.2 became available, and which seems to be causing stability problems for all Fusion 5.x on recent MBA and MBP systems when 3D acceleration is in use. You probably would have encountered the same crash even if you had not updated Fusion.
We'll continue to investigate the problem to determine whether it is a defect in Fusion or a defect in the updated graphics driver from Apple.
It's very unfortunate for us that the timing of the Apple Software Update release is causing so many people to blame this failure on the Fusion 5.0.2 update.
If my description here doesn't match your situation, please collect a support information bundle and attach it to your reply, and I'll take a look.
It is not safe to assume that there is only one problem being discussed in this thread.
From the sum of available evidence, the logical conclusion is that there are two separate (and likely unrelated) problems being discussed in this thread, and that the problem you're seeing is unrelated to that encountered by most/all people who've jumped onto this thread since. It makes things mighty confusing! So, I ask you to kindly ignore the advice I am giving to many of the other posters on this thread, because it does not apply to your problem; Similarly, when I tell others that the software update is the trigger, that does not apply to your problem.
Can you provide more information on the times at which you are seeing the "DOS environment"? Does it happen as Windows is first booting up, or some short time after Windows is running, or during normal use of the VM, or something else? Is it still happening at all? How long did you leave it at the DOS screen before resetting or powering off the VM? 30 seconds? A few minutes? I'd appreciate any information you have which might help understand what's happening by correlating it to what's going on in the VM at the time. I think it is normal to see that screen for a few seconds after a Fusion version upgrade, when the VMware SVGA driver is being upgraded inside the VM, but it should not last more than a few seconds and then the normal Windows desktop should reappear.
Dariusd - You keep blaming the Apple Software update for VMWare's bugs and that's just not right. I had absolutely no problems wihen I was running 5.01 and Apple's updates. It was only after I upgraded VMWare Fusion to 5.02 that I had issues. This is not something I expected for a minor maintenance release and I repeat, Apple's updates worked fine with VMWare Fusion before the upate to 5.02.
Did you not see where he said "We'll continue to investigate the problem to determine whether it is a defect in Fusion or a defect in the updated graphics driver from Apple." in Re: 5.0.2 crashing? As I told you in the other thread I don't take his comments in this thread (or the other) to be that of one explicitly and specifically blaming Apple for this!
I have the same problem on my Ubuntu 12.10 guest on my rMBP 10.8.2 with Fusion 5.0.2.
From my experience, turning off 3D acceleration at least gets the Ubuntu booting and stablizing a bit.
But it still generates system errors within Ubuntu every once in a while like complaining about printer and stuff.
I have to turn off "Share mac printer with linux", plus completely "Remove USB Controller" to stop the system errors within Ubuntu.
So you folks may have to look into more than just the 3D acceleration under the Display setting, something on the USB side maybe causing some issues.
Note the Apple Update says "This update includes graphics performance and reliability enhancements and improves compatibility with some USB devices.", meaning it's messing with the USB stuff too.
Hopefully, you guys will come out with a fix soon.
The problem is that a lot of the same issues are occurring on older model Macs like my 2008 MacBook Pro that did not receive and are not eligible for the Apple MacBook 2.0 update. Turning off 3D allows it to at least boot up as you describe and then I get intermittent messages again as you describe. Does anyone know what VMWare changed. Was it even disclosed ? It sure seems like they changed quite a bit more then you'd expect for a small maintenance release. I'm bothered by this because it really doesn't seem like VMWare is adequately testing and they only seem to be entertaining the idea of incompatibility with that one specific Apple update even though the same issues are occurring on Macs that did not receive the Apple update. There are definitely serious gaps in their testing. My Parallels Mac is not having any issues...
Sent from my iPad
Hi ACWL, and welcome to the VMware Communities!
Thanks for the detailed report, and sorry for the trouble you're having. We can look into this. Could you possibly share a screenshot of the exact printer/USB error messages you're seeing inside the guest, or attach some/all of the relevant logfile from within the guest? That would help us know for sure if we've reproduced the same problematic system error(s) that you're seeing. If the errors are all gone and you don't want to mess with your configuration, that's fine, just say so, and we'll work with the good information you've already provided.