I am in the process of planning for a large infrastructure upgrade from ESX3.5 to vSphere 4. As part of the planning I’ve been looking at Virtual Machine Virtual Hardware Versions. Currently all VM’s are running Version 4, but as we migrate to ESX4 we will have the option to upgrade to Version 7.
Instead of just upgrading all VM’s no questions asked, I decided to try and answer these following questions;
- Exactly what does Version 7 offer?
- What is the upgrade process?
- Will upgrading introduce any downtime?
- Could there be any issues after the upgrade which may cause the VM to not function correctly?
Here is what I’ve found
Exactly what does Version 7 offer that Version 4 doesn’t?
Virtual Hardware Version 7 offers five new features.
- Serial Attached SCSI (SAS) virtual devices – Provides support for running Windows Server 2008 Failover Clustering configurations.
- IDE virtual device – Ideal for supporting older operating systems that lack SCSI drivers.
- Hot Plug support – For virtual devices and hot add support for memory and virtual CPUs — List of supported Operating Systems
- VMDirectPath for Virtual Machines – VMDirectPath I/O device access enhances CPU efficiency in handling workloads that require constant and frequent access to I/O devices by allowing virtual machines to directly access the physical hardware devices. Read More >>
- Change Block Tracking – Use to increase Backup and Recovery times.
- VMXNET Generation 3 – See the feature below
- MSI/MSI-X support (subject to guest operating system kernel support)
- Receive Side Scaling
- IPv6 checksum and TCP Segmentation Offloading (TSO) over IPv6
- VLAN off-loading
- Large TX/RX ring sizes
- IPv6 Support
What is the upgrade process?
VMware Tools must be upgraded before you try to upgrade the Virtual Hardware
The upgrade process is very simple. It can either be done manually or you can automate it using VMware Upgrade Manager.
There are also things that need to be considered before upgrading;
- When you upgrade from virtual hardware version 3 to version 7, the upgrade is irreversible, even if you take a virtual machine backup or snapshot before performing the upgrade.
- Upgraded virtual machines cannot be powered on by an ESX 2.x host, even if relocated to a VMFS2 datastore.
Will upgrading introduce any downtime?
There will always be downtime when upgrading the Virtual Hardware regardless of the Operating System. The VM needs to be Powered Off when initiating the upgrade. Once turned on the OS will detect the new devices and then prompts for a reboot. Failing to reboot will result in the new devices not working correctly.
There will not be any downtime to vCenter or any of your ESX Hosts.
Could there be any issues after the upgrade which may cause the VM to not function correctly?
Using Snapshots give you the option to revert back if there is an issue. You could also run a test. Clone the VM that you wish to upgrade and upgrade the Clone first to see if there are any issues. If there are you can find a resolution for when you upgrade the proper VM.
As always the answer is “It Depends“.
The question you need to ask yourself is: Will the VM make use of the new features offered by Version 7?
- If the answer is Yes, then upgrade. But allow for downtime and the small chance of issues after the upgrade.
- If the answer is No, then don’t upgrade. If it’s not broken why fix it? Don’t make extra work for yourself.
- PCoIP Log Viewer 2.0 - February 15, 2012
- VDI Paging Files — Big? Small? Or Non At All? - February 2, 2012
- VMware View 4.5: Rebalance - May 25, 2011
- VMware View Desktops: IDE or SCSI? BusLogic, LSI Logic or PVSCSI? - February 7, 2011
- vSphere 4.1 HA and DRS Technical Deepdive — Book Review - December 10, 2010
- Is Jumbo Frames Working? - September 24, 2010
- VMware Auto Deploy — Stateless ESXi - September 23, 2010
- VMware MVP — Coming Soon? - September 7, 2010
- Using vMA As Your ESXi Syslog Server - June 1, 2010
- VMware Certified Advanced Professional — VCAP - May 26, 2010