The vmx-10 Paradox

vmx-10 paradox

 

 

Since the introduction of vmx-10 there has been a lot of debate on whether to use it or not.
The  main shortcoming is that one cannot edit the settings of a Virtual Machine that is running on VM hardware version 10 (vmx-10) using the vSphere client.
It can only be done using the web client, so if you are running just an ESXi server and you have a VM with vmx-10, you are in trouble.

 

Also, I realized that even when you have a vCenter server, if its installed on a VM that is running with vmx-10 you will still get into trouble.
It could all start with something simple, like the vCenter going down because the  C:\ drive is full and thus the service does not start. Which is exactly what happened in my case!

 

Now the vCenter is down, and I need to add space to the C drive, by editing it,  but the vCenter is down and so is the web client.
I could login into the ESXi host that is hosting the vCenter server to make any changes, but again I would need the web client. This brings us back to square one.

 

I racked my brains for a while about this and then thought of trying this, using the vmkfstools.
So I logged into my host and powered off my vCenter server ( the service was not running anyway), located the server under /vmfs/volumes///

Warning : Do not extend a disk that has snapshots. Commit or discard snapshots before increasing the size of the virtual disk. Extending the size of a virtual disk that has snapshots invalidates the snapshots.

The command that came in handy to extend the disk space was

vmkfstools -X 60G /vmfs/volumes/datastore/vcenter-server/vcenter-server.vmdk

This extended  the disk and gave some space to the C drive, so it could do what it does and get the vCenter service up and running.

This got me thinking, what if the same thing happens because of other resources like RAM and CPU?

That is when I stumbled upon a KB Article that tells you how to make these changes using PowerCLI commands when you don’t have a web client in your environment or when its down.

 

To conclude :

If you do not have a need to run your vCenter server on vmx-10 then avoid it until VMware changes the architecture and the way the machine settings are edited in higher versions of VM hardware. If you need to run the vCenter VM with vmx-10 then keep the KB Article handy as it will help you perform these operations on the VM directly using powercli cmdlets.

Note:

Take a backup of the vCenter server before you do any of these tasks.

UPDATE : With the release of 5.5U2, you can edit VMX-10 using C# clients. VMware finally realized it.

 

 

5,334 total views, 4 views today

Abhilash B

Abhilash is a wannabe geek who tries his hand at everything interesting. Partial DevOps guy, a little bit of SEO nerd and a VMware vExpert. Cloud consultant by day. Blogger by night. A virtualization lover who is recognized as #PernixPro and a #CiscoChampion for his contributions at VMTN community and here at vPirate.in.

8 thoughts on “The vmx-10 Paradox

  • July 15, 2014 at 4:58 pm
    Permalink

    Hi! Can you please post the link to the KB aricle?

    Reply
  • July 16, 2014 at 12:24 am
    Permalink

    How did you manage to increase the partition size after increasing the disk size to 60G?

    Reply
  • July 16, 2014 at 12:52 am
    Permalink

    Hi Koray,
    I powered the machine back on, re-scanned for free space and extended the partition.

    Reply
    • July 19, 2014 at 11:26 am
      Permalink

      Oh of course.. You cannot edit VM settings but you can open console via a client connection to ESXi. Good hint, thx

      Reply
      • July 19, 2014 at 11:52 am
        Permalink

        Since it’s a windows box you can just RDP into it and extend it after its up.

        Reply
  • July 23, 2014 at 5:32 am
    Permalink

    I’m confused why you didn’t just log into the vCenter VM directly and clean up the disk before going through all the gyrations of using vmkfstools.

    Reply
    • July 23, 2014 at 8:45 am
      Permalink

      We tried cleaning up the disk but we did not find any space that could be reclaimed. The whole problem started because the vCenter machines were given less space to start with. Now we have increased our standard size to a bigger drive for vCenter servers.

      Reply

Leave a Reply