This error seems bizarre especially when you are actually trying to increase the guest RAM and the error is about disk space. The cause could be the following:
- By default, ESX will configure a swap on the VM's datastore equal to the RAM. So, when RAM is increased, more disk space is required. The fix is to reserve memory in resource allocation settings for the VM.
- There really isn't enough disk space on the datastore. Reduce Hard Disk size for the VM.
Please leave a comment if this post helped you, or if you find something else that fixed your problem. Thanks!
ReplyDeleteThis post has been one of the most popular posts on this blog. What people are searching leading them to this post? Some of the popular search strings have been:
ReplyDelete[1] could not power on vm no space left on device (40%)
[2] failed to power on vm no space left on device (26%)
[3] could not power on vm : no space left on device. (19%)
[4] failed to power on vm could not power on vm : no space left on device (15%)
Thank you! Why is this necessary? Most of my vm's do not have a reservation, yet they are happy...
ReplyDeleteThanks for your comment Mark. This post specifically targets the "No space left on device" error when trying to increase the RAM of your existing VM. With this error you have 2 solutions, to rebuild your VM, or to reserve memory. By reserving memory, when RAM is increased, ESX does not require any extra disk space for swap.
DeleteIn short, memory reservation is not necessary, but helpful if you want to increase RAM of an existing VM and you do not want the VM (swap) to use more of your valuable disk space.
Yes, I am strongly agreed with you, please keep writing like this.
ReplyDeleteI read your article and got impressed due to have a positive ipression, many people would like to read about tech 4 technology because you have made an effort to write perfectly, please keep it up!
ReplyDelete