Limit IOPs Per VMDK

One of the many features in VMware vSphere, which I didn’t know, is the capability, to limit IOPs per VMDK without setting any limitations on the underlying storage system or for the whole Virtual Machine.


As you can see on the image above, it is easy to limit the IOPs per VMDK within the vSphere web-client.
Just browse to your Virtual Machine and go to edit settings. Select the “Hard drive”, which you would limit on IOPs and expand it.

Note: By default, all VMDKs are set to unlimited IOPs.

Remove VIB – Device or resource busy

Today, I was playing around with some vSphere Installation Bundles (VIB) and ran into an issue when I tried to remove vib:

Even adding the –force attribute did not help in this situation.

The following workaround seemed to be working for me:

  1. Stophostd on theESXi host – this will be non-disruptive to yourVMs
  2. Runlocalcli to uninstallVIB

    Note: We need to run localcli, since esxcli is not available if hostd is stopped
  3. Starthostd on theESXi host
  4. Verify thatvmware-esx-KoraPlugin no longer shows up

You should no longer see the VIB installed on your ESXi host.
Localcli is not widely spread within the community and mainly used by VMware’s Technical Support. It provides more troubleshooting capabilities, even if hostd is not running.



Unmount VMware Datastore – Device Busy

Welcome back, I hope everyone had some time to relax and spend the christmas holidays with their families. I was lucky enough to have some time off and play with my lab.

After playing around with some newly deployed NFS datastores, I tried to unmount them and I got a device busy error and on the CLI I’ve got Sysinfo error on operation returned status : Busy. Please see the VMkernel log for detailed error information.

Let me show you the steps I ran through:

  1. Mounted a newNFSdatastore throughtheESXCLI
  2. List all NFS shares
  3. Verify that all VMs on this datastore are either powered off or have been vMotioned to another datastore
  4. Trytounmountthedatastore
  5. Looking through the vmkernel.log, doesn’thelpmuch either. The only messageprintedthere is
  6. After some searching, I found this article on VMware
  7. Basically, the issue seems to be that vSphere HA Datastore Heartbeats are  enabled on this datastore, which is causing the device to be busy.

The solution for this problem is pretty simple. Open your vSphere Client and edit the vSphere HA settings, after selecting your vSphere HA Cluster. Within the settings, make sure to set the vSphere HA heartbeats to Use Datastores only from the specified list and deselect your datastore, which you try to unmount.

Screen Shot 2015-01-12 at 2.39.42 PM

After changing the setting, I was able to successfully unmount the NFS share with the following command esxcli storage nfs remove -v datastore_name 

VMware Update Manager 5.5 Installation

Last week I started to setup a VUM – VMware vSphere Update Manager 5.5 to get my ESXi hosts updated and some 3rd party software installed. If you have multiple ESXi hosts and you need an easy way to keep your vSphere environment current, VUM is the way to go.

Additionally, VUM plays quiet nicely with DRS (Distributed Resource Scheduler) to avoid any downtime to your VMs, while applying patches to the hosts. DRS will migrate all active VMs from the host  and then put the host into maintenance mode, one at a time.

For the people who do not know where to get VMware Update Manger from, it is part of the VMware vSphere 5.5 ISO. It took me a while to find it. Once you load the ISO you can find the VMware Update Manager under VMware vCenter Support Tools.


The installation is pretty straight forward.

Screen Shot 2014-12-17 at 3.40.27 PM

Once you have launched the installation wizard, click Next and then accept the EUL – End User License Agreement.

Screen Shot 2014-12-17 at 3.40.35 PM

On the next screen, you can select whether you want updates to be automatically downloaded from the default sources after the installation. By default, this option is enabled but can be disabled if you prefer to review the default sources, first.

Screen Shot 2014-12-17 at 3.40.42 PM

Next, you have to specify your vCenter server address, port and credentials in order to register VUM with it.
Note: VCSA – vCenter Server Appliance is also supported since VUM 5.0. However VUM needs to be installed on a Windows Server.

Screen Shot 2014-12-17 at 3.41.04 PM

After you have specified your vCenter credentials, you have to choose if you want to install Microsoft SQL Server 2008 R2 Express instance or to use an already existing database/use a different database type. For smaller vSphere deployments it is ok to use the Microsoft SQL Server. However, if you plan to have more than 5 hosts or 50 VMs, you will be better off with a different database, more information can be found here.

Screen Shot 2014-12-17 at 3.41.12 PM

On the next screen, you can specify whether VUM will be identified by IP address or DNS name. Personally, I always chose IP since VUM would still be accessible even if the DNS server is down. Additionally, you can make changes to the default ports for SOAP, Web and SSL.

Screen Shot 2014-12-17 at 3.41.19 PM

Next, specify the installation folders for the VMware vSphere Update Manager and location for downloading patches.

Note: The patch location should have at least 20 GB free space.

Screen Shot 2014-12-17 at 3.41.31 PM

Now, VUM will start to extract the executable for the Microsoft SQL Server.

Screen Shot 2014-12-17 at 3.41.47 PM

For the actual Microsoft SQL Server installation, you do not need to do anything and it is automated by VUM.

Screen Shot 2014-12-17 at 3.43.08 PM

Last but not least, click Finish to complete the installation.

Screen Shot 2014-12-17 at 3.45.54 PM

Before you can start using VUM, log into your vCenter Server and click on Home. Under Solutions and Appliances, you should be able to see Update Manager.

Screen Shot 2014-12-17 at 3.54.28 PM

If the Update Manager does not show up, go to Plugins -> Manage Plugins and verify that the VMware vSphere Update Manager is enabled. You will need to install the VUM client on your local machine through the Plug-in Manager.

Screen Shot 2014-12-17 at 3.54.33 PM