SysAdmin

Here , i have shared all things as per my knowledge. These all
are sourced from internet and from my knowledge.
Showing posts with label VSphere 5.5. Show all posts
Showing posts with label VSphere 5.5. Show all posts

Monday, 27 January 2014

Virtualization - Comparision - Windows 2012 R2 Vs VMWare

          

For further detail pl visit :


Microsoft
Windows Server 2012 R2 
+ System Center 2012 R2 Datacenter Editions
VMware
vSphere 5.5 Enterprise Plus + vCenter Server 5.5
Notes
Maximum # of Logical Processors per Host
320
320
With vSphere 5.5 Enterprise Plus, VMware has “caught up” to Microsoft in terms of Maximum # of Logical Processors supported per Host.
Maximum Physical RAM per Host
4TB
4TB
With vSphere 5.5 Enterprise Plus, VMware has “caught up” to Microsoft in terms of Maximum Physical RAM supported per Host.
Maximum Active VMs per Host
1,024
512

Maximum Virtual CPUs per VM
64
64
When using VMware FT, only 1 Virtual CPU per VM can be used.
Hot-Adjust Virtual CPU Resources to VM
Yes - Hyper-V provides the ability to increase and decrease Virtual Machine limits for processor resources on running VMs. 
Yes - Can Hot-Add virtual CPUs for running VMs on selected Guest Operating Systems and adjust Limits/Shares for CPU resources. 
VMware Hot-Add CPU feature requires supported Guest Operating System. Check VMware Compatibility Guide for details.

VMware Hot-Add CPU feature not supported when using VMware FT
Maximum Virtual RAM per VM
1TB
1TB
When using VMware FT, only 64GB of Virtual RAM per VM can be used.
Hot-Add Virtual RAM to VM
Yes 
Requires supported Guest Operating System.
Dynamic Memory Management
VMware vSphere 5.5 also supports another memory technique: Transparent Page Sharing (TPS).  While TPS was useful in the past on legacy server hardware platforms and operating systems, it is no longer effective in many environments due to modern servers and operating systems supporting Large Memory Pages (LMP) for improved memory performance.
Guest NUMA Support
Yes
Yes
NUMA = Non-Uniform Memory Access.  Guest NUMA support is particularly important for scalability when virtualizing large multi-vCPU VMs on Hosts with a large number of physical processors.
Maximum # of physical Hosts per Cluster
64
32

Maximum # of VMs per Cluster
8,000
4,000

Virtual Machine Snapshots
Yes - Up to 50 snapshots per VM are supported.
Yes - Up to 32 snapshots per VM chain are supported, but VMware only recommends 2-to-3.


Integrated Application Load Balancing for Scaling-Out Application Tiers
No – Requires additional purchase of vCloud Network and Security (vCNS) or vCloud Suite.

Bare metal deployment of new Hypervisor hosts and clusters
Yes - VMware Auto Deploy and Host Profiles supports bare metal deployment of new hosts into an existing cluster, but does not support bare metal deployment of new clusters.

Bare metal deployment of new Storage hosts and clusters
No

Manage GPU Virtualization for Advanced VDI Graphics
Yes - Server GPUs can be virtualized and pooled across VDI VMs via RemoteFX and native VDI management features in RDS role.
Yes - via vDGA and vSGA features, but requires separate purchase of VMware Horizon View to manage VDI desktop pools.

Virtualization of USB devices
Yes - Client USB devices can be passed to VMs via Remote Desktop connections. Direct  redirection of USB storage from Host possible with Windows-to-Go certified devices.  Direct redirection of other USB devices possible with third-party solutions.
Yes - via USB Pass-through support.

Virtualization of Serial Ports
Yes - Virtual Machine Serial Ports can be connected to Named Pipes on a host.   Named Pipes can then be connected to Physical Serial Ports on a host using free PipeToCom tool.
  
Live Migration of VMs using virtualized serial ports can be provided via 3rd party software, such as Serial over Ethernet and Network Serial Port, or 3rd party hardware, such as Digi PortServer TS and Lantronix UDS1100
Yes - Virtual Machine Serial Ports can be connected to Named Pipes, Files or Physical Serial Ports on a host.  

vMotion of VMs using virtualized serial ports can be supported when using 3rd party virtual serial port concentrators, such as Avocent ACS v6000.
Note that the ability to perform Virtual Machine Live Migration (or vMotion) for VM's with virtualized serial ports requires a third-party option on both solutions compared.
Minimum Disk Footprint while still providing management of multiple virtualization hosts and guest VM's
~800KB - Micro-kernelized hypervisor ( Ring -1 )

~5GB - Drivers + Management ( Parent Partition - Ring 0 + 3 )

Microsoft Hyper-V uses a modern micro-kernelized hypervisor architecture, which minimizes the components needed within the hypervisor running in Ring -1, while still providing strong scalability, performance, VM security, Virtual Disk security and broad device driver compatibility.
~155MB - Monolithic hypervisor w/ Drivers( Ring -1 + 0 )
  
~4GB - Management  ( vCenter Server Appliance - Ring 3 )

VMware vSphere uses a larger classic monolithic hypervisor approach, which incorporates additional code, such as device drivers, into the hypervisor.  This approach can make device driver compatibility an issue in some cases, but offers increased compatibility with legacy server hardware that does not support Intel-VT / AMD-V hardware-assisted virtualization.
Microsoft and VMware each use different approaches for hypervisor architecture.  Each approach offers different advantages as noted in the columns to the left.

See When it comes to hypervisors, does size really matter? for a more detailed real-world comparison.

Frequently, patch management comes up when discussing disk footprints.  See Orchestrating Patch Management for more details on this area.
Boot from Flash
Yes - Supported via Windows-to-Go devices.
Yes

Boot from SAN
Yes - can leverage included iSCSI Target Server or 3rd party iSCSI / FC storage arrays using software or hardware boot providers.
Yes - can leverage 3rd party iSCSI / FC storage arrays using software or hardware boot providers.