Restoring Virtual Machine State

[p3tavmware]

My Windows XP Professional Virtual Machine running on nmy MacBook Pro is stuck on Restoring Virtual Machine State... It goes about 25% nice and fast then hangs... any ideas I woudl hate to rebuild everything I have on there.

Thanks

Peter

[rcardona2k]

Was this machine migrated from another environment? Was it migrated in a saved state? What kind of machine did it come from?

If no to those questions above, have you tried to reboot your machine before restoring?

Look in the vmware.log file in the VM folder and post the last twenty or so lines here when it gets stuck.

[p3tavmware]

Nope not migrated. Not migrated in a saved state... and have tried rebooting before restoring

Here are the last twenty lines form the log if that helps... it also generated a Windows XP Professional.vmx.WRITELOCK whatever that is...

Thanks fr any input you might have:

Jan 05 06:03:13.781: vmx| \----

---

Jan 05 06:03:13.781: vmx| Opened paging file /Users/peta/vmware/Windows XP Professional/Windows XP Professional.vmem

Jan 05 06:03:13.781: vmx| Lazy Restore with prefetch of 128 MB

Jan 05 06:03:13.781: MMPageWalker| MMC: Entering MM LazySave Loop

Jan 05 06:03:13.918: vmx| XXXMACOS: Do we need VMMon_MarkLockedVARangeClean?

Jan 05 06:03:38.948: vmx| Caught signal 10 -- tid -1610559552

Jan 05 06:03:38.948: vmx| SIGNAL: eip 0x5da20 esp 0xbffff2b0 ebp 0xbffff378

Jan 05 06:03:38.948: vmx| SIGNAL: eax 0x0 ebx 0x5d718 ecx 0x18 edx 0x1728d000 esi 0x20 edi 0x0

Jan 05 06:03:38.948: vmx| SIGNAL: stack 0xbffff2b0 : 0x01bd3380 0x00001f60 0x00000020 0xbffff3f4

Jan 05 06:03:38.948: vmx| SIGNAL: stack 0xbffff2c0 : 0x00000000 0x003f5c24 0x00000018 0x0007f4fb

Jan 05 06:03:38.948: vmx| SIGNAL: stack 0xbffff2d0 : 0x0000000a 0x00000000 0x00000000 0x03a245fc

Jan 05 06:03:38.948: vmx| SIGNAL: stack 0xbffff2e0 : 0x00007d80 0x0007d8fb 0xbffff338 0x0007d90a

Jan 05 06:03:38.948: vmx| SIGNAL: stack 0xbffff2f0 : 0x00000001 0x00000000 0xbffff3ec 0xbffff3f4

Jan 05 06:03:38.948: vmx| SIGNAL: stack 0xbffff300 : 0x0000000a 0x01bd3380 0x00001f60 0x0005fc49

Jan 05 06:03:38.948: vmx| SIGNAL: stack 0xbffff310 : 0x00000000 0x00ffffff 0x01c0d488 0x01c0d450

Jan 05 06:03:38.948: vmx| SIGNAL: stack 0xbffff320 : 0x00000018 0x00001ec0 0x00000000 0x0202df8c

Jan 05 06:03:38.948: vmx| Backtrace:

Jan 05 06:03:38.948: vmx| Backtrace[0] 0xbfffef38 eip 0x25fa57

Jan 05 06:03:38.948: vmx| Backtrace[1] 0xbfffefa8 eip 0x2b08a7

Jan 05 06:03:38.948: vmx| Backtrace[2] 0xbfffefc8 eip 0x9011110c

Jan 05 06:03:38.948: vmx| Backtrace[3] 0xbffff378 eip 0xffffffff

Jan 05 06:03:38.948: vmx| Backtrace[4] 0xbffff418 eip 0x05aa12

Jan 05 06:03:38.948: vmx| Backtrace[5] 0xbffff458 eip 0x05b216

Jan 05 06:03:38.948: vmx| Backtrace[6] 0xbffff498 eip 0x05b51c

Jan 05 06:03:38.948: vmx| Backtrace[7] 0xbffff4d8 eip 0x0590d0

Jan 05 06:03:38.948: vmx| Backtrace[8] 0xbffff898 eip 0x045aeb

Jan 05 06:03:38.948: vmx| Backtrace[9] 0xbffff8d8 eip 0x2bce58

Jan 05 06:03:38.948: vmx| Backtrace\[10] 0xbffff918 eip 0x011c12

Jan 05 06:03:38.948: vmx| Backtrace\[11] 0xbffff978 eip 0x012504

Jan 05 06:03:38.949: vmx| Backtrace\[12] 0xbffffa28 eip 0x00591a

Jan 05 06:03:38.949: vmx| Backtrace\[13] 0xbffffb28 eip 0x005f0a

