At the beginning of the year we performed an upgrade of our vSphere environment from vSphere 5.0 to vSphere 5.1 U1 Build 1063329 compromised of about a dozen ESXi hosts and a vCenter instance hosted on Windows Server 2008 R2 SP1. One of the outstanding issues from this project is the upgrade of Virtual Hardware for Virtual Machines.

I'm having trouble understanding why I should go to work and downtime to upgrade the Virtual Hardware version on all of our VMs. Our newly created Virtual Machines are using Virtual Hardware v. 9, the most recent supported version in vSphere 5.1 U1 which resolves issues we were having with Windows Server 2012 R2 and WinPE 4.0 on our older vSphere 5.0 instance. All of our older Virtual Machines are compatible Virtual Hardware versions (KB2007240) so we are not forced to upgrade their hardware version.

Am I missing some technical reason for upgrading all our Virtual Machine's Virtual Hardware to the "newest" Version 9 since guest operating system and ESXi compatibility are not issues? Upgrading the Virtual Hardware is not necessarily trivial since I have to shutdown the VM, take a snapshot or backup of it and then upgrade it for a few hundred VMs. Other than avoiding having to do this in the future and getting warm fuzzies that all our VMs are running on the most recent Virtual Hardware version why should I bother doing a straight cutover instead of a rolling upgrade as we replace our Virtual Machines?


In general, virtual hardware versions introduce new functionality, extend limits and may have performance implications. See the VMware hardware version matrix.

Don't worry about this for the revision of vSphere you're on now. You can run all day on old versions, based on the setup you have. VM hardware version 8 sounds like the best choice for your specific situation.

The only real consideration with regard to virtual hardware versions is the move from version 8 or vmx-09 to the vmx-10 introduced in vSphere 5.5. There are manageability implications of this move. But on the positive, that process is streamlined through the vSphere Web Client, which allows you schedule the VM version upgrade during guest reboot.

enter image description here

  • 1
    the "Only upgrade after normal guest OS shutdown" option is very cool
    – warren
    Mar 10 '14 at 19:23
  • From what I've observed, "Only upgrade after normal guest OS shutdown" is useless. When it's checked, the hardware version upgrade only happens when the VM is powered off, not when the guest OS reboots, which basically ruins the idea of a "scheduled" (or opportunistic) upgrade. Dec 12 '18 at 12:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy