Skip to main content

vSphere 5.1 Vs vSphere 5.5


Features
vSphere 5.1
vSphere 5.5
Physical CPUs per host
160
320
Physical RAM per host
2  TB
4 TB
NUMA nodes per host
8
16
Maximum vCPUs per host
2048
4096
VMDK Size
2TB
62 TB
Max Size of Virtual RDM
2TB
62 TB
VM Hardware Version
9
10
40 GBps physical Adapter support
No
yes
ESXi Free version RAM limit
32 GB
 unlimited
ESXi Free version maximum vSMP
8-way virtual SMP
8-way virtual SMP
16 GB fibre channel End-to-End support
Support to run these HBAs at 16Gb. However, there is no support for full, end-to-end 16Gb connectivity from host to array.
Yes
APP HA
No
Yes
vFlash Read Cache support
No
Yes
VMware VSAN support
No
Yes
Expanded v-GPU and G-GPU support
only NVIDIA
NVIDIA, AMD and Intel GPU
vCenter Server Appliance With
 Embedded Database support upto
5 Hosts and 50 Virtual
 Machines
100 Hosts and 3000 Virtual
Machines
Microsoft Windows 2012 Cluster Support
No
Yes
PDL (Permanent Device Loss) AutoRemove
No
Intoduced in vSphere 5.5
Graphics acceleration support for Linux
Guest OS
No
Yes
Hot-pluggable SSDPCIe devices
No
Yes
Support for Reliable Memory Technology
No
Yes
CPU C-state Enhancement
Host power management leveraged only the performance state (P-state), which kept the
processor running at a lower frequency and voltage
Processor power state (C-state)
also is used, providing additional power savings
 and increased Performance
 LSI SAS support for Oracle Solaris 11 OS
No
Yes
vSphere Big Data Extensions
No
Yes
SATA-based virtual device nodes via
AHCI (Advanced Host Controller Interface) support
No
Yes (Support upto 120
devices per VM)
Improved LACP Support
one LACP group per
distributed switch
Supports up to 64
Multiple point-in-time replicas
vSphere Replication kept
only the most recent copy
of a virtual machine
Version 5.5 can keep up to
24 historical snapshots


Comments

Post a Comment

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 ðŸ”¹ Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Post a Comment
Read more
  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
Post a Comment
Read more