Jan 05 06:03:38.949: vmx| Backtrace\[14] 0xbffffb68 eip 0x002eca

Jan 05 06:03:38.949: vmx| Backtrace\[15] 0xbffffb80 eip 0x002de5

Jan 05 06:03:38.949: vmx| Backtrace\[16] 00000000 eip 0x000006

Jan 05 06:03:38.949: vmx| Unexpected signal: 10.

Jan 05 06:03:38.949: vmx| Backtrace:

Jan 05 06:03:38.949: vmx| Backtrace[0] 0xbfffeb08 eip 0x25fa57

Jan 05 06:03:38.949: vmx| Backtrace[1] 0xbfffef38 eip 0x010fc0

Jan 05 06:03:38.949: vmx| Backtrace[2] 0xbfffefa8 eip 0x2b08e0

Jan 05 06:03:38.949: vmx| Backtrace[3] 0xbfffefc8 eip 0x9011110c

Jan 05 06:03:38.949: vmx| Backtrace[4] 0xbffff378 eip 0xffffffff

Jan 05 06:03:38.949: vmx| Backtrace[5] 0xbffff418 eip 0x05aa12

Jan 05 06:03:38.949: vmx| Backtrace[6] 0xbffff458 eip 0x05b216

Jan 05 06:03:38.949: vmx| Backtrace[7] 0xbffff498 eip 0x05b51c

Jan 05 06:03:38.949: vmx| Backtrace[8] 0xbffff4d8 eip 0x0590d0

Jan 05 06:03:38.949: vmx| Backtrace[9] 0xbffff898 eip 0x045aeb

Jan 05 06:03:38.949: vmx| Backtrace\[10] 0xbffff8d8 eip 0x2bce58

Jan 05 06:03:38.949: vmx| Backtrace\[11] 0xbffff918 eip 0x011c12

Jan 05 06:03:38.949: vmx| Backtrace\[12] 0xbffff978 eip 0x012504

Jan 05 06:03:38.949: vmx| Backtrace\[13] 0xbffffa28 eip 0x00591a

Jan 05 06:03:38.949: vmx| Backtrace\[14] 0xbffffb28 eip 0x005f0a

Jan 05 06:03:38.949: vmx| Backtrace\[15] 0xbffffb68 eip 0x002eca

Jan 05 06:03:38.949: vmx| Backtrace\[16] 0xbffffb80 eip 0x002de5

Jan 05 06:03:38.949: vmx| Backtrace\[17] 00000000 eip 0x000006

Jan 05 06:03:38.951: vmx| Dumping core...

Jan 05 06:03:48.950: vmx| Waiting for child process 231 to dump core...

Jan 05 06:03:49.951: vmx| Waiting for child process 231 to dump core...

Jan 05 06:03:50.951: vmx| Waiting for child process 231 to dump core...

Jan 05 06:03:51.951: vmx| Msg_Post: Error

Jan 05 06:03:51.951: vmx| \[msg.log.error.unrecoverable] VMware Fusion unrecoverable error: (vmx)

Jan 05 06:03:51.951: vmx| Unexpected signal: 10.

Jan 05 06:03:51.951: vmx| \[msg.panic.haveLog] A log file is available in "/Users/peta/vmware/Windows XP Professional/vmware.log". \[msg.panic.haveCore] A core file is available in "/cores/core.231". \[msg.panic.requestSupport.withLogAndCore] Please request support and include the contents of the log file and core file. \[msg.panic.requestSupport.linux]

Jan 05 06:03:51.951: vmx| To collect files to submit to VMware support, run vm-support.

Jan 05 06:03:51.951: vmx| \[msg.panic.response] We will respond on the basis of your support entitlement.

Jan 05 06:03:51.951: vmx| \----

---

Jan 05 06:03:51.957: vmx| MKS release: start, nesting 0

Jan 05 07:43:14.846: vmx| vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF

Jan 05 07:43:20.716: vmx| MKS release: end, nesting 1

[admin]

Please file an SR with that data -- there's a real bug there that needs looking at, and our support people will want the entire logfile and the corefile it mentions.

However, if you just want to be able to use that VM without rebuilding it (you'll keep the disk image, but lose any unsaved data, since this will forcibly power the VM off from its current suspended state), you can remove the .vmem and .vmss files. The next time you open it, it should boot up again.

[p3tavmware]

Thanks I did send via the proper channels the entire sr and log file so hopefully that will help them.

Just to see if I understand what you are saying... if I remove the .vmem amd .vmss files the windows machine will boot up at last state before the crash without any saved files...

That would be fine with me.

thanks

Peter

[admin]

Yup, that's right.

[p3tavmware]

how right you are... back to the way it was and just in time

A thousand thanks yous

Peter