EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Running VMware from SolFS / SolFS File System

Also by EldoS: CallbackFilter
A component to monitor and control disk activity, track file and directory operations (create, read, write, rename etc.), alter file data, encrypt files, create virtual files.
Posted: 03/24/2014 07:02:47
by Simon King (Basic support level)
Joined: 03/24/2014
Posts: 17

I copied a small VM to a SolFS volume. Upon trying to start the VM, I got a generic error about the file system being too small to contain a required file, and the VM would not start.

The perceived file system of a SolFS volume appears to be FAT32. Can this be changed? Is this why the VM operation failed? Has this scenario been used before, effectively?
Posted: 03/24/2014 07:46:05
by Volodymyr Zinin (EldoS Corp.)

Please specify how to reproduce the problem. I.e. whether it's reproducible with any of the SolFS samples, version of Windows, type of SolFS API (C++, Delphi, .NET, etc), SolFS storage characteristics, actions to do.

Posted: 03/24/2014 12:25:32
by Simon King (Basic support level)
Joined: 03/24/2014
Posts: 17

This is the exact error received from VMware:

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.

The file is too large

Cannot open the disk 'T:\Server 2003 R2 x86\Server 2003 R2 x86-000002.vmdk' or one of the snapshot disks it depends on.

Module DiskEarly power on failed.

Failed to start the virtual machine.

OS: Windows 8.1 x64 Professional
Hardware: Surface Pro 2 64 GB

Mounter App: SolFS Mounter demo
Settings: Unchanged from default, with the exception of:

NewStorage.Compression := crZLib;
NewStorage.CompressionLevel := 9;

Added to:

procedure TfrmMain.btnCreateStorageClick(Sender: TObject);

Immediately after the call to:

NewStorage.Logo := frmWizard.mmLogo.Text;

Please let me know how to fix this problem, thank you!
Posted: 03/24/2014 12:27:18
by Simon King (Basic support level)
Joined: 03/24/2014
Posts: 17

Please also note that the size of the SolFS storage file was identical to the size of the uncompressed size of the VM; which is indicative that SolFS is not compressing any of the VM file(s) stored on its own file system.
Posted: 03/25/2014 01:46:49
by Alexander Plas (EldoS Corp.)


What is the size of Server 2003 R2 x86-000002.vmdk file?

In order to compress the files inside the storage use please SetFileCompression method. Just set the compression for the root directory after the storage creation, and all new files will be compressed.

Posted: 03/25/2014 04:33:18
by Volodymyr Zinin (EldoS Corp.)

I have tried to reproduce the problem by creating a variable sized SolFS storage and making there a VMware virtual machine with a preallocated 3Gb disk. The result was - VMware was able to successfully start the virtual machine.
So please describe in details how to reproduce the problem. Or even, if it's possible, give us your SolFS storage file with the VMware image inside.

Posted: 03/25/2014 05:40:37
by Simon King (Basic support level)
Joined: 03/24/2014
Posts: 17

I have provided the directory listing below.

The VMware virtual disk file is set to be dynamically expanding, perhaps you could reproduce the issue with the VMware file set to be dynamically expanding instead of static.

I would also be happy to provide you with TeamViewer access to my local system - the upload for the full VM file may be prohibitively large!

03/25/2014 12:22 PM <DIR> .
03/25/2014 12:22 PM <DIR> ..
02/03/2014 10:06 AM <DIR> caches
03/25/2014 02:01 AM 5,308,416 Server 2003 R2 x86-000002.vmdk
02/04/2014 06:17 AM 32,096 Server 2003 R2 x86-Snapshot1.vmsn
03/25/2014 02:01 AM 8,684 Server 2003 R2 x86.nvram
02/04/2014 06:17 AM 2,035,220,480 Server 2003 R2 x86.vmdk
03/25/2014 02:01 AM 519 Server 2003 R2 x86.vmsd
03/25/2014 02:01 AM 3,006 Server 2003 R2 x86.vmx
03/25/2014 02:01 AM 3,938 Server 2003 R2 x86.vmxf
03/24/2014 07:26 PM 176,036 vmware-0.log
03/21/2014 08:05 PM 219,032 vmware-1.log
03/19/2014 02:51 AM 197,151 vmware-2.log
03/25/2014 02:01 AM 190,057 vmware.log
03/25/2014 02:01 AM 62,627 vprintproxy.log
12 File(s) 2,041,422,042 bytes
3 Dir(s) 2,685,640,704 bytes free

I will now try again with compression enabled on SolFS per your instructions.
Posted: 03/25/2014 06:05:31
by Alexander Plas (EldoS Corp.)

Is the storage file variable or fixed size?
Posted: 03/25/2014 07:23:06
by Volodymyr Zinin (EldoS Corp.)

I have reproduced the problem. Please wait a little while I'm investigating it.
Posted: 03/25/2014 08:35:26
by Alexander Plas (EldoS Corp.)

Let me explain the root of the problem. SolFS driver reports our volumes as FAT32 formatted. We can't report it as NTFS formatted, since all the features of NTFS are not implemented in SolFS. Actually, it is impossible to implement all the features of NTFS without deep integration with OS.

FAT32 file system doesn't allow files larger then 2 GB, when SolFS allows. Usually, applications doesn't check the type of file system. It looks like VMWare checks it. I think you can try to use "Split virtual disk into multiple files" feature in VMWare, it splits virtual disk image into 2 GB files.
Also by EldoS: Callback File System
Create virtual file systems and disks, expose and manage remote data as if they were files on the local disk.



Topic viewed 6931 times

Number of guests: 1, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!