Enable HA on a mixed ESX Cluster


I have a mixed ESX cluster at home. One box is running ESX 3.5 the other box is running ESX 4.0. When I tried to enable HA on this cluster I got the following error:


The ESX 3.5 host has a second Service Console port on the Storage (iSCSI) lan. The ESX 4.0 host doesn’t need this so this is why the ESX 4.0 host got this error.

To solve this issue I created a second Service Console Port on my ESX4.0 server.


Now I was able to enable HA on Cluster.


Add an ESX 3.x host to your vSphere Cluster


If you add an ESX 3.5 host to your vSphere Cluster,there is a change you’ll get this warning:


The solution is simple, you need the “old” license server running in your network. So download the “old” license server from http://vmware.com/download/vi/drivers_tools.html


Install the License Server for ESX 3.5 on different server than your vCenter box. I tried installing it on the same box, but it ended with a failed startup of the License server services. The installation is straight forward (read next, next, add license file, next and finish).

After the installation open the vCenter Service Settings option.


And enter the address of your license server and press ok.


Now it’s possible to add the ESX 3.5 host to your cluster.

VMware: Adding the Enhanced vmxnet vnic

The Enhanced vmxnet adapter was already available in ESX 3.5 (see KB1001805). The support for this adapter is a lot better since Update 4 is released. Now you can also add the Enhanced vmxnet adapter to a Windows Server 2003 VM, without the workaround mentioned in KB1007195.


