I created five virtual machines in VMware server 5.0. I then tried to load them in VMware workstation 6.0. One loaded succesfully the other four all gave me the message:
"Cannot open the disk 'XXX' or one of the snapshot disks it depends on. reason: failed to lock the file.
I have tried deleting all the .lck files AND switch off all the VMware services but the error still persists.
Post a listing (including file sizes in bytes) of the VM folders in question.
Post the contents of the following files:
xpp-spring02.vmdk
xpp-spring02.vmx
xpp-spring02.vmx
config.version = "8"
virtualHW.version = "4"
memsize = "512"
MemAllowAutoScaleDown = "FALSE"
MemTrimRate = "-1"
displayName = "PimsCalc2"
guestOS = "winxppro"
numvcpus = "2"
tools.remindInstall = "FALSE"
floppy0.present = "FALSE"
floppy0.autodetect = "TRUE"
floppy0.filename = "auto detect"
usb.present = "TRUE"
sound.present = "TRUE"
sound.filename = "-1"
sound.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.addressType = "generated"
ethernet0.connectionType = "hostonly"
ide0:0.present = "TRUE"
ide0:0.fileName = "xpp-spring02.vmdk"
ide0:1.present = "TRUE"
ide0:1.autodetect = "TRUE"
ide0:1.filename = "auto detect"
ide0:1.deviceType = "cdrom-raw"
ide1:0.present = "TRUE"
ide1:0.autodetect = "TRUE"
ide1:0.filename = "auto detect"
ide1:0.deviceType = "cdrom-raw"
mks.keyboardFilter = "allow"
nvram = "XPP-spring02.nvram"
deploymentPlatform = "windows"
tools.upgrade.policy = "useGlobal"
isolation.tools.hgfs.disable = "TRUE"
sharedFolder.maxNum = "4"
sharedFolder0.present = "TRUE"
sharedFolder0.enabled = "TRUE"
sharedFolder0.readAccess = "TRUE"
sharedFolder0.hostPath = "H:\POP\PIMS"
sharedFolder0.guestName = "Pims"
sharedFolder0.expiration = "never"
tools.syncTime = "FALSE"
sharedFolder1.present = "TRUE"
sharedFolder1.enabled = "TRUE"
sharedFolder1.readAccess = "TRUE"
sharedFolder1.hostPath = "Y:\"
sharedFolder1.guestName = "Untitled-1"
sharedFolder1.expiration = "never"
sharedFolder2.present = "TRUE"
sharedFolder2.enabled = "TRUE"
sharedFolder2.readAccess = "TRUE"
sharedFolder2.writeAccess = "TRUE"
sharedFolder2.hostPath = "C:\Pims_spool"
sharedFolder2.guestName = "C$Pims"
sharedFolder2.expiration = "never"
priority.grabbed = "high"
sharedFolder3.present = "TRUE"
sharedFolder3.enabled = "TRUE"
sharedFolder3.readAccess = "TRUE"
sharedFolder3.hostPath = "C:\PIMS"
sharedFolder3.guestName = "PIMS"
sharedFolder3.expiration = "never"
workingDir = ""
priority.ungrabbed = "normal"
ide0:0.redo = ""
ethernet0.generatedAddress = "00:0c:29:79:67:b0"
sound.virtualDev = "es1371"
uuid.location = "56 4d b0 e9 71 58 42 65-54 a1 f5 05 ff 53 95 a6"
uuid.bios = "56 4d df e2 85 a8 5f f9-bd ed 66 c4 ef 79 67 b0"
ethernet0.generatedAddressOffset = "0"
extendedConfigFile = "xpp-spring02.vmxf"
virtualHW.productCompatibility = "hosted"
inVMTeam = "TRUE"
xpp-spring02.vmdk
Disk DescriptorFile
version=1
CID=86f41b13
parentCID=ffffffff
createType="monolithicFlat"
Extent description
RW 104857600 FLAT "xpp-spring02-flat.vmdk" 0
The Disk Data Base
#DDB
ddb.geometry.biosSectors = "63"
ddb.geometry.biosHeads = "255"
ddb.geometry.biosCylinders = "6527"
ddb.adapterType = "ide"
ddb.geometry.sectors = "63"
ddb.geometry.heads = "255"
ddb.geometry.cylinders = "6527"
ddb.thinProvisioned = "1"
ddb.toolsVersion = "7240"
ddb.virtualHWVersion = "4"
This VM is part of a team.
Did you copy the other team members as well?
Also please attach all the log files as well.
This looks like a permission issue.
Do you run WS with admin rights? If not try it and report back.
I am not sure what that means....
I am a local administrator on the machine that hosts the VMware AND these virtual machines were all working fine in VMWare server.
According to the log WS isn't able to lock the files.
This usually is a result of missing permissions or an incompatible filesystem.
These virtual machines were all working in VMware server on the same physical host in exactly the same physical location. all i have done is un install vmware server 5, re-install vmware workstation 6 (as that is where my original builds were made) and then tried to start the machines.
What specific permissions other than admin access on the PC are we talking about. This entire setup has only ever been accessed with one local admin account (mine) so on the windows side there can't be any permission issues ??
In this case try the following:
Uninstall WS, reboot, run the WS installer with the /C (cleanup) option, reboot, then install WS again, reboot and try to power on a VM.
Doing a cleanup install followed by a reboot then a re-install then a reboot still does not fox the problem. As this problem is apparently caused by a bug introduced in version 6, would reverting to version 5 fix this problem ??
thanks
I'm not sure if the problem really is a bug in WS 6.
But a revert sureis worth a try.
Hi,
I have tried this and it does not work either ....
Clement Ajaegbu
Solutions Architect
Strategy Architecture & Technical Solutions
Integrated Supply & Trading
20 Canada Square
Canary Wharf
London E14 5NJ
eMail:Clement.Ajaegbu@uk.bp.com
Tel: +44207 948 3337
BP Oil International Limited, a company registered in England and Wales
with the company number 322365 and VAT Number GB 243 5105 93 and whose
registered office is Chertsey Road, Sunbury on Thames, Middlesex, TW16
7BP. BP Oil International Limited is a company regulated by the
Financial Services Authority.
This message may contain information that is privileged or confidential.
If you are not the intended recipient please destroy it and inform the
sender immediately.
There is a LOT of info on the web (and in the vmware communities) about
these locking issues and they only arose in version 6. I would
definitely call that a bug.
Clement Ajaegbu
Solutions Architect
Strategy Architecture & Technical Solutions
Integrated Supply & Trading
20 Canada Square
Canary Wharf
London E14 5NJ
eMail:Clement.Ajaegbu@uk.bp.com
Tel: +44207 948 3337
BP Oil International Limited, a company registered in England and Wales
with the company number 322365 and VAT Number GB 243 5105 93 and whose
registered office is Chertsey Road, Sunbury on Thames, Middlesex, TW16
7BP. BP Oil International Limited is a company regulated by the
Financial Services Authority.
This message may contain information that is privileged or confidential.
If you are not the intended recipient please destroy it and inform the
sender immediately.