Understanding ESX Licensing

To help myself keep track of licensing I created a licensing script on my VM Scripting Blog. However I now and again get caught in the confusion as my license numbers don't always match up to what I expect. So this is here to remind me and hopefully help others.

License Types:

• VirtualCenter Management Server - VC Server license. Typically only one is listed here.
• ESX Server Standard - Used when licensing server is defined and set as a Standard ESX Host
• VCB Consolidated Backup or ESX_FULL_BACKUP - Assigned on a per server basis for VCB.
• VirtualCenter Agent for ESX Server - Used when added to Virtual Center
• VMotion - Used when added to a cluster that uses VMotion
• VMware HA - Used When Added to a Cluster that has HA Enabled
• VMware DRS - Used When Added to a Cluster that has DRS Enabled

Note: If a server is using an ESX Server Standard license but not in VirtualCenter, add it back into VirtualCenter temporarily and Unlicense the host. The opposite happens as well. If a server is using a VirtualCenter Agent for ESX Server license, but not an ESX Server Standard license, it is due to the server being visible in VirtualCenter but in an Unlicensed state.

HP's VMM

HP's VMM is junk. I like the idea and concept to a point. The reporting is really decent. What they fail to do however is provide a stable agent and decent licensing.

First, the VMM agent will actually lock the VMDK file. This means that if a snapshot is applied back into the main VMDK, there is a possibility that the VM will shutdown to complete the reapplication.

The licensing is also poor. HP has deemed that the VMM license is tied to the hardware. If you rebuild the system, it may actually lose licensing.

I worked with HP on these issues for over a month and they were unwilling to change their stance on the licensing and couldn't figure out the locking issue. I would avoid purchasing or using VMM agents until they straighten it out.

P2V Issues

A couple of things I noticed when doing a P2V that I thought were odd and could potentially cause performance issues.

• Hidden Devices - Neither Platespin nor VMWare Converter remove non present devices. They linger on on the VM. These lingering devices can cause performance issues as well as networking issues. To remove the hidden or non-present devices, go to a command prompt and type "set DEVMGR_SHOW_NONPRESENT_DEVICES=1" then from the same command prompt type "devmgmt.msc". This will bring up a device manager window. From there go into each section and delete all greyed out devices. One network controller that is greyed out won't delete.
• Assigning Multiple CPU - If the physical box that the VM started from had at least 4 cores, VM Converter assigns 4 vCPUs. Platespin at least allows control over this. 4 vCPUs can potentially cause a high CPU Ready and hurt the performance of all VMs on the server.
• Installed Programs - Installed programs and drivers that show up under Add/Remove Programs after a conversion. ATI driver wont uninstall without a registry hack or uninstaller. Remove all vendor specific drivers after that.

That should clean up the VM so it is running smoothly.

ESX Partitioning

I have changed the default partitioning of an ESX host.

# Partitioning
part /boot --fstype ext3 --size 200 --ondisk cciss/c0d0
Note: This was increased from original size of 110. ESX 3.0.1 had a default of 94 so when I updated to ESX 3.0.2 U1 I had errors saying the boot partition is too small. I was forced to rebuild rather than upgrade. I decided on future builds to increase this to allow for easier upgrades.
part / --fstype ext3 --size 4997 --ondisk cciss/c0d0
Note: I kept this one the same.
part swap --size 1600 --ondisk cciss/c0d0
Note: I set this partition to 2 times the maximum memory allocated to the service console (800 MB x 2 = 1600 MB)
#part None --fstype vmfs3 --size 10000 --grow --ondisk cciss/c0d0
Note: I removed the local storage for the time being, so as to prevent other admins from accidentally creating VMs on the local storage
part None --fstype vmkcore --size 110 --ondisk cciss/c0d0
Note: I kept this one the same.
part /var/log --fstype ext3 --size 1992 --ondisk cciss/c0d0
Note: I kept this one the same.

Adding a user during ESX Kickstart

Password Hash:
openssl passwd -1 <password>

Patrol Environment:
Kickstart
%post
echo -n "Adding user..."
useradd <options> <new user>
usermod -p '<password>' <new user>
Note: Include password hash in single quotes.

VCP Certified

I passed my VCP301 Exam today with a 91%. I should have done probably higher, but I hurried through the exam. The notes and practice exams were very helpful.

VCP Training Notes

Well, Day 1 Blog 1. I figured this is about as good of place as any to start. I recently went to VMWare VCP training. Here are some notes that stuck out to me.

VCP Notes