vSphere 5.0 Update 1 released (ESXi 5.0 Update 1 Build 623860 and vCenter Update 1 Build 639890)
This is just a brief product update announcement with reference links.
Upgrade Install of ESXi 5.0 Update 1:
If you don't have VUM (VMware Upgrade Manager) installed, the easiest way to upgrade your existing ESXi 5.0 installation can be done by kicking off the patch download of the zip bundle from this site:
hostupdate.vmware.com/software/VUM/OFFLINE/release-328-20120312-212851/update-from-esxi5.0-5.0_update01.zip
then, while downloading, you can read about the bundle here:
kb.vmware.com/selfservice/microsites
once you've got the zip file, then follow along with these instructions:
TinkerTry.com/patchesxi50
or the new video walkthrough I just recorded here:
Fresh Install of ESXi 5.0 Update 1:
This 5.0 Update 1 installable was also released today, with links to the detailed release notes here:
www.yellow-bricks.com/2012/03/16/vsphere-5-0-update-1-released
If you also want a walk through of the fresh install method, see also:
TinkerTry.com/vsphere5-install-step-by-step
I haven't yet spotted whether this affects Windows 8 Consumer Preview or Windows Server 8 Beta behavior much, other than this sentence in the release notes:
The VMware vCenter Server for Windows 5.0 Update 1 offers the following improvements:
Guest Operating System Customization Improvements: vCenter Server adds support for customization of the following guest operating systems:
Windows 8
update Mar 16 2012 06:00pm, new VMware Tools 8.6.5 build-621624 that comes bundled in ESXi 5.0 Update 1 now lets you install:
"VMware SVGA 3D (Microsoft Corporation - WDDM)" 7/28/2011 7.14.1.1070 driver in Windows 8 Consumer Preview without any errors, seems to work!
Also, when using the create a Virtual Machine Typical install wizard, you can now choose Windows 8 or Windows Server 8 right from the the drop-down menu._
The actual public download site is here, but you need a valid login:
www.vmware.com/go/download-vsphere
and for those with proper entitlement/licensing, the direct download for VMware ESXi 5.0 Installable Update 1:
downloads.vmware.com/d/details/esxi50u1/dHRAYndkZSpidHclZQ==
Free Version of the Hypervisor:
I don't yet see an update for the free Hypervisor download, so it's still at
ESXi 5.0 Installable (CD ISO)
08/24/11 | 5.0.0 | 291 MB | Binary (.iso)
www.vmware.com/tryvmware/index.php
but that can be patched to get the to the same 5.0 Update 1 (see Upgrade Install above)
VMware vCenter Server Appliance is still 5.0.0.3324:
I don't yet see an update for the VMware vCenter Server Appliance, so it's still at
5.0.0.3324 Build 472350, seen in screenshot below.
Easiest to get the appliance by using these links to grab the 3 files you need by manual cut and paste (links don't seem to render and work right):
And here’s the guide to get started with actually importing these files and configuring the VM under ESXi 5.0:
vmwire.com/2011/07/15/vsphere-vcenter-server-linux-virtual-appliance-quick-start-guide
or if you prefer, a video walkthrough I created here:
youtu.be/QPtStneewys?hd=1&t=1h02m26s
See also "Enabling No Execute Memory Protection" in host BIOS, and disabling floppies, as fixes for folks with Error Code 0x0000005D:
social.technet.microsoft.com/Forums/en-US/winserver8setup/thread/54dcd717-a2fe-45bd-95ce-9c8dd03cae73
All Comments on This Article (9)
FYI, Update 1 breaks auto startup/shutdown in free version of ESXi 5.0
See http://blogs.vmware.com/vsphere/2012/03/free-esxi-hypervisor-auto-start-breaks-with-50-update-1.html
I entered my "free" license after having used an eval version until now. Looks like I have to either roll back the install or go back to using eval version.
This is a very interesting/unique problem.
Can I start with asking you a bit about your system.
Is it like vZilla ( http://tinkertry.com/vzilla )?
Which operating system is your VM?
Which YouTube video did you find helpful?
Thank you Meir!
hi tinkereguy,
i am getting a bsod every time i open procmon and procexp together in my vm.
i just folowed your wonderfull video but the update havent solved the problem. any idea?
the bsod is ca
Device Manager says ASMedia version is 1.10.1.0. It's the version that came on the CD with the Highpoint card. Will upgrade just to make sure everything is as intended from now on.
I found I couldn't see my USB 2 devices plugged into my USB 3 port until I install the VMware USB 1.1 and 2.0 controller. Maybe it's Highpoint driver related?
Will assume it's just something weird about my setup, although the only physical difference is that I passthrough a PCI modem you don't have to the VM in question - it could be that, I guess. Will just keep an eye on this and a cautious approach next time.
Ok, confirmed my USB 2.0 device (a UPS) plugged into my motherboard and assigned to my Windows VM still works, indeed it does. Tried a USB 2.0 stick on one of the USB 3.0 ports, it works fine as well.
Checked my VMware Tools, I'm at 8.6.5 build-621624 (which means yes, I did manually install the Tools Update). I don't have COM ports, parallel ports, or sound enabled in my motherboard's BIOS fyi, and I never did manually uninstall unrelated devices (COM ports, HIDs) in my Windows instance.
Have to head away from my computer for the rest of today, will continue to think about this, and follow-up with you as soon as I can. One thought would be to try a fresh VM, no USB controller needed in the VM settings (since you're passing through), and only PCI passthrough turned on, then installing ASMedia drivers. Does that work? Which ASMedia drivers you on? I'm on 1.14.4.0 fyi.
yes, same BIOS level, 1.30. Did you upgrade VMware Tools in the VM? There was an exclamation mark on the icon so I did the upgrade before doing anything else. The problem may have been because of the VMware tools upgrade, not the ESXi update, although not sure I can/want to do one without the other. If it is VMware tools related, maybe the next VMware tools update (regardless of ESXi version) is something to be concerned about?
Are your USB 2 devices mapped through from the client device or are they plugged into the Highpoint USB 3 port, as mine are in this case?
Jean, you definitely got my attention. I just retested my USB 3.0 device passed through to my VM, works fine, no fiddling, and the speed is still fine. Also had a look at ESXi mapped USB 2.0 devices, no issues noticed there either. Not saying you didn't have to fiddle. Am saying you got me very curious, of course.
I wonder what is different about your experience (with ESXi 5.0 Update 1) than my experience, given we have the same motherboard. Can I start by asking your BIOS level, is it also 1.30?
http://www.asrock.com/mb/download.asp?Model=Fatal1ty%20Z68%20Professional%20Gen3&o=BIOS
Just want to pass a warning message along about doing these updates.
I have a ~3 week old vZilla and the update caused my serial port device (the COM1 port on the mb) and the USB controller I added in order to use USB 2 devices on the USB 3 port I passedthrough to be removed from the one VM I have that needs them. It took quite a bit of fiddling, including 2 restarts/re-adds before the devices even came back after a reboot, then uninstalling related devices (COM ports, HIDs) and restarting to allow them to re-install in order for the software that needs them to see them.
I finally got 4 of my 5 devices back and living through reboots. The four that work are the COM port and three USB-to-COM adapters - these all appear as COM ports. The fifth one is my APC UPS via USB cable, an HID device. The APC software is no longer able to detect the UPS. Have tried re-detecting devices, restarting related services, etc. The only thing I haven't yet tried yet is uninstalling/reinstalling the software and reconfiguring from scratch - will try that next, I guess.
Maybe this is normal behavior / workload that just need to be factored into each update but it makes me a little worried about doing them in the future given that much of the vZilla hardware, and in particular the motherboard, is unsupported by vmware. It could make a great thing go bad quickly...
Paul Braren | TinkerTry.com
I will definitely be looking into this issue I had briefly read about a while back, unfortunate that it hasn't been fixed, even after so many months...thank you Jean!