Virtual machine crashes unexpectedly with the error message "There is no more space for virtual disk"

[abdullahyildiz]

Hi,

This issue started to appear since a couple of days. We get the following error message:

2025-06-24T11:38:14.956Z In(05) vmx - [msg.hbacommon.outofspace] There is no more space for virtual disk 'server.vmdk'. You might be able to continue this session by freeing disk space on the relevant volume, and clicking _Retry. Click Cancel to terminate this session.

The VM is hosted on the datastore available in the physical machine and there is plenty of free disk space available (when the VM is powered off):

There are also other VMs running on the other datastore and we don't have this issue for other VMs. Datastores (both are located in the physical machine) are used as in the following scheme:

- datastore 1

VM1

VM2

- datastore 2

VM that is crashing

We didn't expect this as the VM has been running for couple of months without any issue. We also do not have any clue at the moment regarding what has caused this. There is also an article regarding this and but the suggested remedies seem to be not applicable in our case.

I share below the screenshots that belong to the respective VM configuration:

[janatlud]

Hello,

because the disk is THIN provisioned, the disk can grow, what is exactly not possible, when on datastore is available only 512 GB storage. This capacity is probably used for SWAP file, which is created always, when VM is started, and it has the same size as allocated memory. If you want to reduce SWAP file size, set Memory reservation. For the reserved memory is not needed to create so swap file (exactly the swap file size will be 512 GB minus reserved RAM. Or possibly you can check, what is default storage policy for the datastore, to enforce the SWAP file also in thin provisioning.

Please try to reserve some memory, change storage policy, to move swap file location to another storage.

The datastore capacity can be also problematic with active snapshot on VM.

BR

janatlud

[abdullahyildiz]

Hi @janatlud,

Thanks a lot for your support and sharing your feedback. We reserved a memory of 512GB for the VM, and now the resource utilization is as follows while the VM is up and running: