Windows 8 (RTM) runs fine on ESXi 5.0 Update 1 Build 623860, and Build 768111

This post will be updated throughout the next few days, come back and hit refresh for the latest screenshots and most accurate information, possibly including a quick test of the 32 bit version as well…
(Update 11:56pm ET Aug 15 2012, Windows 8 Pro x86 install is nearly identical to the screenshots below, instead choosing Microsoft Windows 8 (32-bit), and leaving the BIOS alone (no UEFI needed)


Nice Seattle photo apparently for the final RTM version of the login screen, purple Metro UI, and flowery desktop apparently chosen, for this final build 9200. Note also that “Build 9200″ always shows on the desktop, no registry tweaking required. Well, at least until you activate your license key.

 

 


BACKSTORY:

Ok, now that we’re done looking at the scenery, let me point out that I’ve already had the chance to try out Windows 8 RTM (Release To Manufacture) code in several VMs, thanks to the power of vZilla. This release is the same exact bits as the actual GA (Generally Available) code release on October 26,2012.

While the MSDN site was swamped starting at the 1pm ET release of the code, finally, by 1:30pm eastern, I was able to finally locate the file I wanted by searching MSDN for “Windows 8 Pro”, since it wasn’t showing in any other views.

I then kicked off the download, and after about 30 tries, the Akamai based Download Manager (using IE ActiveX) came up, and within 15 minutes, I had the file named en_windows_8_pro_vl_x64_dvd_917699.iso completely downloaded.

And now that I’ve taken Windows 8 Pro x64 out for a sping, (videos below), I’m relieved to say Windows 8 x64 runs fine under ESXi 5.0 Update 1. Even smoother with ESXi patched to Build 768111 and it’s recent VMware Tools drivers. The only trickery All you have to do is either:

a)  pretend it’s Windows 7 x64, since telling ESXi it’s Windows 8 x64 gives you the usual hang after the first reboot

b)  set the VM to Windows 8 x64, with a UEFI BIOS

That’s pretty easy, either way. You’ll also see a little Windows UI Tutorial video that runs during the second reboot, to get you used to the new UI. Same video comes up when I deploy from the template (cloned, but with new virtual hardware).

I had Windows 8 working and configured within about 15 minutes of completing the download from Microsoft. The install itself took under 5 minutes. Even the VMware Tools Full Install was simple.


VIDEOS:

1080p step-by-step (yeah, that took Camtasia Studio 8 a while to render and upload to YouTube, but I think you’ll agree the wait was worthwhile)

You can witness my very first install attempt, from beginning to end, right over here:

  • using the pretend it’s Windows 7 x64 technique:

And here’s take 2, much cleaner, but also a much more time consuming approach
(I suspect no patches will be needed, once ESXi 5.1 comes out)

  • ESXi 5.0 Update 1 patched to build 768111 first
  • create a Windows 8 x64 VM set to UEFI BIOS type
  • install newest VMware Tools (that the latest patched ESXi provided)
  • some best practices tips including handy auto-login, and extremely rapid deployment from template:

 


REFERENCE:

For reference, here’s the actual MSDN download details that I used
(I cannot get to the Retail versions, just the VL versions, but all function and screenshots and videos should be very similar, and VL version does not require license keys to install):

Windows 8 Pro VL (x64) – DVD (English)
ISO|English|Release Date: 8/15/2012|Details
3327 MB
File Name: en_windows_8_pro_vl_x64_dvd_917699.iso
Languages: English
SHA1: 6DDEDEBE40AB59CB11823F62F475C43C4053FE60

Note that the Windows Experience Index wasn’t exactly spectacular as far as graphical performance (2.0) in vSphere Client Console, even with the VM’s Video Adapter type set to 3D:

