blix3
Contributor
Contributor

Same vmx-vmdk runs on IDE disk but crashes on SATA

I recently upgraded my HDD from a 160GB IDE to a 250GB SATA. All my programs and data made the transition smoothly, with the exception of the vmx-vmdk files for XPSP2. When Fusion tries to run the vmx, it crashes.

There were no hardware or software changes to my system (Intel Core 2 Duo, 2GB RAM, OS X 10.4.10). I just cloned the old IDE to the new SATA, and all programs (MS Office, iLife 08, Firefox, etc. run fine, as they did on the previous disk. Fusion starts up fine, too, but when I try to run the vmx...CRASH.

I tried uninstalling and reinstalling Fusion and recopying the vmx and vmdk files from the old HDD. They still crash.

What could be the problem?

0 Kudos
11 Replies
rcardona2k
Immortal
Immortal

When you "crash", what actually happens, does:

Windows not start and stay dark?

Windows generate a blue screen error?,

the Fusion application window disappear and OS X says Fusion quit unexpectedly?,

does your OS X screen dim with a power switch in the background?

something else?

You may need to provide some log files, try reading for details on where to locate them.

0 Kudos
blix3
Contributor
Contributor

"The application VMWare Fusion quit unexpectedly" is the message that appears after Fusion crashes. Fusion starts up and shows the vmk. I select it. If I want to change the settings, which I've fiddled with to try to prevent a crash, I can. A black screen with a large start button is in the background. It's when I click on that button to start XP that Fusion crashes.

The only difference in this system (home-built, Intel Core Duo, 2GB RAM, OS X 10.4.10) that previously ran this XPSP2 guest for months is that I upgraded its HDD from an IDE to a SATA. I was using 1.0.0 build 51348 on the IDE disk and moved that to the SATA. Since that crashed from the first try, I upgraded to 1.1.0 build 62573. Fusion still crashes. I tried this guest on my iMac 20 (Intel Core Duo, 2GB RAM, OS X 10.4.11) and it runs fine. The guest was made with VMWare Converter on XPSP2 several months ago.

When I first cloned the IDE to the SATA, all the VMWare related folders and files came along. When Fusion continually crashed, I uninstalled and reinstalled both builds several times, and I went so far as to find and delete related folders that were not removed with the uninstallations.

Here's one of the logs:

Dec 22 23:21:05.260: vmfusion| Log for VMware Fusion pid=309 version=1.0 build=build-51348 option=Release

Dec 22 23:21:05.260: vmfusion| Hostname=taylor-familys-computer.local

Dec 22 23:21:05.260: vmfusion| Using log file /Users/taylorfamily/Library/Logs/VMware Fusion/vmware-vmfusion.log

Dec 22 23:21:05.366: vmfusion| Failed to acquire super user privileges.

Dec 22 23:21:05.367: vmfusion| UUID: Unable to open /dev/mem: No such file or directory

Dec 22 23:21:05.379: vmfusion| Msg_Reset:

Dec 22 23:21:05.379: vmfusion| http://msg.dictionary.load.statFailed Unable to get information about file "/Library/Application Support/VMware Fusion/messages/en/tip_list.vmsg": No such file or directory.

Dec 22 23:21:05.379: vmfusion| -


Dec 22 23:21:05.379: vmfusion| Cannot load message dictionary "/Library/Application Support/VMware Fusion/messages/en/tip_list.vmsg".

Dec 22 23:21:05.382: vmfusion| XXXMACOS: Implement HostDeviceInfo_FindHostSoundDevices

Dec 22 23:21:05.386: vmfusion| Could not open /proc/net/dev

Dec 22 23:21:05.387: vmfusion| SGMAC: XXX: SGHostEnumerate not yet implemented

Dec 22 23:21:05.388: vmfusion| Failed to acquire super user privileges.

Dec 22 23:21:05.388: vmfusion| SMBIOS: can't open /dev/mem: Could not find the file

Dec 22 23:21:05.388: vmfusion| VmhsHostInfoPopulateSystem: Could not get information from smbios to populate VMDB.

Dec 22 23:21:05.388: vmfusion| Failed to acquire super user privileges.

Dec 22 23:21:05.388: vmfusion| UUID: Unable to open /dev/mem: No such file or directory

Dec 22 23:21:05.388: vmfusion| HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 1.

Dec 22 23:21:05.388: vmfusion| HOSTINFO: This machine has 1 physical CPUS, 2 total cores, and 2 logical CPUs.

Dec 22 23:21:05.531: vmfusion| Foundry Init: setting up global state (0 threads)

Dec 22 23:21:05.531: vmfusion| Foundry Init: version 2, hostType 1, hostName (null), hostPort 0, options 0x203

Dec 22 23:21:09.745: | Failed to acquire super user privileges.

Dec 22 23:21:09.745: | UUID: Unable to open /dev/mem: No such file or directory

Dec 22 23:21:09.745: | Failed to acquire super user privileges.

Dec 22 23:21:09.745: | FILE: ScanDirectory discarding file '/Users/taylorfamily/Virtual Machines/XP-ASUS/XP-ASUS.vmx.lck/M57991.lck'; invalid executionID.

Dec 22 23:21:09.746: | Failed to acquire super user privileges.

Dec 22 23:21:09.747: | Reloading config state: /Users/taylorfamily/Virtual Machines/XP-ASUS/XP-ASUS.vmx

Dec 22 23:21:09.777: | Failed to acquire super user privileges.

Dec 22 23:21:09.778: | Failed to acquire super user privileges.

Dec 22 23:21:09.918: vmfusion| readlink /var/run/vmware/d345e01b329e52d7cca574f327b75221: No such file or directory

Dec 22 23:21:09.918: vmfusion| readlink /var/run/vmware/%2fUsers%2ftaylorfamily%2fVirtual%20Machines%2fXP%2dASUS%2fXP%2dASUS%2evmx: No such file or directory

Dec 22 23:22:09.396: vmfusion| Failed to acquire super user privileges.

Dec 22 23:22:09.397: vmfusion| Failed to acquire super user privileges.

Dec 22 23:22:54.262: vmfusion| Failed to acquire super user privileges.

Dec 22 23:22:54.264: vmfusion| Failed to acquire super user privileges.

Dec 22 23:22:54.276: vmfusion| VMHSVMCbPower: Setting state of VM /vm/#28cfe07c8fe83d4b/ to powerOn with option hard

Dec 22 23:22:54.277: vmfusion| VMHS: Exec()'ing /Library/Application Support/VMware Fusion/vmware-vmx, /Users/taylorfamily/Virtual Machines/XP-ASUS/XP-ASUS.vmx

Dec 22 23:22:55.081: vmfusion| Caught signal 10 -- tid -1610559488

Dec 22 23:22:55.081: vmfusion| SIGNAL: eip 0x156ef3 esp 0xbfffd6e0 ebp 0xbfffd708

Dec 22 23:22:55.081: vmfusion| SIGNAL: eax 0x0 ebx 0x156ef0 ecx 0x0 edx 0x1 esi 0xbfffe9a8 edi 0x0

Dec 22 23:22:55.081: vmfusion| SIGNAL: stack 0xbfffd6e0 : 0x01b18a30 0xbfffdb30 0x00000000 0x00000000

Dec 22 23:22:55.081: vmfusion| SIGNAL: stack 0xbfffd6f0 : 0x0202b778 0x16c0fe47 0xbfffd838 0x000e12f6

Dec 22 23:22:55.081: vmfusion| SIGNAL: stack 0xbfffd700 : 0xbfffe9a8 0x00000000 0xbfffe9d8 0x000e1fa7

Dec 22 23:22:55.081: vmfusion| SIGNAL: stack 0xbfffd710 : 0x00000000 0xbfffdb30 0xbfffe9a8 0xbfffe0ba

Dec 22 23:22:55.081: vmfusion| SIGNAL: stack 0xbfffd720 : 0x0055a404 0x01b18810 0x00000000 0x00000000

Dec 22 23:22:55.081: vmfusion| SIGNAL: stack 0xbfffd730 : 0x00000000 0xbfffdd2a 0xbfffd758 0x000a9508

Dec 22 23:22:55.081: vmfusion| SIGNAL: stack 0xbfffd740 : 0xbfffd8c4 0xbfffdd2a 0x00000005 0x000af1b3

Dec 22 23:22:55.081: vmfusion| SIGNAL: stack 0xbfffd750 : 0x000be7f1 0xbfffdd27 0xbfffd898 0x000be8b2

Dec 22 23:22:55.081: vmfusion| Backtrace:

Dec 22 23:22:55.081: vmfusion| Backtrace[0] 0xbfffd378 eip 0x0cdf79

Dec 22 23:22:55.081: vmfusion| Backtrace[1] 0xbfffd3d8 eip 0x16f31a

Dec 22 23:22:55.081: vmfusion| Backtrace[2] 0xbfffd3f8 eip 0x9011072c

Dec 22 23:22:55.081: vmfusion| Backtrace[3] 0xbfffd708 eip 0xffffffff

Dec 22 23:22:55.081: vmfusion| Backtrace[4] 0xbfffe9d8 eip 0x0e1fa7

Dec 22 23:22:55.081: vmfusion| Backtrace[5] 0xbfffec78 eip 0x0f2f94

Dec 22 23:22:55.081: vmfusion| Backtrace[6] 0xbfffee48 eip 0x0ad79b

Dec 22 23:22:55.081: vmfusion| Backtrace[7] 0xbfffee68 eip 0x0ad8bb

Dec 22 23:22:55.081: vmfusion| Backtrace[8] 0xbfffeee8 eip 0x0c22cd

Dec 22 23:22:55.081: vmfusion| Backtrace[9] 0xbfffef18 eip 0x395d49

Dec 22 23:22:55.081: vmfusion| Backtrace[10] 0xbfffef48 eip 0x395dac

Dec 22 23:22:55.081: vmfusion| Backtrace[11] 0xbfffefa8 eip 0x90842faf

Dec 22 23:22:55.081: vmfusion| Backtrace[12] 0xbfffefe8 eip 0x90842d24

Dec 22 23:22:55.081: vmfusion| Backtrace[13] 0xbffff538 eip 0x9082cf92

Dec 22 23:22:55.081: vmfusion| Backtrace[14] 0xbffff578 eip 0x9082cace

Dec 22 23:22:55.081: vmfusion| Backtrace[15] 0xbffff5b8 eip 0x92dec8d8

Dec 22 23:22:55.081: vmfusion| Backtrace[16] 0xbffff628 eip 0x92debf19

Dec 22 23:22:55.081: vmfusion| Backtrace[17] 0xbffff648 eip 0x92debe39

Dec 22 23:22:55.081: vmfusion| Backtrace[18] 0xbffff968 eip 0x93270465

Dec 22 23:22:55.081: vmfusion| Backtrace[19] 0xbffffbc8 eip 0x93270056

Dec 22 23:22:55.081: vmfusion| Backtrace[20] 0xbffffc88 eip 0x93269ddb

Dec 22 23:22:55.081: vmfusion| Backtrace[21] 0xbffffcc8 eip 0x9325dd2f

Dec 22 23:22:55.081: vmfusion| Backtrace[22] 0xbffffd08 eip 0x066dba

Dec 22 23:22:55.081: vmfusion| Backtrace[23] 0xbffffd48 eip 0x0032da

Dec 22 23:22:55.081: vmfusion| Backtrace[24] 0xbffffd64 eip 0x0031f5

Dec 22 23:22:55.081: vmfusion| Backtrace[25] 00000000 eip 0x000002

Dec 22 23:22:55.082: vmfusion| Unexpected signal: 10.

Dec 22 23:22:55.082: vmfusion| Backtrace:

Dec 22 23:22:55.082: vmfusion| Backtrace[0] 0xbfffcf28 eip 0x0cdf79

Dec 22 23:22:55.082: vmfusion| Backtrace[1] 0xbfffd348 eip 0x0c7ebf

Dec 22 23:22:55.082: vmfusion| Backtrace[2] 0xbfffd378 eip 0x066d6f

Dec 22 23:22:55.082: vmfusion| Backtrace[3] 0xbfffd3d8 eip 0x16f23f

Dec 22 23:22:55.082: vmfusion| Backtrace[4] 0xbfffd3f8 eip 0x9011072c

Dec 22 23:22:55.082: vmfusion| Backtrace[5] 0xbfffd708 eip 0xffffffff

Dec 22 23:22:55.082: vmfusion| Backtrace[6] 0xbfffe9d8 eip 0x0e1fa7

Dec 22 23:22:55.082: vmfusion| Backtrace[7] 0xbfffec78 eip 0x0f2f94

Dec 22 23:22:55.082: vmfusion| Backtrace[8] 0xbfffee48 eip 0x0ad79b

Dec 22 23:22:55.082: vmfusion| Backtrace[9] 0xbfffee68 eip 0x0ad8bb

Dec 22 23:22:55.082: vmfusion| Backtrace[10] 0xbfffeee8 eip 0x0c22cd

Dec 22 23:22:55.082: vmfusion| Backtrace[11] 0xbfffef18 eip 0x395d49

Dec 22 23:22:55.082: vmfusion| Backtrace[12] 0xbfffef48 eip 0x395dac

Dec 22 23:22:55.082: vmfusion| Backtrace[13] 0xbfffefa8 eip 0x90842faf

Dec 22 23:22:55.082: vmfusion| Backtrace[14] 0xbfffefe8 eip 0x90842d24

Dec 22 23:22:55.082: vmfusion| Backtrace[15] 0xbffff538 eip 0x9082cf92

Dec 22 23:22:55.082: vmfusion| Backtrace[16] 0xbffff578 eip 0x9082cace

Dec 22 23:22:55.082: vmfusion| Backtrace[17] 0xbffff5b8 eip 0x92dec8d8

Dec 22 23:22:55.082: vmfusion| Backtrace[18] 0xbffff628 eip 0x92debf19

Dec 22 23:22:55.082: vmfusion| Backtrace[19] 0xbffff648 eip 0x92debe39

Dec 22 23:22:55.082: vmfusion| Backtrace[20] 0xbffff968 eip 0x93270465

Dec 22 23:22:55.082: vmfusion| Backtrace[21] 0xbffffbc8 eip 0x93270056

Dec 22 23:22:55.082: vmfusion| Backtrace[22] 0xbffffc88 eip 0x93269ddb

Dec 22 23:22:55.082: vmfusion| Backtrace[23] 0xbffffcc8 eip 0x9325dd2f

Dec 22 23:22:55.082: vmfusion| Backtrace[24] 0xbffffd08 eip 0x066dba

Dec 22 23:22:55.082: vmfusion| Backtrace[25] 0xbffffd48 eip 0x0032da

Dec 22 23:22:55.082: vmfusion| Backtrace[26] 0xbffffd64 eip 0x0031f5

Dec 22 23:22:55.082: vmfusion| Backtrace[27] 00000000 eip 0x000002

Dec 22 23:22:55.082: vmfusion| Msg_Post: Error

Dec 22 23:22:55.082: vmfusion| http://msg.log.error.unrecoverable VMware Fusion unrecoverable error: (vmfusion)

Dec 22 23:22:55.082: vmfusion| Unexpected signal: 10.

Dec 22 23:22:55.082: vmfusion| http://msg.panic.haveLog A log file is available in "/Users/taylorfamily/Library/Logs/VMware Fusion/vmware-vmfusion.log". http://msg.panic.requestSupport.withLog Please request support and include the contents of the log file. http://msg.panic.requestSupport.vmSupport

Dec 22 23:22:55.082: vmfusion| To collect files to submit to VMware support, run "/Library/Application Support/VMware Fusion/vm-support.tool".

Dec 22 23:22:55.082: vmfusion| http://msg.panic.response We will respond on the basis of your support entitlement.

Dec 22 23:22:55.082: vmfusion| -


0 Kudos
rcardona2k
Immortal
Immortal

Anytime you copy a VM you can introduce file permission access problems. First thing to try is run Apple's Disk Utility in Applications > Utilities and Repair Permissions for your disk(s). Next on the virtual machine bundle itself in Documents > Virtual Machines, try the directions in this message:

0 Kudos
blix3
Contributor
Contributor

Yes, I have two Macs and a homebuilt, so I'm familiar with the need to repair permissions. I believe that the cloning program (Clonetool) does that as part of the clone, but still, I also repaired permissions first thing after booting the new disk. Again, all other software, including iLife '08, MS Office, etc. are working fine on the new disk. The ONLY application that has failed to run on the new disk is Fusion.

0 Kudos
rcardona2k
Immortal
Immortal

VMware does not support (and can't) or test Fusion on "home-built" Intel boxes. Apple licensing does not sanction running OS X off their hardware in any way and you agreed to those terms when you bought your Mac or Leopard.

If you can not reproduce this problem on an Apple Mac, you have built a bed to lay in. There are Macs that definitely have SATA drives like newer MacBook Pros and MacPros, so that in itself may not be the issue. Apple tests their hardware controllers with the OS for very good reasons and Fusion makes deep use of the kernel and drivers in OS, it's not a run-of-the-mill Office app.

Sorry.

edit: remove comment about Core Duo + SATA as all MacBook Pros have SATA.

0 Kudos
blix3
Contributor
Contributor

FYI, Apple made Macs with Core Duo (not Core 2 Duo) processors and SATA drives in 2006. I bought two of them, an iMac 20 with an Intel Core Duo and a 250GB 3.5" SATA HDD and a Macbook 13 with a Core Duo and a 120GB 2.5" SATA HDD.

My homebuilt is a hobby. It has a Core 2 Duo and a 160GB IDE that runs Fusion fine and a 250GB SATA that doesn't. I can continue running Fusion on the former drive, but it would be nice to have the added space of the latter. I'll figure out how to do so, but on the off chance that someone else might have had the same experience, I thought I'd ask on the forum.

Also, I tried your suggestion regarding the ".vmwarevm" extension from the guest, confirming permissions for the folder, and then adding back the vmwarevm (although in my case, the extension was vmdk) and this did not prevent Fusion from crashing.

Regarding your lecture to me on behalf of Apple, save your breath, or your typing. I bought multiple copies and family packs of the software and I'll run it on whatever hardware I want, thank you.

0 Kudos
rcardona2k
Immortal
Immortal

FYI, Apple made Macs with Core Duo (not Core 2 Duo) processors and SATA drives in 2006. I bought two of them, an iMac 20 with an Intel Core Duo and a 250GB 3.5" SATA HDD and a Macbook 13 with a Core Duo and a 120GB 2.5" SATA HDD.

Yes my mistake, sorry I corrected my statement, see the edit above. (This was before you replied but you may not have seen it.)

Also, I tried your suggestion regarding the ".vmwarevm" extension from the guest, confirming permissions for the folder, and then adding back the vmwarevm (although in my case, the extension was vmdk) and this did not prevent Fusion from crashing.

Changing the extension wasn't the point, it was to change the bundle to a folder so the Finder would let you apply recursive permissions. A Fusion-built VM has the bundle extension .vmwarevm which must be temporarily removed to expose the folder so the Finder can offer additional settings.

My homebuilt is a hobby. It has a Core 2 Duo and a 160GB IDE that runs Fusion fine and a 250GB SATA that doesn't. I can continue running Fusion on the former drive, but it would be nice to have the added space of the latter. I'll figure out how to do so, but on the off chance that someone else might have had the same experience, I thought I'd ask on the forum. Regarding your lecture to me on behalf of Apple, save your breath, or your typing. I bought multiple copies and family packs of the software and I'll run it on whatever hardware I want, thank you

I will not repeat my two sentence "lecture" and I didn't accuse you of anything like piracy - I own the Leopard family pack too, btw. In the interest of full-disclosure I thank you for admitting your configuration so you do not fruitlessly waste other people's time with your "hobbies." Sure if someone is running a similar configuration they can confirm or deny the problem. VMware will not support your configuration and based on the traffic here, this may not be the forum for this kind of experimenting. Enjoy your "new" machine.

0 Kudos
blix3
Contributor
Contributor

You referred me to the following regarding file/folder permissions (which would apply to VMWare on my iMac, a system you do support):

1. Shutdown your VM

2. Find your VM's icon under Virtual Machines and click on it to highlight it and choose File > Get Info in the Finder

3. When the VM's Info window comes up in "Name & Extension" remove the ".vmwarevm" part of the name.

4. Close the Info window, confirm you want to remove the extension and your VM's icon should now be a folder icon.

5. Get Info on the VM "folder" and open the triangle twistie under

"Ownership & Permissions" to access the "Details" triangle twistie.

6. Open Details, verify you're the Owner with Read & Write access.

7. Click on "Apply to enclosed items" and confirm you want to apply

permissions and if necessary authenticate yourself with your login.

(See attachment below for reference on this step)

8. Before closing Info, go back to "Name & Extension" and re-add ".vmwarevm", close the Info window

9. Click "Add" to restore the vmwarevm extension when prompted.

Hmmmm. Perhaps the above refers to VMs made by Fusion, because there is no such "VM icon" or ".vmwarevm" extension on my VM, which was made by VMWare Converter and copied to a Virtual Machines folder I created in OS X. My VM is "XP-ASUS.vmdk" Would the above still apply if I followed the directions and changed the vmdk extension, etc.?

0 Kudos
rcardona2k
Immortal
Immortal

Right the difference between VMs brought from Workstation or made with Converter is these are simple files in a folder and referenced by the .vmx file. A Fusion bundle is a presentation formality. If you want to see what it looks like, add ".vmwarevm" to the folder enclosing the .vmx file and accept to add the ".vmwarevm" extension. Then the folder becomes a VMware Fusion VM bundle. It's still a folder, etc but the Finder presents it as a VM document bundle. Since your cloner takes care of permissions, the ownership and permissions should be OK. I wrote the instructions this way to keep users from changing permission on each file (.vmx, vmdk. vmss, .vmem, .vmsn, .log, etc). You can apply the permissions to your folder and ignore renaming the folder.

0 Kudos
blix3
Contributor
Contributor

Thanks for the explanation. I won't trouble you for any further suggestions. FYI, I re-cloned to the SATA disk. All applications run just fine, with the exception of Fusion, which still crashes when I try to run the XP virtual machine. Added the .vmwarevm extension to the folder enclosing the XP virtual machine and updated file/folder permissions. Makes a nice little bundle, as you described, but it still crashes. Removed the name extension. Still crashes. Weird. Next, I'll go get the original vmdk, vmx and associated files from the XP disk on which Converter made them. If they don't work, then I guess I will make a new XP virtual machine from scratch on this disk.

0 Kudos
blix3
Contributor
Contributor

I got it working! The problem is a conflict between the new SATA HDD and the existing IDE CD/DVD. Once I realized OS X wasn't able to detect and mount the CD/DVD, I tried unchecking CD/DVD in virtual machine settings and that allowed the vm to run. Now I'll either have to find and eliminate the SATA-IDE conflict or perhaps get a SATA DVD or adapter, which might bypass the conflict.

0 Kudos