I had a Windows 2003 VM running on an Ubuntu host that died on me. I'm now trying to boot up that VM on another Ubuntu machine running the same version of VMware Server 1.0.7 and I keep getting ...
Sep 01 21:04:44: vmx| DISK: OPEN scsi0:2 '/data/vm/windoze_2003/Windows Server 2003 Enterprise Edition.vmdk' independent-persistent R[(null)]
Sep 01 21:04:44: vmx| FILEIO: Failed to get a lock for file '/data/vm/windoze_2003/Windows Server 2003 Enterprise Edition.vmdk'.
Sep 01 21:04:44: vmx| DISKLIB-LINK : "/data/vm/windoze_2003/Windows Server 2003 Enterprise Edition.vmdk" : failed to open (Failed to lock the file).
Sep 01 21:04:44: vmx| DISKLIB-CHAIN : "/data/vm/windoze_2003/Windows Server 2003 Enterprise Edition.vmdk" : failed to open (Failed to lock the file).
Sep 01 21:04:44: vmx| DISKLIB-LIB : Failed to open '/data/vm/windoze_2003/Windows Server 2003 Enterprise Edition.vmdk' with flags 0xa (Failed to lock the file).
Sep 01 21:04:44: vmx| DISK: Cannot open disk "/data/vm/windoze_2003/Windows Server 2003 Enterprise Edition.vmdk": Failed to lock the file (16392).
Sep 01 21:04:44: vmx| DISK: Failed to open disk '/data/vm/windoze_2003/Windows Server 2003 Enterprise Edition.vmdk' : Failed to lock the file (16392) 3023.
Sep 01 21:04:44: vmx| Msg_Post: Error
Sep 01 21:04:44: vmx| http://msg.disk.noBackEnd Cannot open the disk '/data/vm/windoze_2003/Windows Server 2003 Enterprise Edition.vmdk' or one of the snapshot disks it depends on.
I'm starting vmware as root and this is my directory ...
root@christa-desktop:/data/vm/windoze_2003# ls -al
total 16350952
drwxrwxrwx 2 root root 4096 2008-09-01 11:54 .
drwxrwxrwt 3 root root 4096 2008-09-01 06:36 ..
-rwxrwxrwx 1 root root 1073741824 2008-08-30 18:58 564d5e7e-6b5b-9824-d033-9570f9dbd141.vmem
-rwxrwxrwx 1 root root 1073741824 2008-08-30 18:38 564dce1d-fd27-3f6e-7872-281952681a1e.vmem
-rwxrwxrwx 1 root root 8684 2008-08-30 18:34 nvram
-rw-rr 1 root root 28815 2008-09-01 07:18 vmware-0.log
-rw-rr 1 root root 28815 2008-09-01 07:06 vmware-1.log
-rwxrwxrwx 1 root root 28815 2008-09-01 07:02 vmware-2.log
-rw-rr 1 root root 21867 2008-09-01 11:53 vmware.log
-rwxrwxrwx 1 root root 2145058816 2008-09-01 11:53 Windows Server 2003 Enterprise Edition-0-s001.vmdk
-rwxrwxrwx 1 root root 560988160 2008-09-01 11:53 Windows Server 2003 Enterprise Edition-0-s002.vmdk
-rwxrwxrwx 1 root root 804323328 2008-09-01 11:53 Windows Server 2003 Enterprise Edition-0-s003.vmdk
-rwxrwxrwx 1 root root 327680 2008-09-01 11:53 Windows Server 2003 Enterprise Edition-0-s004.vmdk
-rwxrwxrwx 1 root root 327680 2008-09-01 11:53 Windows Server 2003 Enterprise Edition-0-s005.vmdk
-rwxrwxrwx 1 root root 1048576 2008-09-01 11:53 Windows Server 2003 Enterprise Edition-0-s006.vmdk
-rwxrwxrwx 1 root root 742 2008-08-30 18:38 Windows Server 2003 Enterprise Edition-0.vmdk
-rwxrwxrwx 1 root root 2147221504 2008-08-30 18:30 Windows Server 2003 Enterprise Edition-f001.vmdk
-rwxrwxrwx 1 root root 2147221504 2008-08-30 18:32 Windows Server 2003 Enterprise Edition-f002.vmdk
-rwxrwxrwx 1 root root 2147221504 2008-08-30 18:34 Windows Server 2003 Enterprise Edition-f003.vmdk
-rwxrwxrwx 1 root root 2147221504 2008-08-30 18:36 Windows Server 2003 Enterprise Edition-f004.vmdk
-rwxrwxrwx 1 root root 2147221504 2008-08-30 18:38 Windows Server 2003 Enterprise Edition-f005.vmdk
-rwxrwxrwx 1 root root 1310720 2008-08-30 18:38 Windows Server 2003 Enterprise Edition-f006.vmdk
-rwxrwxrwx 1 root root 903 2008-08-30 18:38 Windows Server 2003 Enterprise Edition.vmdk
-rwxrwxrwx 1 root root 1073741824 2008-08-30 18:43 Windows Server 2003 Enterprise Edition.vmem
-rwxrwxrwx 1 root root 0 2008-08-30 18:38 Windows Server 2003 Enterprise Edition.vmsd
-rwxrwxrwx 1 root root 1107187 2008-08-30 18:45 Windows Server 2003 Enterprise Edition.vmss
-rwxrwxrwx 1 root root 2133 2008-09-01 11:53 Windows Server 2003 Enterprise Edition.vmx
-rwxrwxrwx 1 root root 293 2008-08-30 18:38 Windows Server 2003 Enterprise Edition.vmxf
There are no lock files and I even set the file perms to 777 in desperation. VMware Server 2.0 rc2 is telling me the same thing. I don't see anything in the vmx or vmdk file indicative of an absolute path that might be bad.