i have this in the vmware.log of a windows xp guest:
Jan 08 20:06:18: vmx| DISK: OPEN ide0:0 '/opt/raid0/VirtualMachines/europa/Windows XP Professional.vmdk' persistent R\[(null)]
Jan 08 20:06:18: vmx| FILEIO: Failed to get a lock for file '/opt/raid0/VirtualMachines/europa/Windows XP Professional.vmdk'.
Jan 08 20:06:18: vmx| DISKLIB-LINK : "/opt/raid0/VirtualMachines/europa/Windows XP Professional.vmdk" : failed to open (Failed to lock the file).
Jan 08 20:06:18: vmx| DISKLIB-CHAIN : "/opt/raid0/VirtualMachines/europa/Windows XP Professional.vmdk" : failed to open (Failed to lock the file).
Jan 08 20:06:18: vmx| DISKLIB-LIB : Failed to open '/opt/raid0/VirtualMachines/europa/Windows XP Professional.vmdk' with flags 0xa (Failed to lock the file).
Jan 08 20:06:18: vmx| DISK: Cannot open disk "/opt/raid0/VirtualMachines/europa/Windows XP Professional.vmdk": Failed to lock the file (16392).
Jan 08 20:06:18: vmx| DISK: Failed to open disk '/opt/raid0/VirtualMachines/europa/Windows XP Professional.vmdk' : Failed to lock the file (16392) 3023.
Jan 08 20:06:18: vmx| Msg_Post: Error
Jan 08 20:06:18: vmx| \[msg.disk.noBackEnd] Cannot open the disk '/opt/raid0/VirtualMachines/europa/Windows XP Professional.vmdk' or one of the snapshot disks it depends on.
Jan 08 20:06:18: vmx| \[msg.disk.configureDiskError] Reason: Failed to lock the file.----
Jan 08 20:06:18: vmx| POST(no connection): Cannot open the disk '/opt/raid0/VirtualMachines/europa/Windows XP Professional.vmdk' or one of the snapshot disks it depends on.
Jan 08 20:06:18: vmx| Reason: Failed to lock the file.
Jan 08 20:06:18: vmx| Module DiskEarly power on failed.
Jan 08 20:06:18: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0
Jan 08 20:06:18: vmx| VMX idle exit
Jan 08 20:06:18: vmx| Flushing VMX VMDB connections
Jan 08 20:06:18: vmx| IPC_exit: disconnecting all threads
Jan 08 20:06:18: vmx| VMX exit.
Jan 08 20:06:18: vmx| AIOMGR-S : stat o=9 r=3 w=0 i=0 br=1710 bw=0
this is the current file list in its directory:
jhorne@polaris:/opt/raid0/VirtualMachines/europa> ls
564d5f48-47e1-9a43-eb50-a2b39527ebde.vmem nvram vmware-
564d5f48-47e1-9a43-eb50-a2b39527ebde.vmem.WRITELOCK QuickBooks2007.iso vmware.
564d80db-b1b7-7035-71a5-7583c4df4294.vmem vmware-0.log Windows
564d80db-b1b7-7035-71a5-7583c4df4294.vmem.WRITELOCK vmware-1.log Windows
jhorne@polaris:/opt/raid0/VirtualMachines/europa> ls
564d5f48-47e1-9a43-eb50-a2b39527ebde.vmem
564d5f48-47e1-9a43-eb50-a2b39527ebde.vmem.WRITELOCK
564d80db-b1b7-7035-71a5-7583c4df4294.vmem
564d80db-b1b7-7035-71a5-7583c4df4294.vmem.WRITELOCK
nvram
QuickBooks2007.iso
vmware-0.log
vmware-1.log
vmware-2.log
vmware.log
Windows XP Professional-f001.vmdk
Windows XP Professional-f002.vmdk
Windows XP Professional-f003.vmdk
Windows XP Professional-f004.vmdk
Windows XP Professional-f005.vmdk
Windows XP Professional-f006.vmdk
Windows XP Professional-f007.vmdk
Windows XP Professional.vmdk
Windows XP Professional.vmdk.WRITELOCK
Windows XP Professional.vmsd
Windows XP Professional.vmx
is there a way out of this? i do have a backup of the entire VM, but i would like to not pull that out if i can avoid it.