Vmware Fix for Server 2012 Virtual machines running on ESXI 5.0

Technical Article
September 17, 20122 min read

2012 fix for Server 2012 Virtual Machines

Categories
MicrosoftVirtualisationVmware
Tags
Vmware EsxWindows 8Windows ServerWindows Server 2008 R2Windows Server 2012
Vmware Fix for Server 2012 Virtual machines running on ESXI 5.0

Windows 8 / Windows Server 2012 is listed as Tech Preview support for ESXi 5.0 Update 1 in the Guest OS compatibility guide. For more information on the Tech Preview support level, see Understanding guest operating system support levels (2015161).

Windows 8 / Windows Server 2012 is fully supported for ESXi 5.1. For more information, see What’s New in VMware vSphere 5.1.

Consider this guidance, which is based on testing Windows 8 / Windows Server 2012 up to build 8224:

  • Windows 8 Developer Preview / Windows Server 2012 Release Candidate does not boot on ESXi 5.0. To resolve this issue, you must install patch ESXi500-201112001 (Patch 02):
    1. Download and install ESXi500-201112001 (Patch 02). For more information, see VMware ESXi 5.0, Patch Release ESXi500-201112001 (2007680).
    2. Create a new virtual machine configured for either Windows 7 or Windows 2008 R2.
    3. Enable 3D graphics or do not install VMware's WDDM video driver.
    4. Install Windows 8 / Windows Server 2012 from Media.
    5. Install VMware Tools.Note: VMware does not recommend installing VMware's WDDM video driver. Use the default VESA driver.
  • If you experience a black screen after installing VMware's WDDM video driver in a virtual machine with Windows 8 / Windows Server 2012, enable 3D graphics or reinstall the operating system and VMware Tools without VMware's WDDM video driver.
  • VMware does not currently recommend using USB xHCI with Windows 8 / Windows Server 2012. To work around this issue, remove the USB xHCI controller or use the USB EHCI+UHCI controller.Note: Any changes to the virtual hardware must be preceded by a full shutdown on the command line (shutdown /s /t 0 /full). Otherwise, the Windows 8 / Windows Server 2012 hibernate-shutdown may not fully detect hardware changes and you may experience a blue diagnostic screen or triple fault at boot.
  • The vmxnet3 virtual NIC does not work in a Windows 8 / Windows Server 2012 virtual machine with ESXi 5.0. To work around this issue, use e1000e or e1000 NICs.
Related

Related articles

Upgrading ESXI 5.1 to 5.5 - The Shell Way
September 25, 2013

Upgrading ESXI 5.1 to 5.5 - The Shell Way

Shell-based upgrade from VMware ESXi 5.1 to 5.5 using esxcli software profile update against the VMware online depot, with the httpClient firewall ruleset, SAN disconnect precaution and esxupdate log tailing for progress.

Poor Man's DRS: Memory Balancing for vSphere Standard Clusters
March 8, 2013

Poor Man's DRS: Memory Balancing for vSphere Standard Clusters

A PowerCLI scheduled task that balances VM memory across hosts in a vSphere cluster that is not licensed for DRS. Calculates the cluster's average host memory utilisation, finds hosts more than a configurable threshold above the average, and vMotions one VM per hot host to the coldest host in the cluster.