Some info about the Enhanced vmxnet from KB1001805:

  • Enhanced vmxnet — The enhanced vmxnet adapter is based on the vmxnet adapter but provides some high-performance features commonly used on modern networks, such as jumbo frames. This virtual network adapter is the current state-of-the-art device in virtual network adapter performance, but it is available only for some guest operating systems on ESX Server 3.5. This network adapter will become available for additional guest operating systems in the future.
    Enhanced VMXNET is supported only for a limited set of guest operating systems:

    • 32/64-bit versions of Microsoft Windows 2003 (Enterprise and Datacenter Editions). You can use enhanced vmxnet adapters with other versions of the Microsoft Windows 2003 operating system, but a workaround is required to enable the option in the VI Client. See http://kb.vmware.com/kb/1007195. Since Update 4, you can add the Enhanced vmxnet via the VIC.
    • 32/64-bit versions Red Hat Enterprise Linux 5.0
    • 32/64-bit versions SUSE Linux Enterprise Server 10
    • 64-bit versions Red Hat Enterprise Linux 4.0
  • And a warning:

    Migrating virtual machines that use enhanced vmxnet. Enhanced vmxnet is new with ESX Server 3.5. Virtual machines configured to have enhanced vmxnet adapters cannot migrate to older ESX Server hosts, even though virtual machines can usually migrate freely between ESX Server 3.0 and ESX Server 3.0.1.

    If you must migrate a virtual machine between newer and older hosts,don’t choose enhanced vmxnet but instead one of the older adapter types. Flexible or e1000 are offered whenever enhanced vmxnet is offered.

    VMware: ESX(i) 3.5 u4 released


    VMware ESX 3.5 Update 4 has been released. You can find the download and release notes here:

    What’s New:


    Not all combinations of VirtualCenter and ESX Server versions are supported and not all of these highlighted features are available unless you are using VirtualCenter 2.5 Update 4 with ESX Server 3.5 Update 4. See the ESX Server, VirtualCenter, and VMware Infrastructure Client Compatibility Matrixes for more information on compatibility.

    1. This version of ESX Server requires a VMware Tools upgrade.

    The following information provides highlights of some of the enhancements available in this release of VMware ESX Server:

    Expanded Support for Enhanced vmxnet Adapter This version of ESX Server includes an updated version of the VMXNET driver (VMXNET enhanced) for the following guest operating systems:

    • Microsoft Windows Server 2003, Standard Edition (32-bit)
    • Microsoft Windows Server 2003, Standard Edition (64-bit)
    • Microsoft Windows Server 2003, Web Edition
    • Microsoft Windows Small Business Server 2003
    • Microsoft Windows XP Professional (32-bit)

    The new VMXNET version improves virtual machine networking performance and requires VMware tools upgrade.

    Enablement of Intel Xeon Processor 5500 Series — Support for the Xeon processor 5500 series has been added. Support includes Enhanced VMotion capabilities. For additional information on previous processor families supported by Enhanced VMotion, see Enhanced VMotion Compatibility (EVC) processor support (KB 1003212).

    QLogic Fibre Channel Adapter Driver Update — The driver and firmware for the QLogic fibre channel adapters have been updated to version 7.08-vm66 and 4.04.06 respectively. This release provides interoperability fixes for QLogic Management Tools for FC Adapters and enhanced NPIV support.

    Emulex Fibre Channel Adapter Driver Update The driver for Emulex Fibre Channel Adapters has been upgraded to version This release provides support for the HBAnyware 4.0 Emulex management suite.

    LSI megaraid_sas and mptscsi Storage Controller Driver Update — The drivers for LSI megaraid_sas and mptscsi storage controllers have been updated to version 3.19vmw and vmw respectively. The upgrade improves performance and enhance event handling capabilities for these two drivers.

    Newly Supported Guest Operating Systems — Support for the following guest operating systems has been added specifically for this release:

    For more complete information about supported guests included in this release, see the Guest Operating System Installation Guide: http://www.vmware.com/pdf/GuestOS_guide.pdf.

    • SUSE Linux Enterprise Server 11 (32-bit and 64-bit).
    • SUSE Linux Enterprise Desktop 11 (32-bit and 64-bit).
    • Ubuntu 8.10 Desktop Edition and Server Edition (32-bit and 64-bit).
    • Windows Preinstallation Environment 2.0 (32-bit and 64-bit).

    Furthermore, pre-built kernel modules (PBMs) were added in this release for the following guests:

    • Ubuntu 8.10
    • Ubuntu 8.04.2

    Newly Supported Management Agents — Refer to VMware ESX Server Supported Hardware Lifecycle Management Agents for the most up-to-date information on supported management agents.

    Newly Supported I/O Devices — in-box support for the following on-board processors, IO devices, and storage subsystems:

      SAS Controllers and SATA Controllers:

    The following are newly supported SATA Controllers.

    • PMC 8011 (for SAS and SATA drives)
    • Intel ICH9
    • Intel ICH10
    • CERC 6/I SATA/SAS Integrated RAID Controller (for SAS and SATA drivers)
    • HP Smart Array P700m Controller


      1. Some limitations apply in terms of support for SATA controllers. For more information, see SATA Controller Support in ESX 3.5 (KB 1008673).
      2. Storing VMFS datastores on native SATA drives is not supported.

    Network Cards: The following are newly supported network interface cards:

    • HP NC375i Integrated Quad Port Multifunction Gigabit Server Adapter
    • HP NC362i Integrated Dual port Gigabit Server Adapter
    • Intel 82598EB 10 Gigabit AT Network Connection
    • HP NC360m Dual 1 Gigabit/NC364m Quad 1 Gigabit
    • Intel Gigabit CT Desktop Adapter
    • Intel 82574L Gigabit Network Connection
    • Intel 10 Gigabit XF SR Dual Port Server Adapter
    • Intel 10 Gigabit XF SR Server Adapter
    • Intel 10 Gigabit XF LR Server Adapter
    • Intel 10 Gigabit CX4 Dual Port Server Adapter
    • Intel 10 Gigabit AF DA Dual Port Server Adapter
    • Intel 10 Gigabit AT Server Adapter
    • Intel 82598EB 10 Gigabit AT CX4 Network Connection
    • NetXtreme BCM5722 Gigabit Ethernet
    • NetXtreme BCM5755 Gigabit Ethernet
    • NetXtreme BCM5755M Gigabit Ethernet
    • NetXtreme BCM5756 Gigabit Ethernet

    Expanded Support: The E1000 Intel network interface card (NIC) is now available for NetWare 5 and NetWare 6 guest operating systems.

    Onboard Management Processors:

    • IBM system management processor (iBMC)

    Storage Arrays:

    • SUN StorageTek 2530 SAS Array
    • Sun Storage 6580 Array
    • Sun Storage 6780 Array

    VMware: Creating VMware ESX Unattended Install Media

    Paul Shannon heeft weer een super document gemaakt over het maken van een Unattended Installatie CD voor VMWare ESX. In de tijd van ESX 2.5.x heb ik ook eens zo’n CD gemaakt door de volgende guide te gebruiken: http://www.vmprofessional.com/index.php?content=kickstart_2. Helaas werkte deze guide niet meer met ESX 3.5. Ik ben dus erg blij met het document van Paul. Thanks Paul!

    Paul schrijft het volgende op zijn blog:

    I had a customer that had a requirement to backup the ESX Service Console settings and wanted to know the best files to backup. I suggested that it may be more prudent to create unattended installation media to make restores more seamless. This took a turn and I was asked to make a single CD that was capable of restoring any one of the 11 ESX hosts in the clusters. With a lot of reading and a lot of testing this was achieved and this document explains how I did it.

    Download het document hier: http://www.vm-aware.com/files/tech_notes/Creating_Custom_ESX_CD.pdf

    Bron: http://www.vm-aware.com/2008/12/22/creating-vmware-esx-unattended-install-media/

    Add Custom Fields to VI Client with Powershell (Samples)

    Hugo Peeters heeft zijn Powershell scripts voor het vullen van Custom Fields in vCenter gepost:

    Snapshot Count

    I already showed you how to do this, but I have now added an IF-statement so that only changes are updated (equal values are not overwritten). And I have added Julian Wood’s correction. Add-VMSnapshotCount.ps1

    Total Snapshot Size

    The number of snapshots is quite inetresting, but even more interesting, is the total size of the delta files all snapshots are occupying. They might be eating up all your precious SAN space. Plus, reverting to or committing a large snapshot is tricky. Add-VMSnapshotSize.ps1

    Host Hardware Model

    Want to see what models of hardware you are using in your datacenter? You could look at the summary tab of each host. Or run this script to add the info to the every Hosts tab in the VI Client. Select your Datacenter, select the Hosts tab and enjoy! Add-VMHostModel.ps1

    Host ESX Version

    Did you update all your ESX Servers to the latest version? Check it quickly using this script. Add-VMHostVersion.ps1

    Host LUN Count

    Last but certainly not least: are you sure every datastore you are using is available to all your ESX Servers? It is visible at a glance when you add the LUN Count to your VI Client! Add-VMHostLUNCount.ps1


    Check zijn site voor allerlei top Powershell scripts: http://www.peetersonline.nl/


    Bron: http://www.peetersonline.nl/index.php/vmware/add-custom-fields-to-vi-client-with-powershell-samples/

    VMware: Search the Hardware Compatibility Guide

    Jeej, we hoeven niet meer in de pdf’s te zoeken. Sinds kort heeft VMware een zoekfunctie op de site geplaatst.

    The new online compatibility guide provides a single point of access for all VMware hardware compatibility guides. The new search tool streamlines the HCL posting process and offers advanced search capabilities and the ability to save the guide(s) or search results in a .PDF or csv format.

    The new hardware compatibility guide replaces the following legacy PDF-format HCLs:

        * VMware ESX 3.0.x and above version Systems Compatibility Guide
        * VMware ESX 3.0.x and above version SAN (storage) Compatibility Guide
        * VMware ESX 3.0.x and above version I/O Compatibility Guide
        * VMware View Client Compatibility Guide


    De Compatibility guide vind je hier:


    Series: Hyper-v, not in my Datacenter part3

    Gabrie heeft part3 gepost.

    In part 3 of this series, I want to shed a light on the difference between the types of Migration in ESX and Hyper-V and the differences in storage between the both of them. Although I think most of the readers know the differences, I will start with a brief summary.

    • Hyper-V QuickMigration: When you want to move a running Virtual Machine from one host to another with as little downtime as possible, you can use QuickMigration. On host-A the VM will be suspended to disk, and then host-B will unsuspend the VM and run it.
    • Hyper-V & ESX Cold Migration: Moving a VM that is not running, to different host and/or different storage.
    • ESX VMotion: Moving of a running VM to a different host, without downtime.
    • ESX Storage VMotion: Moving the disks of a VM to different storage without downtime (VM doesn’t move).

    Lees de rest hier: http://www.gabesvirtualworld.com/?p=107

    EMC: Celerra Virtual Appliance and VI3


    De virtualgeek is bezig met een howto serie over het configureren van de Celerra Virtual Appliance. Deze appliance kun je impoprteren binnen VMware Workstation of ESX server. Hoe dit in zijn werk gaat lees je in de volgende posts:

    In de toekomst gaat EMC meer Virtual Appliances aanbieden van haar overige producten. Let wel op deze  appliances zijn alleen bedoeld voor test en studie doeleinden.

    VMware heeft ook een document uitgegeven. De pdf kun je hier vinden: VMware_VI3_and_EMC_Celerra_IP.pdf