Help:

[daphnissov]

What client are you using to create these disks? Also, what does this have to do with hands-on-labs?

[lchuakc]

I am using the web client. I placed it in the labs because most people here are probably playing around with the systems alot. Where should I place this topic in?

[daphnissov]

This should go in vSphere. Are you using the ESXi host (web) client or vCenter Server web (Flex) client?

[lchuakc]

I am using VCSA 6.5 web client.

Can we still use standard windows client for vsphere 6.5?

Can moderator help to move my topic to the Vsphere forum? Thanks.

[daphnissov]

You cannot use the legacy Windows-based thick/fat/C# client in vSphere 6.5 as of Update 1.

The datastore on which you're creating this disk, what type is it? Feel free to show screenshots of your work.

[DougBaer]

This forum is for the VMware Hands-on Labs, which are available at http://labs.hol.vmware.com/

There are other forums available for questions about "ESXi" (ESXi ) and "vSphere Hypervisor," (vSphere Hypervisor ) which would be more appropriate for this type of question I think.

That said, I have not had this issue in using vSphere 6.5 for several years.

I went through our lab, HOL-1810, and created a new VM on the iSCSI datastore using the HTML5 client. The first disk, I made 2 GB Thick and the second a 1 GB EZT.

Executing the PowerCLI commands, I was able to see how the disks actually report their configuration:

Connect-VIServer vcsa-01a

Get-VM MyNewVM | Get-HardDisk | Select Name,StorageFormat

This showed my disks with a storage format of Thick and EagerZeroedThick respectively.

[DougBaer]

This is where I would focus your attention. I am not completely familiar with how Nutanix configures storage, but the type of the datastore and any SPBM policies attached could affect the behavior of your created VMDKs.

[rcporto · Accepted solution]

I think you're experiencing that issue: Heads Up! ESXi cannot distinguish between EagerZeroedThick & LazyZeroedThick - CormacHogan.com

[lchuakc]

Thanks Everyone for helping.

I think Richardson solved the mystery. I guess Eager Zero should be fine so long the disk is running on Lazy Zero in the background.

Thank you everyone.