Home > Blogs > VMware vSphere Blog


A Summary of What’s New in vSphere 5.5

On August 26th at VMworld 2013 VMware announced vSphere 5.5, the latest release of  VMware’s industry-leading virtualization platform.  This latest release includes a lot of improvements and many new features and capabilities.  In an effort to try and get my head around all this exciting new “stuff” I decided to go through the what’s new paper and compile a brief summary (well, relatively brief anyway).

Here’s the list I came up with.  I’m sure I missed some things, but this list should help you get started with learning about what’s new in vSphere 5.5.

Summary of new features and capabilities available in vSphere 5.5

  • Doubled Host-Level Configuration Maximums – vSphere 5.5 is capable of hosting any size workload; a fact that is punctuated by the doubling of several host-level configuration maximums.  The maximum number of logical CPUs has doubled from 160 to 320, the number of NUMA nodes doubled from 8 to 16, the number of virtual CPUs has doubled from 2048 to 4096, and the amount of RAM has also doubled from 2TB to 4TB. There is virtually no workload that is too big for vSphere 5.5!
  • Hot-pluggable PCIe SSD Devices – vSphere 5.5 provides the ability to perform hot-add and remove of SSD devices to/from a vSphere 5.5 host.  With the increased adoption of SSD, having the ability to perform both orderly as well as unplanned SSD hot-add/remove operations is essential to protecting against downtime and improving host resiliency.
  • Improved Power Management – ESXi 5.5 provides additional power savings by leveraging CPU deep process power states (C-states).   By leveraging the deeper CPU sleep states ESXi can minimizes the amount of power consumed by idle CPUs during periods of inactivity.  Along with the improved power savings comes additional performance boost on Intel chipsets as turbo mode frequencies can be reached more quickly when CPU cores are in a deep C-State.
  • Virtual Machine Compatibility ESXi 5.5 (aka Virtual Hardware 10) – ESXi 5.5 provides a new Virtual Machine Compatibility level that includes support for a new virtual-SATA Advance Host Controller Interface (AHCI) with support for up to 120 virtual disk and CD-ROM devices per virtual machine.   This new controller is of particular benefit when virtualizing Mac OS X as it allows you to present a SCSI based CD-ROM device to the guest.
  • VM Latency Sensitivity – included with the new virtual machine compatibility level comes a new “Latency Sensitivity” setting that can be tuned to help reduce virtual machine latency.  When the Latency sensitivity is set to high the hypervisor will try to reduce latency in the virtual machine by reserving memory, dedicating CPU cores and disabling network features that are prone to high latency.
  • Expanded vGPU Support – vSphere 5.5 extends VMware’s hardware-accelerated virtual 3D graphics support (vSGA) to include GPUs from AMD.  The multi-vendor approach provides customers with more flexibility in the data center for Horizon View virtual desktop workloads.  In addition 5.5 enhances the “Automatic” rendering by enabling the migration of virtual machines with 3D graphics enabled between hosts running GPUs from different hardware vendors as well as between hosts that are limited to software backed graphics rendering.
  • Graphics Acceleration for Linux Guests – vShere 5.5 also provides out of the box graphics acceleration for modern GNU/Linux distributions that include VMware’s guest driver stack, which was developed by VMware and made available to all Linux vendors at no additional cost.
  • vCenter Single Sign-On (SSO) – in vSphere 5.5 SSO comes with many improvements.   There is no longer an external database required for the SSO server, which together with the vastly improved installation experience helps to simplify the deployment of SSO for both new installations as well as upgrades from earlier versions.   This latest release of SSO provides enhanced active directory integration to include support for multiple forest as well as one-way and two-way trusts.  In addition, a new multi-master architecture provides built in availability that helps not only improve resiliency for the authentication service, but also helps to simplify the overall SSO architecture.
  • vSphere Web Client – the web client in vSphere 5.5 also comes with several notable enhancements.  The web client is now supported on Mac OS X, to include the ability to access virtual machine consoles, attach client devices and deploy OVF templates.  In addition there have been several usability improvements to include support for drag and drop operations, improved filters to help refine search criteria and make it easy to find objects, and the introduction of a new “Recent Items” icon that makes it easier to navigate between commonly used views.
  • vCenter Server Appliance – with vSphere 5.5 the vCenter Server Appliance (VCSA) now uses a reengineered, embedded vPostgres database that offers improved scalabilityI wasn’t able to officially confirm the max number of hosts and VMs that will be supported with the embedded DB.  They are targeting 100 hosts and 3,000 VMs but we’ll need to wait until 5.5 releases to confirm these numbers.  However, regardless what the final numbers are, with this improved scalability the VCSA is a very attractive alternative for folks who may be looking to move a way from a Windows based vCenter.
  • vSphere App HA – App HA brings application awareness to vSphere HA helping to further improve application uptime.  vSphere App HA works together with VMware vFabric Hyperic Server to monitor application services running inside the virtual machine, and when issues are detected perform restart actions as defined by the administrator in the vSphere App HA Policy.
  • vSphere HA Compatibility with DRS Anti-Affinity Rules –vSphere HA will now honor DRS anti-affinity rules when restarting virtual machines.  If you have anti-affinity rules defined in DRS that keep selected virtual machines on separate hosts, VMware HA will now honor those rules when restarting virtual machines following a host failure.
  •  vSphere Big Data Extensions(BDE) – Big Data Extensions is a new addition to the VMware vSphere Enterprise and Enterprise Plus editions.  BDE is a vSphere plug-in that enables administrators to deploy and manage Hadoop clusters on vSphere using the vSphere web client.
  • Support for 62TB VMDK – vSphere 5.5 increases the maximum size of a virtual machine disk file (VMDK) to 62TB (note the maximum VMFS volume size is 64TB where the max VMDK file size is 62TB).  The maximum size for a Raw Device Mapping (RDM) has also been increased to 62TB.
  • Microsoft Cluster Server (MCSC) Updates – MSCS clusters running on vSphere 5.5 now support Microsoft Windows 2012, round-robin path policy for shared storage, and iSCSI and Fibre Channel over Ethernet (FCoE) for shared storage.
  • 16Gb End-to-End Support – In vsphere 5.5 16Gb end-to-end FC support is now available.  Both the HBAs and array controllers can run at 16Gb as long as the FC switch between the initiator and target supports it.
  • Auto Remove of Devices on PDL – This feature automatically removes a device from a host when it enters a Permanent Device Loss (PDL) state.  Each vSphere host is limited to 255 disk devices, removing devices that are in a PDL state prevents failed devices from occupying a device slot.
  • VAAI UNMAP Improvements – vSphere 5.5 provides  and new “esxcli storage vmfs unmap” command with the ability to specify the reclaim size in blocks, opposed to just a percentage, along with the ability to reclaim space in increments rather than all at once.
  • VMFS Heap Improvements – vSphere 5.5 introduces a much improved heap eviction process, which eliminates the need for large heap sizes.  With vSphere 5.5 a maximum of 256MB of heap is needed to enable vSphere hosts to access the entire address space of a 64TB VMFS.
  • vSphere Flash Read Cache – a new flash-based storage solution that enables the pooling of multiple flash-based devices into a single consumable vSphere construct called a vSphere Flash Resource, which can be used to enhance virtual machine performance by accelerating read-intensive workloads.
  • Link Aggregation Control Protocol (LACP) Enhancements – with the vSphere Distributed Switch in vSphere 5.5 LACP now supports 22 new hashing algorithms, support for up to 64 Link Aggregation Groups (LAGs), and new workflows to help configure LACP across large numbers of hosts.
  • Traffic Filtering Enhancements – the vSphere Distributed Switch now supports packet classification and filtering based on MAC SA and DA qualifiers, traffic type qualifiers (i.e. vMotion, Management, FT), and IP qualifiers (i.e. protocol, IP SA, IP DA, and port number).
  • Quality of Service Tagging – vSphere 5.5 adds support for Differentiated Service Code Point (DCSP) marking.  DSCP marking support enables users to insert tags in the IP header which helps in layer 3 environments where physical routers function better with an IP header tag than with an Ethernet header tag.
  • Single-Root I/O Virtualization (SR-IOV) Enhancements – vSphere 5.5 provides improved workflows for configuring SR-IOV as well as the ability to propagate port group properties to up to the virtual functions.
  • Enhanced Host-Level Packet Capture – vSphere 5.5 provides an enhanced host-level packet capture tool that is equivalent to the command-line tcpdump tool available on the Linux platform.
  • 40Gb NIC Support – vSphere 5.5 provides support for 40Gb NICs.  In 5.5 the functionality is limited to the Mellanox ConnectX-3 VPI adapters configured in Ethernet mode.
  • vSphere Data Protection (VDP) – VDP has also been updated in 5.5 with several great improvements to include the ability to replicate  backup data to EMC Avamar,  direct-to-host emergency restore, the ability to backup and restore of individual .vmdk files, more granular scheduling for backup and replication jobs, and the ability to mount existing VDP backup data partitions when deploying a new VDP appliance.  For more information about these new features as well as more information about VDP vs. VDP advanced check out Jeff Hunter’s recent blog post.

