Running Nested ESXi 5 in VMWare Workstation 8

 

VMware Workstation 8

The best thing about VMware, is I can also virtualize ESXi inside VMware Workstation!  So on my laptop, in VMware Workstation, I can run multiple ESXi servers, that in turn have VMs inside them.  Even better is the fact that I can have 64bit guests inside my ESXi servers running inside VMware Workstation.  Sounds confusing as I type, so here’s a diagram:

In order to run ESXi inside VMware workstation, we simply need to select “VMware ESXi 5″ as the operation system of the guest VM we are creating.

Then, Edit the VM’s Settings, and under the Hardware tab, and processors, check the box to Virtualize Intel VT.

The option to run ESXi inside of VMware workstation is great, especially for when you don’t have a lot of physical hardware to test with. I have also used it to test H/A scenarios. 

VMWare ESXi 5 High Availability Isolation Network Problems

 

Installing VMWARE ESXi 5 High Availability in a school today, I came across a problem with the ISOLATION network address being the gateway not being pingable from any of the VM Hosts as the local authority has prevented icmp packets (Ping) across the LAN. So to force the HA Cluster to use a different IP for the isolation network you will need to do the following:

Multiple isolation response addresses can be specified using the das.isolationaddress0 through das.isolationaddress9 options.

To specify the values for these options in Virtual Infrastructure Client:

  1. Select the HA cluster.
  2. On the Summary tab, click Edit Settings.
  3. In the Settings dialog, select VMware HA.
  4. Click Advanced Options.
  5. In the Advanced Options (HA) dialog, enter the option name and the corresponding value:
    • Option: das.isolationaddress0
    • Value: A valid IP address other than the default gateway address
      Similarly, you can set more isolation response addresses using das.isolationaddress1 throughdas.isolationaddress9.
  6. In the Advanced Options (HA) dialog box, set this option:
    • Option: das.usedefaultisolationaddress
    • Value: false
      Notes:
      • You must set this option if you are setting multiple isolation response addresses.
      • Additionally you should configure das.usedefaultisolationaddress to false when the default gateway is a device which cannot be pinged.
  7. Click OK.
  8. Click OK.
  9. Edit settings for the cluster again.
  10. Disable HA and click OK.
  11. Edit settings again.
  12. Enable HA and click OK.

At the time of VMware HA configuration, if none of the specified addresses can be reached, the configuration operation fails. If only a subset of the specified isolation addresses cannot be reached, then the configuration operation succeeds, but a configuration issue is displayed for the cluster and the cluster becomes yellow. The configuration issue identifies the isolation response addresses that could not be reached.

Although VMware HA supports a maximum of 10 isolation response addresses, in most cases one or two isolation response addresses should be sufficient. Also, the das.isolationaddress option formerly used to set a single isolation response address is still supported.

Note: If you specify multiple isolation response addresses, VMware recommends that you ensure the correct operation of VMware HA by:

  • Use the default gateway address and other reliable addresses physically close to the hosts in the cluster.
  • Ensure a corresponding isolation address is setup for each service console network that has been created on the ESX Server.
  • Change the default failure detection time to 20 seconds or greater. To change the default failure detection time:
    1. Select the HA cluster.
    2. On the Summary tab, click Edit Settings.
    3. In the Settings dialog, select VMware HA.
    4. Click Advanced Options.
    5. In the Advanced Options (HA) dialog, enter the option name and the corresponding value:
      • Option: das.failuredetectiontime
      • Value: A value in milliseconds that represents the timeout value (20 seconds = 20000 milliseconds)
    6. Click OK.
    7. Click OK.

Notes:

  • das.failuredetectiontime does not need to be increased when multiple das.isolationaddress options are specified as the pings occur in parallel.
  • das.failuredetectiontime is no longer supported in vCenter Server 5.0. For more information, see vSphere HA Advanced Attributes.

VMWare Converter and Microsoft Sysprep

Microsoft has a different version of Sysprep for each release and service pack of Windows. You must use the version of Sysprep specific to the operating system you are deploying.The differences are not immediately visible in the packaging and documentation of the service packs, so it is necessary to manually investigate.

The contents of the Sysprep deploy.cab file must be extracted to the Sysprep Directory on the vCenter Server host. If the file downloaded from the Microsoft Web Site is a .cab file, the Installing the Microsoft Sysprep Tools in the Virtual Machine Administration guide, details how to install the Sysprep Tools.

 

