VMware Communities
protondonor
Contributor
Contributor
‎07-22-2016 12:08 PM
Jump to solution

VMware Workstation 12 Player crashes to desktop loading Windows 10 VM after host crashed

I am running VMware Workstation 12 Player on Xubuntu 16.04. I have a VM with Windows 10 installed. My machine crashed recently (while the VM was powered on) and I wound up having to reinstall Xubuntu. Since then, VMware crashes to desktop when I try to load the VM. Full logs are attached. Here is an excerpt:

2016-07-22T11:36:11-07:00[+0.059]| mks| W115: Caught signal 4 -- tid 20708 (addr 7F5908E330C0)

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: rip 0x7f5908e330c0 rsp 0x7f5901d39d20 rbp 0x7f5901d39de0

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: rax 0x0 rbx 0x0 rcx 0x0 rdx 0x0 rsi 0x7f58f83086b0 rdi 0x10

2016-07-22T11:36:11-07:00[+0.059]| mks| I125:         r8 0x7 r9 0x10 r10 0x3 r11 0x0 r12 0x7f5901d39f70 r13 0x40 r14 0x7f58f8306300 r15 0x7f5901d39f00

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: stack 7F5901D39D20 : 0x4180000041800000 0x4180000041800000

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: stack 7F5901D39D30 : 0x4180000041800000 0x4180000041800000

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: stack 7F5901D39D40 : 0x4180000041800000 0x4180000041800000

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: stack 7F5901D39D50 : 0x4180000041800000 0x4180000041800000

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: stack 7F5901D39D60 : 0x0000000000000000 0x0000000000000000

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: stack 7F5901D39D70 : 0x0000006e0000005b 0x0000000000000004

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: stack 7F5901D39D80 : 0x0000000000000000 0x0000007c00000077

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: stack 7F5901D39D90 : 0x00007f58f8800e10 0x00007f58f876d398

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: Backtrace:

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: Backtrace[0] 00007f5901d39370 rip=000055fa719380ce rbx=000055fa71937ea0 rbp=0000000000000000 r12=00007f5901d3b600 r13=00007f5901d39da0 r14=00007f5901d39680 r15=000000000000000b

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: Backtrace[1] 00007f5901d393a0 rip=000055fa71bd3278 rbx=00007f5901d39da0 rbp=0000000000000004 r12=00007f5901d3b600 r13=00007f5901d39da0 r14=00007f5901d39680 r15=000000000000000b

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: Backtrace[2] 00007f5901d39630 rip=000055fa71bd35ad rbx=0000000000000004 rbp=0000000000000002 r12=00007f5901d3b660 r13=00007f5901d397b0 r14=00007f5901d39680 r15=000000000000000b

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: Backtrace[3] 00007f5901d39680 rip=00007f5908af23d0 rbx=0000000000000000 rbp=00007f5901d39de0 r12=00007f5901d39f70 r13=0000000000000040 r14=00007f58f8306300 r15=00007f5901d39f00

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: Backtrace[4] 00007f5901d39d20 rip=00007f5908e330c0 rbx=0000000000000000 rbp=00007f5901d39de0 r12=00007f5901d39f70 r13=0000000000000040 r14=00007f58f8306300 r15=00007f5901d39f00

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SymBacktrace[0] 00007f5901d39370 rip=000055fa719380ce in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 000055fa71428000

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SymBacktrace[1] 00007f5901d393a0 rip=000055fa71bd3278 in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 000055fa71428000

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SymBacktrace[2] 00007f5901d39630 rip=000055fa71bd35ad in function (null) in object /usr/lib/vmware/bin/vmware-vmx loaded at 000055fa71428000

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SymBacktrace[3] 00007f5901d39680 rip=00007f5908af23d0 in function (null) in object /lib/x86_64-linux-gnu/libpthread.so.0 loaded at 00007f5908ae1000

2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SymBacktrace[4] 00007f5901d39d20 rip=00007f5908e330c0

2016-07-22T11:36:11-07:00[+0.059]| mks| E105: PANIC: Unexpected signal: 4.

Is there a way to recover the VM, or at least the information on disk?

vmware.log.zip
1 Solution

Accepted Solutions
wila
Immortal
Immortal
‎07-28-2016 02:15 AM
Jump to solution

Hello,

Welcome at the VMware community forums.

When I looked at your attached log I noticed the lines above the backtrace:

2016-07-22T11:36:11.120-07:00| mks| I125: GLManager: Emulating point sprites with quads.


2016-07-22T11:36:11.120-07:00| mks| I125: GLManager: using core profile


2016-07-22T11:36:11.120-07:00| mks| I125: GLManager: maxVertAttrStride = 2048


2016-07-22T11:36:11.120-07:00| mks| I125: GLManager: Host supports 18 vertex texture units, 18 fragment texture units, 18 geometry texture units and 54 combined texture units.


2016-07-22T11:36:11-07:00[+0.059]| mks| W115: Caught signal 4 -- tid 20708 (addr 7F5908E330C0)


2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: rip 0x7f5908e330c0 rsp 0x7f5901d39d20 rbp 0x7f5901d39de0


2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: rax 0x0 rbx 0x0 rcx 0x0 rdx 0x0 rsi 0x7f58f83086b0 rdi 0x10

So it seems that the VM crashes while configuring the graphical backend.

Signal 4 is "illegal instruction"  (see signal(7) - Linux manual page )

The  first thing I would do is ... make a copy of the VM to another disk so that whatever happens in the future you can go back to this pristine copy.


Then I would try and see if you can boot the VM after disabling 3D support under display settings.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva

View solution in original post

2 Replies
wila
Immortal
Immortal
‎07-28-2016 02:15 AM
Jump to solution

Hello,

Welcome at the VMware community forums.

When I looked at your attached log I noticed the lines above the backtrace:

2016-07-22T11:36:11.120-07:00| mks| I125: GLManager: Emulating point sprites with quads.


2016-07-22T11:36:11.120-07:00| mks| I125: GLManager: using core profile


2016-07-22T11:36:11.120-07:00| mks| I125: GLManager: maxVertAttrStride = 2048


2016-07-22T11:36:11.120-07:00| mks| I125: GLManager: Host supports 18 vertex texture units, 18 fragment texture units, 18 geometry texture units and 54 combined texture units.


2016-07-22T11:36:11-07:00[+0.059]| mks| W115: Caught signal 4 -- tid 20708 (addr 7F5908E330C0)


2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: rip 0x7f5908e330c0 rsp 0x7f5901d39d20 rbp 0x7f5901d39de0


2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: rax 0x0 rbx 0x0 rcx 0x0 rdx 0x0 rsi 0x7f58f83086b0 rdi 0x10

So it seems that the VM crashes while configuring the graphical backend.

Signal 4 is "illegal instruction"  (see signal(7) - Linux manual page )

The  first thing I would do is ... make a copy of the VM to another disk so that whatever happens in the future you can go back to this pristine copy.


Then I would try and see if you can boot the VM after disabling 3D support under display settings.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
protondonor
Contributor
Contributor
‎07-31-2016 08:06 PM
Jump to solution

Thank you! It boots up properly now. I was able to re-enable 3D graphics support and now everything inside the VM runs just as well as it did previously. And of course, I now have a backup in case this happens again.