Unrecoverable error in 1.1.2 and 2.0

[flyby]

I had to skip over 1.1.1 because I was one of those getting a signal 10 error. I installed 1.1.2 when it came out and it was running fine for a while. Yesterday 1.1.2 stopped, returning an "unrecoverable error . . .". Went through various restarts, reinstalls, etc. and would get as far as the XP Welcome screen, up to actually being able to open a program before Fusion shutdown. It always shut down.

Since 2.0 was available I put it in, with the same results.

In the interest of full disclosure, I had just put in a second drive for Time Machine, format it, but never attached it to Time Machine. Time Machine stopped working too. Since TM and Fusion don't get along, I'm not sure if these issues are related.

Any thoughts would be appreciated.

[admin]

Yesterday 1.1.2 stopped, returning an "unrecoverable error . . ."

The ... is the really important part, we can't diagnose it without that information. Also, log files are good. .

[flyby]

Sorry for the omission, I thought it was a standard error message.

"Unrecoverable error (vcpu-0). Unexpected signal 10." Then it goes on about the log files and vm-support.tool, which did not load on my machine in either 1.1.2 or 2.0. Since I don't have another option. I'll dump a portion of the log here. If it is insufficient, there's more.

FWIW, Time Machine seems better after dismounting three volumes and rebooting. So, the VM-TM tie-in may not be an issue.

Thanks for looking at my problem.

May 23 06:33:49.899: vcpu-0| FILE: FileIO_ResetExcludedFromTimeMachine Couldn't set xattr on path : Permission denied.

May 23 06:33:49.937: vcpu-0| TOOLS INSTALL finished copying upgrader binary into guest. Starting Upgrader in guest.

May 23 06:33:50.049: vcpu-0| Guest: toolbox: Version: build-87978

May 23 06:33:50.049: vcpu-0| TOOLS unified loop capability requested by 'toolbox'; now sending options via TCLO

May 23 06:33:50.049: vcpu-0| TOOLS INSTALL completed Foundry upgrade.

May 23 06:33:50.158: vcpu-0| TOOLS INSTALL entering COPYING state.

May 23 06:33:50.535: vcpu-0| GuestRpc: Channel 2, guest application tools-upgrader.

May 23 06:33:50.535: vcpu-0| DISKUTIL: scsi0:0 : toolsVersion = 7363

May 23 06:33:50.542: vcpu-0| TOOLS Received upgrader capability parameters.

May 23 06:33:50.568: vcpu-0| TOOLS state change 3 returned status 1

May 23 06:33:52.933: vcpu-0| TOOLS INSTALL Sent upgrader.run -s to guest.

May 23 06:33:52.933: vcpu-0| TOOLS INSTALL entering INSTALLING state.

May 23 06:33:54.107: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 start feature 0

May 23 06:33:54.134: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 start feature 30

May 23 06:33:54.134: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 start feature 31

May 23 06:33:54.134: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 start feature 32

May 23 06:33:54.134: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 start feature 33

May 23 06:33:54.135: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 start feature 35

May 23 06:33:54.135: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 start feature 36

May 23 06:33:54.135: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 start feature 38

May 23 06:33:54.135: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 start feature 45

May 23 06:33:54.135: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 start feature 46

May 23 06:33:54.135: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 start feature 47

May 23 06:33:54.135: vcpu-0| CDROM: Emulate GET CONFIGURATION RT 0 start feature 259

May 23 06:33:57.281: vcpu-0| Caught signal 10 -- tid -1339920384

May 23 06:33:57.281: vcpu-0| SIGNAL: eip 0x73635 esp 0xb0226d10 ebp 0xb0226d68

May 23 06:33:57.281: vcpu-0| SIGNAL: eax 0x54e1c000 ebx 0x735e6 ecx 0x1038eb4 edx 0xb0226d40 esi 0x2c3c94c edi 0x35610

May 23 06:33:57.281: vcpu-0| SIGNAL: stack B0226D10 : 0x00000001 0xb0226d3c 0xffbff000 0x00000001

