VMware Cloud Community
Marko55
Contributor
Contributor

The disk capacity specified is greater than the amount available in the datastore. Disk space overcommitment can consume all space in the virtual disk and block the virtual machine. Increase the datastore capacity before proceeding or enter a smaller disk

I'm running ESXi 6.0u2 free.  I've got a 54TB datastore on DAS to an LSI SAS3 controller (9380-4i4e).  After setting everything up, including a Server 2012 R2 standard VM, I was able to create a 30TB VMDK for the server, though I had to use the web client to do it (the fat client seems to only allow 16TB max). 

At some point I lost the ability to edit ANY settings on that VM (memory, CPU, disk, etc) and it throws the error in the subject line.  Again, even if I'm trying to change a non-disk-related setting.  I removed (and deleted) the entire datastore and recreated it from scratch and I'm having the same issue.  In the web client it even shows it has 54TB free/available.

I've also got a Windows 7 x64 pro and a Windows 10 x64 pro VM running and I'm having the same problem with editing their settings in the web client as well.  I was having no issues earlier today however.  I did find that I was able to create a new virtual disk of 16TB on the Windows 7 VM using the vSphere client, even though it appeared to throw an error it still worked.  Problem is it appears you need the web client to do anything over 16TB which is what I need to do and its basically unusable at this point.

Note that I can still edit VM settings using the vSphere client as normal.  I just can't edit settings on ANY VMs using the web client?  I already tried the "Reset client settings" in the web client; didn't help.


I've seen only a couple other folks online that have run in to this and I see no fix.  I'm trying to backtrack my steps and the last thing I was doing was messing around with MTU settings on my vSwitch in the web client.  This definitely feels like a bug but I'm not sure how to proceed!  Maybe there's some way to completely reset/reinstall the web client?

Reply
0 Kudos
9 Replies
virtualg_uk
Leadership
Leadership

What was the error that was getting thrown and what tasks were you completing when the error occurred?


Graham | User Moderator | https://virtualg.uk
Reply
0 Kudos
rgaasenb
Contributor
Contributor

This is a bug I encountered (and reported) in the web client. When editing a VM, it incorrectly checks to see whether the datastore your current VM disks reside on have enough space to fit the virtual hard disks already assigned to them. Example:

Your data store is 100GB

Your VM's HDD is 70 GB, so 30 GB free

You edit the VM, it throws this error as it checks to see whether there is enough space on the datastore to fit *another* 70GB which is nonsense as the 70GB is already committed to this VM.

This is a really annoying bug, and while you won't encounter it with the Vsphere client, this doesn't help you as certain settings of your VM you can only edit with the web client.

The only workaround is making sure you don't create any virtual disk on a VM (first or second!) that is greater than the free space available on your datastore.

colinjrob
Contributor
Contributor

No remedy in sight though. I wanted to change my CD/DVD from using an image to using the device on the hosting server. Every time I go to save I get that message. I guessed that was what it was doing, trying to set up the drive again but it's madness. What is the remedy - an update?

Reply
0 Kudos
continuum
Immortal
Immortal

When I get this message I power off the VM, unregister it and make the change manually by editing the vmx-file and reregister the VM.
Thats inconvenient but ir works.


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
illizit
Contributor
Contributor

I've had this issue for about two years and I've been working around it as you suggested. I can't believe that this issue is still around, how is it possible there is no bug report or update to fix this issue? I just patched vcenter to the latest version thinking surely it was included in the April updates to no avail. Incredibly disappointing.

Reply
0 Kudos
continuum
Immortal
Immortal

There are lots of function that are not really reliable / trustworthy via the webinterface.

If you value your mental health I recommend to get used to:
1. doing all your VM edits that are potentially dangerous or destructive via edit of vmx-files or commandline
2. assume that flaws in the webinterface will be fixed before you get married

Thats what I do - it definetely safes time often.


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
SinanCaliskan
Contributor
Contributor

Mouse right click amd Inspect on Cancel Save button's "Save" when its Green after entering Edit Settings menu of VM before click "Add Hard Disk" .

Copy this line below :

<button type="button" ng-click="vuiDialog.onOk()" ng-disabled="vuiDialog.confirmOptions.disabled" data-test-id="dialog-footer-action-confirm" class="btn-primary">Save</button>

Then Add Hard Disk and configure it , you will see grayed Save.

Then Mouse Right click again and paste, copied "<button...." line on Grayed buton html instead.

And you will see green Save button and press to add disk to VM.

It works for me

😄 

Reply
0 Kudos
MCastelein
Contributor
Contributor

Need to describe this better, I'm not getting a green button

Reply
0 Kudos
vitsupport
Contributor
Contributor

Hi, @continuum  I bumped into this problem on a customers old installation now. Could you please explain what you edited in the vmx-file to overcome this? Can't for the bare life of me find a way to add a USB-device to a VM without the use of the Web GUI...

Reply
0 Kudos