If the file downloaded from the Microsoft Web Site is a .exe file, these additional steps must be executed to extract the files from the .exe:

  1. Open a Windows command prompt. For more information, see Opening a command or shell prompt (1003892).
  2. Change to the directory where the .exe file is saved.
  3. Enter the name of the .exe file with the /x switch to extract the files. For example:

    WindowsServer2003-KB926028-v2-x86-ENU.exe /x

  4. When prompted, choose a directory for the extracted files.
  5. Browse the directory and double-click the deploy.cab file.

    Note: In some cases, the deploy.cab file may be located within one of the subfolders created in Step 3.

  6. Select all the files, and copy them to the Sysprep Directory.

When the contents of the of the Sysprep deploy.cab file have been extracted to the Sysprep Directory on the vCenter Server:

  1. Log in to the vCenter Server as an Administrator.
  2. Click Start > Programs > Accessories > Windows Explorer.

  3. Navigate to the Sysprep Directory as listed in the table below.
  4. Right-click on the Sysprep .exe file and choose Properties.
  5. Click the Version tab. Record the number at the top next to File Version:.

The table below lists the Sysprep version for the Windows versions that are supported for Image Customization. Compare the Sysprep version number with the Windows version for which it is intended:

Notes:

  • If vCenter Server is installed on Windows Server 2008 and above, is%ALLUSERSPROFILE%\VMware\VMware VirtualCenter\Sysprepwhich generally translates toC:\ProgramData\VMware\VMware VirtualCenter\Sysprep by default.

    Note: C:\ProgramData may be a hidden folder.

  • If vCenter Server is installed on any other Windows operating system, is%ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Sysprep\ which generally translates to C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Sysprep\ by default.
  • To check the SID of a server deployed from a template, you can use the PsGetSid. For more information, seehttp://technet.microsoft.com/en-us/sysinternals/bb897417.

 

Windows Version Sysprep Directory Sysprep Version
Windows 2000 Server SP4 with Update Rollup 1

Download at

http://www.microsoft.com/downloads/details.aspx?FamilyID=0c4bfb06-2824-4d2b-abc1-0e2223133afb

Or

The updated Deployment Tools are available in the Support\Tools\Deploy.cab file on the Windows 2000 SP4 CD-ROM. To download this file, visit the following Microsoft Web site:

\2k 5.0.2195.2104
Windows XP Pro SP2

Download at

http://www.microsoft.com/downloads/details.aspx?FamilyId=3E90DC91-AC56-4665-949B-BEDA3080E0F6

\xp 5.1.2600.2180
Windows 2003 Server SP1

Download at

http://www.microsoft.com/downloads/details.aspx?familyid=A34EDCF2-EBFD-4F99-BBC4-E93154C332D6

\svr2003
5.2.3790.1830

(srv03_sp1_rtm.050324-1447)

Windows 2003 Server SP2

Download at

http://www.microsoft.com/downloads/details.aspx?FamilyID=93f20bb1-97aa-4356-8b43-9584b7e72556

\svr2003
5.2.3790.3959

(srv03_sp2_rtm.070216-1710)

Windows 2003 Server R2

Download at

http://www.microsoft.com/downloads/details.aspx?FamilyID=93f20bb1-97aa-4356-8b43-9584b7e72556&displaylang=en

\svr2003
5.2.3790.3959

(srv03_sp2_rtm.070216-1710)

Windows 2003 x64
Download at
http://www.microsoft.com/downloads/details.aspx?familyid=C2684C95-6864-4091-BC9A-52AEC5491AF7&displaylang=en
\svr2003-64
5.2.3790.3959

(srv03_sp2_rtm.070216-1710)

Windows XP x64
Download at
http://www.microsoft.com/downloads/details.aspx?familyid=C2684C95-6864-4091-BC9A-52AEC5491AF7&displaylang=en
\xp-64
5.2.3790.3959

(srv03_sp2_rtm.070216-1710)

Windows XP Pro SP3

Download at

http://www.microsoft.com/downloads/details.aspx?familyid=673a1019-8e3e-4be0-ac31-70dd21b5afa7&displaylang=en

\xp 5.1.2600.5512
Windows Vista

System Preparation tools are built into the Windows Vista operating system and do not have to be downloaded.

Not Applicable Not Applicable
Windows Server 2008

System Preparation tools are built into the Windows Server 2008 operating system and do not have to be downloaded.

Not Applicable Not Applicable
Windows Server 2008 R2

System Preparation tools are built into the Windows Server 2008 R2 operating system and do not have to be downloaded.

Not Applicable Not Applicable
Windows 7

System Preparation tools are built into the Windows 7 operating system and do not have to be downloaded.
Not Applicable Not Applicable
vCenter Server Virtual Appliance 5.0 /etc/vmware-vpx/sysprep/ Not Applicable