Maximum size of VMDK file for vSphere & provision of a 1TB VM ?

[TonyJK]

From the what's new feature, I find that we can assign 256GB RAM and 8 vCPU to a VM for vSphere. However, we would like to know the maximum size of VMDK file ? Is it still 256GB ?

The Server Administrator asks for providing him a File Server of size around 1TB. Would it be a good idea to use the precious SAN for it ? Would it be better to use a standalone physical machine or use the internal SCSI HD (VMFS) of one of the ESX Hosts in the cluster ?

Your advice is sought

[lamw]

If you take a look at the configuration maximum for vSphere: http://www.vmware.com/pdf/vsphere4/r40/vsp_40_config_max.pdf you'll note that the maximum disk size for a VM is 2TB - 512bytes, also the maximum VMFS volume size with 8MB block. vMemory for a VM is actually 255gb and not 256gb, this is due to some state information that is roughly ~400mb and the value of the maximum is rounded down to be safe and more details can be found here: http://www.yellow-bricks.com/2009/05/12/255gb-memory-limit-for-vms-with-vsphere/

Also if you take a look at the 'whats new feature' section, it does reference 255gb and not 256gb for a VMs memory: http://www.vmware.com/support/vsphere4/doc/vsp_40_new_feat.html

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at:

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

[TomHowarth]

firstly Max Mem is 255GB, but max disksize depends on your VMFS block size.

1MB block size = Max VMDK 256GB

2MB block size = Max VMDK 512GB

4MB block size = Max VMDK 1024GB

8MB block size = Max VMDK 2048GB-512bytes

Block size is set a VMFS formating stage. it is now considered best practice to format your LUNs with 8MB blocks as this will allow easy expansion if you need to grow your LUN sizes.

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "[VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment|http://my.safaribooksonline.com/9780136083214]”. Currently available on roughcuts

[TonyJK]

Thanks for both of your advice.

Does the 8MB Block Size parameter also apply to ESX 3.5 or just for vSphere ? Besides, at the present moment, I find that the existing ESX Hosts have block size of 1MB and File System = VMFS 3.31.

I believe that not much we can do for the existing ESX Host. However, we are going to add a new ESX host to our cluster before the end of this calendar year, will there be any potential problem if we choose block size = 8MB for it ?

Thanking you in anticpation.

[TomHowarth]

this block size has been inplace since the release of VI3. however a VMFS partition that is created during installation will always be created with the default 1MB block size. this will mean that you will never be able to create a VMDK of a size greater that 256GB. to get greater block sizes consider VMFS creation post installion (just remove the VMFS partion for the partition table during installation) and use either the VIC to create the datastore or via the command line with vmsftools command.

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "[VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment|http://my.safaribooksonline.com/9780136083214]”. Currently available on roughcuts

[TonyJK]

Dear Tom,

From your reply, my understanding is that we cannot change the block size (like 8MB) when we create a new partition. The only way is to reformat the partition with command like: vmkfstools --createfs vmfs3 --blocksize 8M vmhba0:0:0:3

Is my understanding correct ?

Thanks

[TomHowarth]

That is correct, you can also do it from the VI Client as well, if you are uncomfortable with the command line. but a reformat is necessary yes.

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "[VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment|http://my.safaribooksonline.com/9780136083214]”. Currently available on roughcuts

[TonyJK]

Dear Tom,

Would it be possible to show me how to do the change in VI Client ?

Thanks