Posts Tagged ‘VMware’

VMware vSphere Converter 4.0 U1 Cold Clone

Sunday, February 14th, 2010

This is my first look at the current release of converter (4.0.1), release notes here. Some of the new features in this version include support for Windows Server 2008 and RHEL, Ubuntu and SUSE, also a few good things around hot cloning.

The conversion I’m doing was of a Windows Server 2003 Ent 32-bit physical server running on an HP DL380 G5 into a VM running on vSphere 4.0 U1, virtual hardware version 7. The process is almost identical to the previous cold clone version, the livery has been changed to reflect vSphere and vCenter in all the relevant places but it flowed the same. As with all conversions, it’s a good idea to prepare the server before conversion by disabling hardware agents (e.g. HP Insight Agents) and anything not absolutely necessary for the server to boot the first couple of times

Two good things: firstly configuring network settings seemed more robust (could be just me). I’d had problems with the previous version of the cold clone image where the network settings either didn’t take or would for whatever reason just not connect. Secondly, the conversion of this particular server was really fast. The server itself had two very small disks but both were resized (72GB partition into a 20GB partition and a ~570GB partition into a tiny 10GB partition), but the process did seem to run much faster than previous servers of similar size that I’ve converted with the old cold clone CD.

Only one odd thing with the end result was the amount of memory the virtual machine was assigned. The server itself had 4GB physical memory of which Windows sees 3.75GB. The virtual machine was allocated 3220MB during he creation process, not sure why this would happen.

VMware ESX 4.0 U1 – Storage Pathing Policy Issue

Thursday, January 7th, 2010

While fixing up storage pathing through redundant FC adapters, noticed that one ESX 4.0 U1 host using Fixed (VMware) path selection policy had an Active (I/O) path for each presented LUN but did not have a Preferred adapter highlighted. Also, received the following error when trying to set the preferred adapter (under Datastore Properties -> Manage Paths -> right-click in Paths, select Preferred):

Unable to cast object of type ‘LogicalUnitPolicy’ to type ‘FixedLogicalUnitPolicy’

This was only happening on one host and was happening for every datastore and every type of storage presented to the host (local and remote).

To fix, selected the only local storage presented to this host (where ESX was installed) and briefly changed the Path Selection Policy to Most Recently Used (VMware), which causes a Set logical unit policy action on the host. After doing so and then switching back to Fixed (VMware), the preffered path is then highlighted and the other LUN’s were able to be successfully set as well.

I expect that a rescan of the storage adapters may also resolve it but didn’t get the chance to try it.

VMware ESX 3.5 to vSphere (ESX 4.0 U1) Upgrade In A Nutshell

Thursday, January 7th, 2010

The intention for this upgrade was to use the VMware Host Update Utility included with the vSphere Client. However, an upgrade was in the end not possible. The reason being because the existing ESX 3.5 installation had customized partitions (specifically to fill out the local storage with /, /var, swap, etc). This was fine for ESX 3.5 but for ESX 4.0, these partitions are inside the service console VMDK stored on the local VMFS. There was only 2.5GB of space left over for VMFS on the ESX 3.5 installation.

So, the upgrade was effectively a per host rebuild to ESX 4.0. The process, however, is still simple:

  • vMotion all guests off of the host to be rebuilt
  • Put the host into maintenance mode
  • Remove the host from the cluster
  • Reboot the host and install from the ESX 4.0 media (selecting local storage to create the VMFS for the service console VMDK)
  • Add the host back to the cluster

After upgrading the first host, adding it to the cluster and ensuring that it’s configuration was good, I then created a Host Profile of it and used that profile to attach to the remaining hosts and apply it’s settings to ensure full compliance. This process saved plenty of time configuring the hosts post-install. A scripted installation may have been a better option but for <5 hosts, the Host Profile utility is a very fast way to configure hosts and ensure compliance. Further, for management purposes going forward, the Host Profile utility is an excellent tool to ensure compliance of hosts.

Install VMware ESX 4.0 vSphere in VMware Workstation 7

Tuesday, January 5th, 2010

Using a laptop with 4GB of RAM, trying to install ESX 4.0 Update 1. Allocated 2GB RAM to the virtual machine but receiving the following error when trying to power it on:

Not enough physical memory is available to power on this virtual machine with its configured settings.
To fix this problem, decrease the memory size of this virtual machine to XXXXMB, or adjust the additional memory settings to allow more virtual machine memory to be swapped.
Alternatively, do you want to temporarily reduce the memory size of the virtual machine from 2048MB to XXXXMB? Reduce Memort | Do Nothing

The only option of any use is of course “Do Nothing”. ESX 4.0 won’t install without a minimum of 2GB of memory.

To fix the issue and allow the virtual machine to power on with its allocation of 2GB memory: In Workstation, go to Edit -> Preferences -> Memory tab then increase the Reserved Memory slider up to the desired amount of memory. I increased it to exactly 2048MB and the ESX 4.0 virtual machine could be powered on.

Also tested with lower values and it will also work – it depends on the Additional Memory setting. The default option is to ‘Allow some virtual machine memory to be swapped’ (switching to the ‘Fit all virtual machine memory into reserved host RAM’ option, will result in the VM failing to power on if the Reserved Memory allocation is lower than the amount of memory allocated to the virtual machine).

A VMware Holiday

Sunday, December 20th, 2009

Between Christmas and the New Year, I plan to do a VMware ESX 3.5 cluster upgrade to vSphere. This will be 4 hosts in an HA/DRS cluster all upgraded to vSphere / ESX 4.0 U1.

The process should be similar to a regular host upgrade: Virtual Center (oops, vCenter), followed by the hosts, followed by the VM’s (tools and virtual hardware). There are a few different options when it comes to the upgrade including Update Manager, ESX host update utility, using install media at the console, … Will post again with the upgrade details.