As you can see this is an impressively long summary of new features and capabilities being provided with vSphere 5.5.  I’m looking forward to leveraging many of these in my vSphere environments.

For additional information about these features check out the What’s New in vSphere 5.5 Platform white paper.

62 thoughts on “A Summary of What’s New in vSphere 5.5

  1. Vamshi Meda

    With the release of vSphere 5.5, vCenter Server
    Appliance now uses a reengineered, embedded vPostgres database that can now support as many as 500
    vSphere hosts or 5,000 virtual machines.

    1. Kyle GleedKyle Gleed Post author

      Thanks for the comment. Note that 5.5 has not officially released yet and as such some numbers may change slightly. With regard to the VCSA scalability I believe they are targeting 100 hosts and 3,000 VMs, but we’ll need to wait for 5.5 to release to get the official numbers. The white paper is in the process of being updated.

    1. Kyle GleedKyle Gleed Post author

      Hi, sorry I don’t know when 5.5 will release. Check back, as soon as I find out I’ll post a note on the vSphere blog.

  2. Pingback: What’s New in vSphere 5.5 Platform–Quick Reference | VMware vSphere Blog - VMware Blogs

    1. Kyle GleedKyle Gleed Post author

      Hi Arun, we did a lot of work during the beta testing upgrades from both 4.x and 5.0 (pre-SSO) as well as 5.1 (SSO). We even went so far as to hand carry the 5.5 beta bits out to customer sites and test SSO in their environments. Things went very well and feedback has been very positive. I’m sure you will find it’s greatly improved.

      1. iwan rahabok

        Good to hear that. Definitely useful to know the upgrades works on 4.x and 5.0. I do have quite a number of customers on these versions.
        For 5.0, does it have to be 5.0 with the latest patch/updates?
        For 4.1, does it have to be 5.0 with the latest patch/updates?
        Thanks from Singapore.
        e1

  3. Arun Raju

    Another query about vSphere Client based on C#. Has it been deprecated in this release making the vSphere web client the only way of accessing vSphere ?

    1. Kyle GleedKyle Gleed Post author

      Hi Arun, No, the C# client has not been deprecated in 5.5. It’s status is largely the same as with 5.1. You still need to use the C# client to connect to individual ESXi hosts, to remediate hosts with Update Manager (can do compliance scanning from the Web UI) and for SRM. There are other plug-ins that are still being converted over to the web client as well. However, do keep in mind that much of the new functionally introduced with 5.5 will require use of the Web Client, so you definitely want to get started with learning and using the Web client.

  4. angelo

    I read that ESXi 5.5 free edition is still limited to 8-way vCPU per VM. How about Essentials and Standard 5.5 license, does the 8-way vCPU still applies?

    1. Kyle GleedKyle Gleed Post author

      No, vCPUs/VM are no longer a licensed restriction with paid vSphere editions. Yes, we still limit the free edition (vSphere Hypervisor) with same restrictions as in 5.1.

      1. Steven Cheng

        Do you have any document stating that the restriction of vCPU is removed in vSphere 5.5?

          1. Davy

            Hi Kylee,

            Sorry i can’t find the information in the doc that explain all paid vsphere license can support up to 64 vCPU explicitly. Is there any doc that stated it explicitly?

            Thanks alot

    1. Kyle GleedKyle Gleed Post author

      VSAN is available as a beta feature in 5.5. As it’s not a fully supported feature I didn’t want to call it out. Full VSAN support in 5.5 is expected to be added shortly after the initial release.

  5. Pingback: Welcome to vSphere-land! » vSphere 5.5 Link-O-Rama

  6. Pingback: A Summary of What’s New in vCloud Director 5.5 | VMware vSphere Blog - VMware Blogs

  7. Peter

    In terms of the C# client, I wonder if there is a document covering what is supported in the “fat” client and what not – especially considering the fact that there are differences between the two. In other words I am sure most people wouldn’t know what are the differences between the two.

  8. Pingback: VMware unwraps vSphere 5.5 – Whats in it for your Datacenter? | Tech Talk

  9. Pingback: What’s New in vSphere 5.5 – Quick Reference | The VS Blog

    1. Kyle GleedKyle Gleed Post author

      Yes, the first item on the list calls out the new ESXi configuration maximums. Number of logical CPUs has doubled from 160 to 320 and the amount of memory has doubled from 2TB to 4TB.

  10. here

    Does anyone know if in version 5.5 Fault Tolerance (FT) would accept more than 1 CPU now? up to 5.1 we could only designate 1 CPU.
    thanks!

      1. here

        Thanks Kyle,
        We were really looking forward on having this improvement on this release.. we were told that ‘maybe’ would be on 5.5..
        maybe the next one…

      2. Chris

        @Kyle

        I attended breakout session BCO506 this year at VMworld and it discussed protecting SMP VMs using FT. The description of the session is:

        VMware vSphere® Fault Tolerance (VMware FT) for multiprocessor virtual machines. This new technology allows continuous availability of multiprocessor virtual machines with literally zero downtime and zero data loss, even surviving server failures, while staying completely transparent to the guest software stack, requiring absolutely no configuration of in-guest software. In this technical preview, we will outline the virtues of VMware FT, provide a detailed look at the new technology enabling VMware FT for multiprocessor virtual machines, offer guidance on how to plan and configure your environments to best deploy these capabilities, examine performance data and showcase a demo of the technology in action.

        Why are you stating that SMP FT is not supported in 5.5?

        Thanks,

        Chris

        1. Kyle GleedKyle Gleed Post author

          Hi Chris, The VMworld session was a technology preview showcasing a future capability that is not yet available. vSphere 5.5 still only supports uni-processor FT. Look for SMP FT to come in a future release.

  11. Stefan Lasiewski

    Thank you for this great summary. I have a few questions:

    With vSphere 5.1 and earlier, there were still many things which required (or strongly encouraged) a Windows machine. vCenter needed a SQLServer (Windows), some vCenter components wanted Active Directory, etc.

    My site desires to have as few Windows machines as possible. We have an LDAP cluster and don’t need AD. We’re perfectly capable of running MySQL or PostgreSQL on a Linux machine.

    The vCenter Server Appliance (VCSA) is quite attractive, but does it completely eliminate the need for Windows? Can I set up vCenter Server on a Linux machine myself, or do I need to use the VCSA?

    1. Kyle GleedKyle Gleed Post author

      There is no separate installer for vCenter on Linux. There are two options – install on Windows or deploy the appliance.

      There is no windows server requirement when you use the appliance. You can run the appliance with the embedded DB, which now scales up to 300 hosts, 1,000 VMs with vSphere 5.5. Or you can run the appliance with an external Oracle DB, which provides full scalability up to the documented vCenter configuration maximums.

  12. docs

    I hope this time VMWARE can clean-up/update the documentation/knowledge base before releasing the product…. In the past the KB lags months behind and there are so many errors in documentations making the product unsupportable…

  13. bhanu

    This is with reference RDM where it is mentioned as support for 62TB is that specific to virtual compatibility mode as if i am not wrong, RDM in physical compatibility mode was enhanced to support 64TB in vsphere 5.1.

  14. Pingback: VMware vSphere 5.5 Enhancements That DBAs Should Care About | Technobabble by Klee

  15. Enrique Hernandez

    Is the upgrade path from vCenter v5.1 to vCenter v5.5 a straight through task? or is it like an upgrade from v4.1?

    1. Kyle GleedKyle Gleed Post author

      Yes, in place upgrades are very straight forward. If you have all your vCenter components running on the same VM/Server, just use the Simple Install.

  16. Pingback: New features and capabilities available in vSphere 5.5 | Ramnathgr's Blog

  17. Dirk

    MSCS “died” with Server 2008 R2. The nomenclature is now Failover Clustering. VMware should reference the new nomenclature to match the feature in Server 2012, continuing to call it MSCS will just confuse folks.

  18. Eduardo Lee

    One question: I can configure Fault Tolerance (FT) using only local disks of my hosts?
    Example: I have 4 hosts with only internal disks. (An internal datastore per host)
    My license allows me to configure HS and DRS but not having shared storage, do not know if it is possible to configure FT.
    Please comment.
    thanks

  19. Christopher

    I had two questions that I can’t seem to find answers to and I’m hoping you guys can help out.

    1) Whats the recommended memory that I should reserve for the host (OS).

    2) With vCenter Server Appliance (vCSA) what do I “loose” moving from a Windows install to an application. In the past 4x/5x there were things that only worked if you had vCenter installed on a Windows box. Just yesterday Splunk told me that they only support Windows installs for some things of thiers.
    For instance, we would still need a “windows” box for the SQL server, so we aren’t gaining by not having to purchase a Windows OS license.
    Will vCenter Operations Manager still work with the vApp? I’ve purchased this but not installed yet. Waiting for upgrade from 5x to 5.5.
    I’ll have to start running a vMA (Management Assistant) now.

    1. Kyle GleedKyle Gleed Post author

      The recommended “minimum” memory for ESXi 5.5 hosts is 4GB. For more info on memory management with ESXi check out these docs:

      http://www.vmware.com/files/pdf/mem_mgmt_perf_vsphere5.pdf

      http://pubs.vmware.com/vsphere-51/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-51-resource-management-guide.pdf

      The following features are not yet supported by the VCSA (5.5):
      - No MSSQL DB
      - No vCenter Heartbeat
      - No Linked Mode
      - No IPV6

      Note that with vCenter 5.5 the VCSA can support up to 300 hosts and 1,000 VMs with the embedded DB. So for configurations of this size there is no need for an external DB. Also, an Oracle DB running on Linux is supported with the VCSA.

      vC Ops does come with a vApp. When you deploy the vApp it will instantiate two VMs – a UI VM and an Analytics VM.

  20. Pingback: Yet Another VCAP-DCA post – Sección 1 – Objetivo 1.1 / Parte 2 | Chubascos Blog

  21. Pingback: Tổng quan VMWare vSphere . | Chieu's space

Comments are closed.