May 23 06:33:57.281: vcpu-0| SIGNAL: stack B0226D20 : 0xb0226d3c 0x0100001a 0x01000000 0xffffffff

May 23 06:33:57.281: vcpu-0| SIGNAL: stack B0226D30 : 0x00000000 0x00000000 0x00000000 0x00035610

May 23 06:33:57.281: vcpu-0| SIGNAL: stack B0226D40 : 0x54e1c000 0x00000001 0x01038eb4 0x00000001

May 23 06:33:57.281: vcpu-0| SIGNAL: stack B0226D50 : 0x0000001a 0x00000000 0xb0226d78 0x000738fd

May 23 06:33:57.281: vcpu-0| SIGNAL: stack B0226D60 : 0x00000000 0x02c3c930 0xb0226dd8 0x00073947

May 23 06:33:57.281: vcpu-0| SIGNAL: stack B0226D70 : 0x00100f2a 0x02c29f80 0xb0226d88 0x00100f4a

May 23 06:33:57.281: vcpu-0| SIGNAL: stack B0226D80 : 0x00000014 0x000a8b44 0xb0226dc8 0x0010c3e7

May 23 06:33:57.281: vcpu-0| Backtrace:

May 23 06:33:57.281: vcpu-0| Backtrace[0] 0xb02269a8 eip 0x2bab2f

May 23 06:33:57.281: vcpu-0| Backtrace[1] 0xb0226a08 eip 0x0ac374

May 23 06:33:57.281: vcpu-0| Backtrace[2] 0xb0226a28 eip 0x9697a5eb

May 23 06:33:57.281: vcpu-0| Backtrace[3] 0xb0226d68 eip 0xffffffff

May 23 06:33:57.281: vcpu-0| Backtrace[4] 0xb0226dd8 eip 0x073947

May 23 06:33:57.281: vcpu-0| Backtrace[5] 0xb0226e68 eip 0x10eea1

May 23 06:33:57.281: vcpu-0| Backtrace[6] 0xb0226ea8 eip 0x0fe9f6

May 23 06:33:57.281: vcpu-0| Backtrace[7] 0xb0226ee8 eip 0x11fa6b

May 23 06:33:57.281: vcpu-0| Backtrace[8] 0xb0226f08 eip 0x0fed3d

May 23 06:33:57.281: vcpu-0| Backtrace[9] 0xb0226f78 eip 0x0a98f7

May 23 06:33:57.281: vcpu-0| Backtrace[10] 0xb0226fc8 eip 0x9693ec55

May 23 06:33:57.281: vcpu-0| Backtrace[11] 0xb0226fec eip 0x9693eb12

May 23 06:33:57.281: vcpu-0| Backtrace[12] 00000000 eip 00000000

May 23 06:33:57.281: vcpu-0| Unexpected signal: 10.

May 23 06:33:57.281: vcpu-0| Core dump limit is 0 KB.

May 23 06:34:01.301: vcpu-0| Child process 502 failed to dump core (status 0x6).

May 23 06:34:01.301: vcpu-0| Backtrace:

May 23 06:34:01.301: vcpu-0| Backtrace[0] 0xb0226578 eip 0x2bab2f

May 23 06:34:01.301: vcpu-0| Backtrace[1] 0xb02269a8 eip 0x0162f6

May 23 06:34:01.301: vcpu-0| Backtrace[2] 0xb0226a08 eip 0x0ac289

May 23 06:34:01.301: vcpu-0| Backtrace[3] 0xb0226a28 eip 0x9697a5eb

May 23 06:34:01.301: vcpu-0| Backtrace[4] 0xb0226d68 eip 0xffffffff

May 23 06:34:01.301: vcpu-0| Backtrace[5] 0xb0226dd8 eip 0x073947

May 23 06:34:01.301: vcpu-0| Backtrace[6] 0xb0226e68 eip 0x10eea1

May 23 06:34:01.301: vcpu-0| Backtrace[7] 0xb0226ea8 eip 0x0fe9f6

