000002.vmdk' or one of the snapshot disks it depends on, Reason: Insufficient permission to access file

[m_therrien]

Copied a VM from one Mac to 2nd Mac. Added user to all Package Contents files with Read/Write permissions and I laucnch Fusion I get this:

VMWare Fusion - Cannot open the disk '/Users/m_therrien/Documents/Virtual Machines/Windows Vista.vmwarevm/Windows Vista-000002.vmdk' or one of the snapshot disks it depends on, Reason: Insufficient permission to access file

Windows Vista-000002.vmdk is set as Read/Write

Thanks for any suggestions

[m_therrien]

I also made sure to set R/W for the user on the VM folder itself.

This from the vmware.log

Feb 04 14:57:11.668: vmx| KHZEstimate 1990099

Feb 04 14:57:11.668: vmx| MHZEstimate 1990

Feb 04 14:57:11.668: vmx| NumVCPUs 2

Feb 04 14:57:11.669: vmx| PShare: enabled 1, scanRate 32, checkRate 16

Feb 04 14:57:11.669: vmx| UUID: Unable to open /dev/mem: No such file or directory

Feb 04 14:57:11.669: vmx| UUID: location-UUID is 56 4d 9b be 76 e8 c8 b2-ea c8 e4 ca fb 65 5b 7f

Feb 04 14:57:11.669: vmx| UUID: Unable to open /dev/mem: No such file or directory

Feb 04 14:57:11.669: vmx| UUID: location-UUID is 56 4d bc 7e 90 91 f3 83-1a 14 f8 ea 97 d0 a9 1d

Feb 04 14:57:11.669: vmx| UUID: Unable to open /dev/mem: No such file or directory

Feb 04 14:57:11.669: vmx| UUID: location-UUID is 56 4d 9b be 76 e8 c8 b2-ea c8 e4 ca fb 65 5b 7f

Feb 04 14:57:11.670: vmx| AIOGNRC: numThreads=18 ide=0, scsi=1, passthru=1

Feb 04 14:57:11.670: vmx| WORKER: Creating new group with numThreads=18 (18)

Feb 04 14:57:11.670: vmx| Replay State = 0

Feb 04 14:57:11.670: vmx| minDEThreshold: 70

Feb 04 14:57:11.670: vmx| MM: Using partialmap, 262144 pages AC 0 CE 1 TM 0 DOHU 0

Feb 04 14:57:11.671: vmx| MStat: Creating Stat vm.uptime

Feb 04 14:57:11.671: vmx| MStat: Creating Stat vm.suspendTime

Feb 04 14:57:11.671: vmx| MStat: Creating Stat vm.powerOnTimeStamp

Feb 04 14:57:11.680: vmx| VMXAIOMGR: Using: simple=Generic unbuf=Generic

Feb 04 14:57:11.686: vmx| FILE: CreateEntryDirectory creation failure on '/Users/m_therrien/Documents/Virtual Machines/Windows Vista.vmwarevm/Windows Vista.vmsd.lck': Permission denied

Feb 04 14:57:11.686: vmx| FILE: FileLockIntrinsic implicit S lock succeeded on '/Users/m_therrien/Documents/Virtual Machines/Windows Vista.vmwarevm/Windows Vista.vmsd'.

Feb 04 14:57:11.695: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Feb 04 14:57:11.705: vmx| DISK: OPEN scsi0:0 '/Users/m_therrien/Documents/Virtual Machines/Windows Vista.vmwarevm/Windows Vista-000002.vmdk' persistent R[]

Feb 04 14:57:11.721: vmx| FILE: CreateEntryDirectory creation failure on '/Users/m_therrien/Documents/Virtual Machines/Windows Vista.vmwarevm/Windows Vista-000002.vmdk.lck': Permission denied

Feb 04 14:57:11.721: vmx| FILE: FileIO_Lock on '/Users/m_therrien/Documents/Virtual Machines/Windows Vista.vmwarevm/Windows Vista-000002.vmdk' failed: Permission denied

Feb 04 14:57:11.721: vmx| DISKLIB-LINK : "/Users/m_therrien/Documents/Virtual Machines/Windows Vista.vmwarevm/Windows Vista-000002.vmdk" : failed to open (Insufficient permission to access file).

Feb 04 14:57:11.721: vmx| DISKLIB-CHAIN : "/Users/m_therrien/Documents/Virtual Machines/Windows Vista.vmwarevm/Windows Vista-000002.vmdk" : failed to open (Insufficient permission to access file).

Feb 04 14:57:11.721: vmx| DISKLIB-LIB : Failed to open '/Users/m_therrien/Documents/Virtual Machines/Windows Vista.vmwarevm/Windows Vista-000002.vmdk' with flags 0x1a (Insufficient permission to access file).

Feb 04 14:57:11.721: vmx| DISK: Cannot open disk "/Users/m_therrien/Documents/Virtual Machines/Windows Vista.vmwarevm/Windows Vista-000002.vmdk": Insufficient permission to access file (38).

Feb 04 14:57:11.722: vmx| Msg_Post: Error

Feb 04 14:57:11.722: vmx| http://msg.disk.noBackEnd Cannot open the disk '/Users/m_therrien/Documents/Virtual Machines/Windows Vista.vmwarevm/Windows Vista-000002.vmdk' or one of the snapshot disks it depends on.

Feb 04 14:57:11.722: vmx| http://msg.disk.configureDiskError Reason: Insufficient permission to access file.----

---

Feb 04 14:57:18.833: vmx| Module DiskEarly power on failed.

Feb 04 14:57:18.833: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0

Feb 04 14:57:18.834: vmx| WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0

Feb 04 14:57:18.852: vmx| VMMon_UnlockPage: failed uvAddr = 13521000, errno = 22

Feb 04 14:57:18.852: vmx| VMMon_UnlockPage: failed uvAddr = 132D0000, errno = 22

Feb 04 14:57:18.852: vmx| Transitioned vmx/execState/val to suspended

Feb 04 14:57:19.848: vmx| vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF

Feb 04 14:57:19.849: vmx| VMX idle exit

Feb 04 14:57:19.881: vmx| Flushing VMX VMDB connections

Feb 04 14:57:19.884: vmx| IPC_exit: disconnecting all threads

Feb 04 14:57:19.884: vmx| VMX exit (0).

Feb 04 14:57:19.885: vmx| AIOMGR-S : stat o=1 r=0 w=0 i=0 br=0 bw=0

[Technogeezer]

Please open a terminal and post the output of the following command:

ls -alR /Users/m_therrien/Documents/Virtual Machines/Windows Vista.vmwarevm

[m_therrien]

Thank you so much - listing the user permissions did the trick - Windows Vista.vmwarevm did not have the user/account 'attached' to the file. Once added with R/W permissions - voila!

Thanks again

Matthew

[RobocopNZ]

FWIW all my VMs for VMWare were broken. No idea why. I finally used BatchMod to set all permissions to 777 which did not solve the problem, then I did a "Clear ACLs" and the first VM just started working !  All good, and I have changed permissions of all the files inside the VM back to 755.  Bigger questions is, why did this happen, and why are so many others having similar problems?

[likelyja]

I am having a similar problem but am not able to resolve. Can you please look at the attachment and offer suggestion?

I have tried a few different ways but no luck. It sounds like you were able to resolve your issue.

Thank you in advanced!