Also note that Microsoft has disabled Aero both on the local console (and on physical hardware), and disabled Aero via Remote Desktop Connection as well, which used to work, seen here:
tinkertry.com/enable-windows7-aero-for-remote-desktop-connection-to-vms
I’ll be doing some more work to test installing the better VMware video driver, if that’s even possible, doesn’t look too promising, based on my poking around the drivers folders, and the comments over here.

See also how much easier the installation has gotten since Windows 8 Consumer Preview:
tinkertry.com/windows-8-consumer-preview-on-esxi-5-0-patch-02

and the good old “Windows 8 operating system does not boot or install on ESXi or ESX” article on VMware’s site since May:
kb.vmware.com/selfservice/microsites/microsite.do?cmd=displayKC&docType=kc&externalId=2006859&sliceId=2&docTypeID=DT_KB_1_1

You’ll still have the best experience, using the Windows 8 Style UI (formerly Metro) and Sound, over Remote Desktop Connection in full screen mode (making moving the mouse to the corners easier).

 


RECIPE: (new screenshots in progress)

How to install Windows 8 Pro x64 in an ESXi 5.0 Build 768111 Virtual Machine

1)  Update if your version of ESXi doesn’t already show as Build 623860 (Update 1) or later, with the latest being 76881 which you can read all about here, which will also get you the most recent VMware Tools version for Windows 8 guests. The general update technique is seen here:
tinkertry.com/patchesxi50

Here’s the actual steps for obtaining and installing Build 768111, along with nice :

a)  download the zip bundle here:
hostupdate.vmware.com/software/VUM/OFFLINE/release-346-20120706-638484/ESXi500-201207001.zip

b)  use WinSCP to put the file into the root of a datastore on the ESXi host you wish to patch, make note of the VMFS datastore name

c)  stop all workload on the ESXi host (shutdown all VMs), and if you’d like, right-click on the ESXi host and put it into maintenance mode

d)  issue the following exact command from a PuTTY session to the VMFS datastore where you put the zip file, substituing your VMFS datastore name for SSDRAID0:
esxcli software vib update --depot=/vmfs/volumes/SSDRAID0/ESXi500-201207001.zip

e)  reboot ESXi

f)  install latest vSphere client
you can do this by pointing your browser to the ESXi host and clicking on the download link there, which points here:
vsphereclient.vmware.com/vsphereclient/6/2/3/3/7/3/VMware-viclient-all-5.0.0-623373.exe

This entire procedure is seen very near the beginning of the second video above (here), if you need more detail.

 

2)  Download the Windows 8 64-bit (x64) 3.3GB ISO
en_windows_8_pro_vl_x64_dvd_917699.iso
from this search for “Windows 8 Pro” at MSDN here
License key is not needed for the initial installation
depending upon the type of MSDN or Technet, you have, you may be downloading a Retail version instead, and don’t forget to grab license keys, only for activation of VMs that you intend to keep

 

3)  Upload the ISO you just downloaded to the ESXi datastore, using free Veeam FastSCP (6x faster) or vSphere Client Datastore Browser (slow)

 

4)  Create Windows 8 Pro x64 Virtual Machine
follow along carefully, verifying you have each checkbox set correctly:
(Update 11:56pm ET Aug 15th, Windows 8 Pro x86 install is nearly identical to the screenshots below, instead choosing Microsoft Windows 8 (32-bit), and leaving the BIOS alone (no UEFI needed)

If you thin provision (pretend you have more storage available than you physically do), be sure to watch your VMFS filesystem available disk space very very carefully!

Get ready to click with your mouse to give the console focus, then press any key to get the virtual UEFI BIOS to boot from the virtual DVD!

 

 

5)  Install VMware Tools

  1. Once installed and booted, you can finally install VMware Tools the usual way in vSphere Client, “Typical Install” seen being kicked off below:

 



ICING ON THE CAKE:

RDP connection for lag free mousing around, don’t forget to try multiple monitors over RDP for a real treat!

  • Enable Remote Desktop Connection in the virtual machine. Configure a Remote Desktop Connection session from your workstation, ideally using Display tab for Fullscreen setting, which will make moving the mouse to the corners a lot easier (for Charms, etc.)
  • Keep in mind that at least 768  minimum vertical resolution is required by Metro, and leave bring sound, and turn on sound and all the high bandwidth options.
  • Finally, be sure to turn on the remote keyboard option (see screenshot below), to allow you to use the crucial Win+Q (find) and Win+C (charms) menus, even in windowed (non-fullscreen) remote sessions:

Under Keyboard, be sure your Windows key combos are sent to the Remote Desktop Connection by choosing “On the remote computer”

Share Button

written by

The author didn‘t add any Information to his profile yet.

2 Pingbacks/Trackbacks

  • moermansk

    I see that you also don’t have sound. I installed RTM but have no audio. Is it not availible in Vsphere ?

  • tinkererguy

    Unfortunately, that’s normal, no sound from vSphere client, so better off with Remote Desktop Connection (where sound works).
    More info here:
    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004839

    and here:
    http://www.tinkertry.com/enable-windows7-aero-for-remote-desktop-connection-to-vms/

  • David Kings

    Another way of configuring sound, which I have done for 4 of my VMGuests running under vSphere, is to purchase inexpensive USB sound sticks, one per VM Guest you would like to provide sound to, and pass through each USB sound device to the individual VM Guest.
    This is useful if you wish to hear sound whilst your VM Guest is running, but doesnt have a Remote Desktop connection currently active.
    I use this extensively for my Home Automation system which runs 24×7 as a VM Guest, making numerous announcements to the house.

    All 4 USB sound sticks have worked successfully plugged into a USB hub on one USB port off my Z77 MB.

    I have tried passing through the onboard sound card to one of my VM Guests, however that did not seem to work.

    David

  • Pingback: “vZilla” Z68/Core i7/LSI 9265-8i – built for virtualization, storage, and speed | Tinkertry

  • http://www.facebook.com/jrobertfisher Rob Fisher

    Incorrect Syntax:
    esxcli software vib update –depot=/vmfs/volumes/SSDRAID0/ESXi500-201207001.zip
    It should be:
    esxcli software vib update –-depot=/vmfs/volumes/SSDRAID0/ESXi500-201207001.zip

    or
    esxcli software vib update –d=/vmfs/volumes/SSDRAID0/ESXi500-201207001.zip

  • RS

    How do you get audio in Win8 / ESX5 ? My VM has no sound at all detected.

  • Alex

    This tutorial is using a PRE version, NOT the RTM of Win8. This version here is from 8/15. The RTM was released 9/25. You’re using a pre-release which is build 8200 or 9200. I forgot which on it was. Between that release and the Win8 evaluation MS changes something major which now it no longer works in esx/esxi. Great job MS.

    • Alex

      RTM is 9200, The pre is 8200. So far the x86 only works under VMware ESX. The x64 version does not work. Can’t recognize the disk etc .

      • Alex

        So, going to correct myself… The version from 8/15 is RTM and is build 9200. The one released the other day is 9200 build also but it just has an evaluation period of 90days.

        If you’re ISO is not working, RE-DOWNLOAD IT. I was getting stuck where it would not find the drives, and seeing errors when trying to boot the CD from EFI.

        • tinkererguy

          That was extremely considerate of you to post this follow-up, hopefully sparing others from experiencing what you did, especially since over 100 folks a week are still reading this older article.
          Thank you!

  • Archie

    Thank you so much for putting this out there. We had set the VM as “Windows 8 64-bit” for Windows 8 Pro 64-bit on our ESXi 5.0 environment. Setting it to “Windows 7 64-bit” did the trick.

    • http://tinkerty.com/ Paul Braren

      Archie, you are quite welcome, so glad it helped.
      Even more glad you took a moment to tell others by posting here, much appreciated!

  • Pingback: TinkerTry IT @ home | Windows 8.1 Preview runs fine on ESXi 5.1 Update 1 Build 1065491