While upgrading two of my ESXi hosts today I found this really helpful howto video on the VMware KB website. It shows you a step by step walkthrough of how to upgrade your ESXi 4.1 host to ESXi 5.0. There is a lot more information on different ways to upgrade to ESXi 5.0 in this VMware KB.
Today playing in my lab I had an issue running some VMs on a SSD. It turns out the Host Cache Configuration was causing some issues running the VMs on the same SSD. You enable host cache when creating a datastore on a SSD, but how do you disable it? Its not an option on the datastore properties. To disable Host Cache Configuration follow the steps below: Select Configuration Tab Select Host Cache Configuration under software Right Click on the SSD Datastore and Select Properties Disable Checkbox for Allocate space for host cache Click OK DONE!! Thats it, host cache has been disabled.
Back in February Max Daneri released his Auto Deploy GUI fling. This builds on the success of his PXE Manager fling released last year. Lots of other blogs have already reported this fling, but I have been asked three times this week where they can download it from. I will be writing a blog post soon on how to actually use this fling, much the same way I did with Max’s PXE Manager. Auto Deploy GUI is a front end interface to the Auto Deploy/Stateless infrastructure. Features The Auto Deploy GUI is a vSphere plug-in for the VMware vSphere Auto Deploy component. The GUI plug-in allows a user to easily manage the setup and deployment requirements in a stateless environment managed by Auto Deploy. Some of the features provided through the GUI include the ability to add/remove Depots, list/create/modify Image Profiles, list VIB details, create/modify rules to map hosts to Image Profiles, check compliance of hosts against these rules and re-mediate hosts. The GUI can be downloaded from labs.vmware.com/flings/autodeploygui There is a PDF document that explains how to configure and install the GUI plugin. The document can be downloaded from download3.vmware.com/software/vmw-tools/autodeploygui/VMwareAutoDeployGUIPracticalGuide5.pdf
So for a couple of days I have been re-building my lab. This has been overdue for a longtime and I finally had some time to get it done. The main purpose of re-building my lab is to make sure it follows the base reference architecture for vCloud as documented in the VMware vCloud Architecture Toolkit. Now you may notice the list of kit that I have in my lab below and wonder how I could do this with only two physical hosts. The simple answer is nested ESXi. The hardware in my lab consists of 1 HP ML115 G5 (AMD Opteron 1354 and 8GB RAM) 1 HP Microserver (AMD Athlon II Neo N36L and 8GB RAM) William Lam has wrote an excellent article on how to run nested ESXi within vSphere 5.0. This explains how to enable the hidden Guest OS settings. To read this article click here. So I began by re-building my physical hosts with ESXi 5.0. They had previously been running ESXi 4.1 Update 2. Simon Seagrave wrote a nice article on how to use a HP ML115 G5 and a HP Microserver together in a HA/DRS cluster using EVC Mode. To read this article click
Back in 2010 and I wrote a quick article on How To: Enable Remote Tech Support mode and SSH on ESXi 4.1. A few people have posted comments asking if I could do the same now that vSphere/ESXi 5.0 has been released. The actual steps haven’t really changed, however Remote Tech Support mode is now just simply called SSH. The steps listed below explain how to enable SSH on an ESXi 5.0 host. Login to vCenter Select your host Click the configuration tab Select Security Profile under Software Click Properties for Services Select SSH and click options Choose the startup policy that you require Click Start Click OK and OK SSH to your host Once enabled you will notice that the host within vCenter has a warning being shown. When selecting that host, and looking under the summary, vCenter alerts you to the fact that SSH is enabled.