I was using VMWare Player (1.0.3) with no problems (host is XP SP2, target is Vista). I upgraded to VMWare Player 2.0.0 build-45731, and I get this error:
Jun 14 12:32:13.020: vmx| DISK: OPEN scsi0:0 '\\xphampton\c$\MyVirtualMachines\Vista\Windows Vista (experimental).vmdk' persistent R[(null)]
Jun 14 12:32:13.098: vmx| DISKLIB-SPARSE: "\\xphampton\c$\MyVirtualMachines\Vista\Windows Vista (experimental).vmdk" : failed to open (36872): Underlying file system does not support files that large.
Jun 14 12:32:13.098: vmx| DISKLIB-DSCPTR: Failed to open extents for embedded descriptor file in normal mode
Jun 14 12:32:13.098: vmx| DISKLIB-LINK : "\\xphampton\c$\MyVirtualMachines\Vista\Windows Vista (experimental).vmdk" : failed to open (The file is too large).
Jun 14 12:32:13.098: vmx| DISKLIB-CHAIN : "\\xphampton\c$\MyVirtualMachines\Vista\Windows Vista (experimental).vmdk" : failed to open (The file is too large).
Jun 14 12:32:13.098: vmx| DISKLIB-LIB : Failed to open '\\xphampton\c$\MyVirtualMachines\Vista\Windows Vista (experimental).vmdk' with flags 0xa (The file is too large).
Jun 14 12:32:13.098: vmx| Msg_Post: Error
Jun 14 12:32:13.098: vmx| [msg.disklib.tooBigForFS] VMware Workstation cannot open one of the virtual disks needed by this VM because it is larger than the maximum file size supported by the host file system. Some remote file systems do not support files larger than 2 GB, even though the file system on the server might.
Jun 14 12:32:13.098: vmx| [msg.disk.noBackEnd] Cannot open the disk '\\xphampton\c$\MyVirtualMachines\Vista\Windows Vista (experimental).vmdk' or one of the snapshot disks it depends on.
Jun 14 12:32:13.098: vmx| [msg.disk.configureDiskError] Reason: The file is too large.----------------------------------------
Jun 14 12:32:57.259: vmx| Module DiskEarly power on failed.
It wasn't too large for 1.0.3, so why does 2.0.0 complain? File system is NTFS.
Jun 14 12:32:13.020: vmx| DISK: OPEN scsi0:0 '\\xphampton\c$\MyVirtualMachines\Vista\Windows Vista (experimental).vmdk' persistent R[(null)]
Jun 14 12:32:13.098: vmx| DISKLIB-SPARSE: "\\xphampton\c$\MyVirtualMachines\Vista\Windows Vista (experimental).vmdk" : failed to open (36872): Underlying file system does not support files that large.
Jun 14 12:32:13.098: vmx| DISKLIB-DSCPTR: Failed to open extents for embedded descriptor file in normal mode
Jun 14 12:32:13.098: vmx| DISKLIB-LINK : "\\xphampton\c$\MyVirtualMachines\Vista\Windows Vista (experimental).vmdk" : failed to open (The file is too large).
Jun 14 12:32:13.098: vmx| DISKLIB-CHAIN : "\\xphampton\c$\MyVirtualMachines\Vista\Windows Vista (experimental).vmdk" : failed to open (The file is too large).
Jun 14 12:32:13.098: vmx| DISKLIB-LIB : Failed to open '\\xphampton\c$\MyVirtualMachines\Vista\Windows Vista (experimental).vmdk' with flags 0xa (The file is too large).
Jun 14 12:32:13.098: vmx| Msg_Post: Error
Jun 14 12:32:13.098: vmx| [msg.disklib.tooBigForFS] VMware Workstation cannot open one of the virtual disks needed by this VM because it is larger than the maximum file size supported by the host file system. Some remote file systems do not support files larger than 2 GB, even though the file system on the server might.
Jun 14 12:32:13.098: vmx| [msg.disk.noBackEnd] Cannot open the disk '\\xphampton\c$\MyVirtualMachines\Vista\Windows Vista (experimental).vmdk' or one of the snapshot disks it depends on.
Jun 14 12:32:13.098: vmx| [msg.disk.configureDiskError] Reason: The file is too large.----------------------------------------
Jun 14 12:32:57.259: vmx| Module DiskEarly power on failed.
It wasn't too large for 1.0.3, so why does 2.0.0 complain? File system is NTFS.