May 23 06:34:01.301: vcpu-0| Backtrace[8] 0xb0226ee8 eip 0x11fa6b

May 23 06:34:01.301: vcpu-0| Backtrace[9] 0xb0226f08 eip 0x0fed3d

May 23 06:34:01.301: vcpu-0| Backtrace[10] 0xb0226f78 eip 0x0a98f7

May 23 06:34:01.301: vcpu-0| Backtrace[11] 0xb0226fc8 eip 0x9693ec55

May 23 06:34:01.301: vcpu-0| Backtrace[12] 0xb0226fec eip 0x9693eb12

May 23 06:34:01.301: vcpu-0| Backtrace[13] 00000000 eip 00000000

May 23 06:34:01.301: vcpu-0| Msg_Post: Error

May 23 06:34:01.301: vcpu-0| http://msg.log.error.unrecoverable VMware Fusion unrecoverable error: (vcpu-0)

May 23 06:34:01.301: vcpu-0| Unexpected signal: 10.

May 23 06:34:01.301: vcpu-0| http://msg.panic.haveLog A log file is available in "/Users/jcooke/Documents/Virtual Machines/Windows XP Professional.vmwarevm/vmware.log". http://msg.panic.requestSupport.withLog Please request support and include the contents of the log file. http://msg.panic.requestSupport.vmSupport.apple

May 23 06:34:01.301: vcpu-0| To collect data to submit to VMware support, run "/Library/Application Support/VMware Fusion/vm-support.tool".

May 23 06:34:01.301: vcpu-0| http://msg.panic.response We will respond on the basis of your support entitlement.

May 23 06:34:01.301: vcpu-0| -

---

[admin]

That's most of the important part of the log (you got the backtrace, which is good), but you left out one important detail - is the log from 1.1.2 or 2.0? Alternately, just include the whole log (attaching it instead of cut-n-paste is also an option).

[flyby]

etung:

I am running 2.0 now. I have attached a full log which just generated. Below is the only related entry from the console, if that helps.

The problem has been consistent from 1.1.2 and 2.0 but it seems that XP would make it a little further along in the boot with 1.1.2. In 2.0 it never gets past the welcome screen.

Hope this helps.

5/23/08 1:59:18 PM .com.vmware.fusion[614] VMHS: Connection to VM broken: cfg: /Users/jcooke/Documents/Virtual Machines/Windows XP Professional.vmwarevm/Windows XP Professional.vmx; error: Pipe connection has been broken; state: 3

[admin]

I don't see a log, try again? Sometimes the forum doesn't like .log files, zipping seems to get around this.

[flyby]

Zip file attached.

[flyby]

For etung, and anyone else that has been following this post, I seem to have solved the problem.

I thought I would try to restore a previous version of the VM data file to see if that would solve the problem. As a precaution, I tried to backup the current file but found that portions of the file could not be read, that seemed to confirm my original suspicion that the file may have been corrupted. Using TIme Machine, I went back to a previous version of the VM file, the most recent one that TM had available. I restored that, keeping a copy of the original. VM started OK after that. I don't know how much, if any, data may have been lost because I haven't run through all the possibilities, but it doesn't look like a lot.

If the VM file was totally mangled, it may help to explain why TM stopped in it's tracks. If I couldn't copy the file, it stands to reason that TM may have had issues backing it up. I probably won't know for a while if everything is back to normal but it looks ok so far.

[admin]

If the filesystem was corrupted, that would explain Fusion's behavior as well (problems whenever it hit one of the patches that couldn't be read). I would check your physical disk for consistency (e.g. with an OS X install disk).

[flyby]

I did check the drive and it didn't report any errors. So far it appears the problem was contained to the actual VM files, the rest of the machine did not experience any problems during this issue. So far it appears to be working normally. I'm using 2.0b.

[admin]

If copying the virtual machine via the Finder resulted in errors, something must have been up with the filesystem. Finder doesn't know anything about the virtual machine format; it can't tell the difference between a corrupted or truncated file (from Fusion's point of view) and a good one.

Whatever the reason, glad it's working now.