Hyper-Vs integration with Windows is definitely a plus, since almost all IT people are familiar with Windows interfaces.Virtual Volumes makes it possible, for example, to clone, replicate or make a snapshot of a VMDK.
Unquestionably, there are some things vSphere does better than Hyper-V, but there are also areas where Hyper-V does excel over vSphere. While a feature-by-feature comparison would be too exhaustive for an overview, Ill emphasize the most important features in the new vSphere 6.0. Hyper-V Advantages And Disadvantages Download From HereVMware published a technical white paper with a complete list of new vSphere 6.0 features, which you can download from here. The hypervisor can now scale to support up to 64 hosts in a cluster, double the previous limit of 32 hosts per cluster. A VMware 6.0 cluster can accommodate 8,000 virtual machines (VMs) -- a twofold increase over the prior release. A single-host server can now accommodate up to 1,000 VMs. Windows Server 2012 R2 Hyper-V also supports up to 64 nodes per cluster and each cluster can accommodate up to 8,000 VMs. Individual Hyper-V hosts can accommodate up to 320 logical processors and up to 4TB of RAM. For starters, VMware enables central management of accounts and permissions for individual host servers. Hyper-V Advantages And Disadvantages Password Complexity RulesIts also now possible to centrally manage password complexity rules for hosts in a cluster. VMware has also introduced a couple new settings for the management of failed logon attempts with local accounts. For those not familiar with this concept, VMware has a history of introducing a new VM hardware version with each major release. For example, hardware version 9 was introduced with vSphere 5.1 and hardware version 10 was introduced with vSphere 5.5. In Windows Server 2012 R2, Microsoft introduced generation 2 VMs (see Figure 2). These second-generation VMs used different virtual hardware than first-generation VMs. Generation 2 VMs, for example, supported the ability to boot from SCSI virtual hard disks, used UEFI firmware and performed PXE boots from standard network adapters (among other things). Version 11 VMs offer some improvements in the way non-uniform memory access (NUMA) memory is used. When memory is hot-added to a VM, that memory is allocated equally across all NUMA regions. This makes it easier to scale a VM without taking it offline. This virtual NUMA support allows a VM to span multiple NUMA nodes so the VM can scale to support larger workloads (see Figure 4) and can take advantage of NUMA-related performance optimizations. Also, vSphere 6.0 gives administrators the ability to remove unneeded serial and parallel ports. For all practical purposes, Hyper-V doesnt support the use of physical serial or parallel ports by VMs. However, its possible to configure a virtual COM port to communicate with a physical computer through a named pipe (see Figure 5). The supported Windows OSes (complete list available here ) include. With releases prior to vSphere 6.0, when a VMware administrator would have to set up some new VMs, it involved calling or e-mailing the storage administrator and asking them to create a LUN according to certain specifications. Once this LUN was created, the virtualization administrator could create a datastore on the LUN and begin creating VMs. This process might have varied slightly from one organization to the next, but in every case there was abstraction between physical storage and the individual virtual hard disks. This new feature allows VMDK files (VMware virtual hard disks) to natively interact with the physical storage array and allows the physical storage arrays capabilities to be exposed through vCenter. This means a VMware admin can direct the array to create a VMDK that meets a specific set of requirements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |