VMware vSphere Review

vSphere 5.1 – Lesser publicized, neat improvements.

There are a lot of neat improvements in vSphere 5.1, but it’s worth mentioning some of the neat features that may not be getting as much publicity. Below are some of the features in the release documentation that aren’t in the “What’s New in vSphere 5.1” one-pager, and so-far I haven’t seen nearly enough excitement about thus far. These are features that an engineer will enjoy, but the engineer’s boss might not care so much about.

  1. 32 Nodes Accessing VMDK Simultaneously on VMFS: This is an important improvement for VMware View workloads using Linked Clones as it allows for higher density clusters. Previously, VMFS only supported 8 nodes accessing a VMDK, and to overcome that then the architect had to use NFS. VMFS and NFS now support the same number of nodes to a read-only file with View 5.1 and greater.
  2. Virtual Machine Hardware Compatibility: Instead of simply relying on the virtual hardware version number, virtual machines are now given a Virtual Machine Compatibility. For example, VM Hardware Version 4 is now labeled as “Compatible with VMware ESX 3.x and later“. In addition, Administrators can select a “Default Compatibility Level,” which will be a great feature in mixed version clusters.

  3. Parallel “Multi-threaded” Storage vMotions: Storage vMotion is now capable of performing four simultaneous disk copies. When migrating a virtual machine with five VMDK files, Storage vMotion copies the first four disks in parallel, then starts the next disk copy as soon as one of the first four finish. This will dramatically increase svMotion processes with many disks.
  4. All Paths Down (APD) Events No Longer Break Hostd: Prior to vSphere 5.1, an APD event could cause hostd to become unresponsive as it would permanently retry failing I/O, which would cause hosts to disconnect from vCenter, etc. A new timeout is now being implemented via the Misc.APDHandlingEnable and Misc.APDTimeout global settings. In the event of an APD, after the default 140 seconds subsequent I/O is met with a quick “No_Connect” response preventing hostd and other processes from hanging.
  5. Better Latency Monitoring within Storage I/O Control: A new metric ‘VmObservedLatency’ is available that replaces the datastore latency metric within SIOC. This metric measures the time between receipt of the I/O by the VMkernel from the virtual machine and receipt of the response from the datastore. Previously, SIOC only measured the latency after the IO had left the ESXi host, but it now measures and controls storage workload latency throughout the whole virtualized storage stack.
  6. vCenter Inventory Tagging: Virtual machines can now be tagged with labels for more granular, advanced grouping. For example, Tier-1 applications can be tagged as such while also being tagged as a ‘Sharepoint’ server. This is a relatively simple additions that gives much better sorting capabilities for Virtual Machines.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
2 visitors found this review helpful
kleegeekReal UserTOP REVIEWERTOP 20

Excellent write up! I love vSphere 5.1! Everyone - make sure to update to vSphere 5.1 Update 1a. They fix a bug that affected the Single Sign On component.

13 June 13
Tech Support Staff at a tech company with 1,001-5,000 employeesVendor

Updates always come with better features and bug fixes, hence the reason it is essential to keep all programs and not just vSphere up-to-date. Excellent review that is easy to understand even by users new to this virtualization program.

04 August 13
kapilmalik1983ConsultantTOP REVIEWER

Can we migrate VM machines using vsphere?

05 August 13
Consultant at a tech services company with 501-1,000 employeesConsultant

Any of the levels of vSphere will give you the tools to migrate, yes. This gives you the ability to migrate from host to host and/or datastore to datastore.

14 January 14
kapilmalik1983ConsultantTOP REVIEWER

That's nice to know that using vSphere, we can even migrate datastore to datastore. Is there any size limit for datastore migrations? Or do we need to create multiple datastores of small sizes if we already have a migration plan?

02 May 14
Systems and Security Administrator at a government with 1,001-5,000 employeesReal UserTOP 5LEADERBOARD

One thing I am looking forward to in my upgrade from 5.1 to 5.,5 is the abilty to go beyond a 2TB vmdk. We are looking at the upgrade soon. There were a few problems we had to address with the 2 TB VMDK limitations but now the ability to go beyond this (for certain things) is a huge benefit.

24 July 14
Systems and Security Administrator at a government with 1,001-5,000 employeesReal UserTOP 5LEADERBOARD

Has anyone had any angst when moving from the vSphere client in 5.1 to the web client in 5.5?

24 July 14
Why do you like it?

Sign Up with Email