How a hypervisor works?
A hypervisor is a program that sits above a hardware layer. Sometimes referred to as the host machine. The hypervisor allows multiple operating systems to run as virtual machines (VM) and these are known as guest machines. It is the hypervisors job to carve up the underlying hardware and provide this to each VM depending on the application the VM is running. By doing this, the hypervisor manages system resources far more efficiently than a standalone server with an operating system and can provide extra processing power, memory, disk space and network ports as and when required from the resources available on the host machine.
As a hypervisor can run multiple operating systems and applications, each VM is containerised and cannot interfere with another VM as everything is controlled by the hypervisor. Should a guest operating system require an update the IT manager can update just this VM or all the VM’s running the same operating system.
Creating a VM takes just a few clicks using the hypervisor simply select the following:
- Firstly, choose the guest OS to run the VM.
- How many processors are required?
- How much memory?
- Amount of disk space?
- Number of network ports?
- Set the IP address and login credentials.
The VM will then run above the hypervisor and typically takes a few minutes and appears as a physical machine running in a virtual environment.
Hypervisor Type I or Type II
Many of the most popular hypervisors are type 1 and these are:
- Microsoft Hyper-V
- VMware ESX/ESXi
- Oracle VM server for x86
- Citrix XenServer
All of these are known as bare metal hypervisors and are completely standalone requiring a host server to run.
A type II hypervisor is loaded once an operating system has been installed. The hypervisor then runs within the operating system. Type II hypervisors are:
- VMware workstation
- Microsoft Virtual PC
- Oracle VM VirtualBox
Type 1 hypervisors are more secure than type II as they are not reliant on an operating system, they are faster and more efficient at managing resources as they directly interface with the system resources.
Hypervisor Data Protection
The hypervisor became a very efficient and feature-filled solution. With the advent of tools, including VMware vMotion, HA, and DRS, users obtained the ability to provide VM high availability and migrate compute workloads dynamically. The only caveat was the reliance on centralised storage, causing the two paths to merge.
Many hypervisors allow the creation of clone volumes or create snapshots that can be mounted as read only or read/write. It is normal to backup the hypervisor rather than each VM due to the difficulties in managing system resources through the host machine, although this can be done by loading an agent on each VM. Another method is to use storage-based replication to replicate the storage volumes across the network and then migrate or copy the VM to another host machine. The last method is to let the hypervisor perform the replication such as VMware vSphere or Hyper-V Replica.
Hypervisors for VDI
Virtual desktop hypervisors allow you to run 100’s or 1,000’s of desktop machines to provide either Persistent VDI that provides the user with customised desktops that can be saved. In addition, Non-persistent VDI provides the same desktop every time the machine is rebooted.
In both instances the desktop image is delivered over a network to an endpoint device. The user experience is that they are using a normal desktop computer as all the processing is done on the server. An endpoint device could be a traditional PC, thin client or mobile device.
A VDI infrastructure brings benefits to the business by extending the lifespan of ageing desktop machines. Another key benefit is security, as no data resides on the endpoint device. Also, anti-virus software and protection is run on the server, rather than individual client machines. Finally, management is far simpler as the same desktop image is deployed across the entire VDI estate.
Whilst VDI provides many benefits including reduced desktop deployments costs. The VDI data now resides centrally on storage arrays and this can increase significantly based on the number of users. Another downside could be network performance as VDI isn’t particularly good at handling motion on the desktop, although there are solutions starting to emerge for collaborative working on the desktop using video, 3D, CGI, CAD/CAE and animation.
The world’s most popular virtualisation software is VMware with the largest market share This is followed by Microsoft Hyper-V, although this is likely to increase with Windows Server 2016. VMware is licensed normally by CPU and then you pay for annual support/software updates and additional software functionality. Microsoft provides Hyper-V as part of it’s operating system and is priced per-core rather than per CPU as was the case before. It is dependent on the Windows Server 2016 edition and pricing can be found below:
Depending on the datacentre environment running, the cost of deploying and maintaining a virtual environment could be expensive.
There are free hypervisors available one of the most popular Linux KVM https://www.linux-kvm.org/page/Main_Page and this is open source software developed by Linux programmers.
A business might want to migrate their current hypervisor to an alternative and converting VMs to another hypervisors format could be problematic. To overcome this a company, we work with StarWind provides V2V Converter and allows for migrations of the following VM formats: VMDK, VHD/VHDX. StarWind V2V Converter supports all industry-standard hypervisors including Microsoft Hyper-V, VMware ESXi, Citrix XenServer, and KVM (coming soon). By converting VMs from and to any selected format, it allows easily migrating between different hypervisors. Best of all it’s FREE available to download from here https://www.starwindsoftware.com/converter.
Consolidation in the datacentre
Before virtualisation, the drive to reduce the complexities of managing multiple standalone servers had begun with the advent of multi-core processors. For the first time multiple applications could be run on a single server. The next phase was to move away from DAS (direct attached storage) to a SAN/NAS infrastructure sometimes referred to as storage virtualisation. This meant servers in the datacentre could be much smaller 1U/2U and the storage for these servers would be highly redundant and provide greatly increased performance.
The next phase was the introduction of virtualisation provided by VMware in 1999 and was VMware Workstation. So, the hypervisor isn’t new, and it has been with us for nearly 20 years.
One of the key problems with a hypervisor is performance. If you are running 200 VMs then each VM is going to be making I/O requests on the server and storage, this is where many hypervisor deployments fail.
How a virtualised environment is configured is based on several factors:
- Number of available CPU compute cores
- Amount of available memory per server
- Number of Ethernet network switches
- Number of storage area network switches
- Number of required network ports
- Ethernet network speed
- Storage network speed
- Single or multiple storage pools
- Number of storage controllers
- Types of storage
What is a hypervisor?
Virtualisation provides huge savings in data management, power, cooling, storage utilisation, computing resources and data availability. The issue is the hypervisor is software that interacts with the physical hardware and this could be a problem as many virtualised deployments are a DIY affair. To provide a completely seamless virtualised environment the hypervisor needs to be able to directly interact with all below:
- Network Switches and Ports
- Data Storage
This is called “hyper convergence” and everything is controlled through the hypervisor. So rather than take the DIY approach there are several hyper-converged infrastructures (HCI) that allow control of the complete software and hardware stack. HCI are faster to deploy, fully tested and approved and work out of the box. Purchasing an HCI involves us knowing how many VMs will you be running and type of workload i.e. Office applications, database, OLTP etc?
The problem with hypervisors
The hypervisor typically resides on server hardware, that in turn sits on a network that connects to pools of storage. Each one of these component parts – software, storage, networking and storage has a management layer and this adds to the complexity.
Each component needs to be individually upgraded and this takes time. If you’ve worked with VMware, you are most likely well aware of how complex the VMware ecosystem has become. The latest version of the VMware Product Guide is over 70 pages long and includes dozens of products and more than twenty bundles and suites to choose from. Due to this complexity, VMware publishes a knowledge base article that defines the multi-step process and order of operations required just for software upgrades. Though sold in bundles or suites, most of the tools are loosely integrated independent software packages (many from acquisitions) with their own management consoles and software life-cycles.
All of these component parts have their own security feature set and functionality.
The network bottleneck
Flash arrays have made a massive change in the way applications perform with colossal IOPS and instantaneous performance running in to the 1,000 MB/s! Therefore if we take a normal SSD drive with a read speed of 500MB/s and write speed of 350MB/s the table below shows how many drives it would take to saturate the network.
|SSDs required to saturate network bandwidth|
|Controller Connectivity||Available Network Bandwidth||Read I/O||Write I/O|
|Dual 4Gb FC||8Gb = =1GB||2||3|
|Dual 8Gb FC||16Gb = = 2GB||4||5|
|Dual 16Gb FC||32Gb = = 4GB||8||11|
|Dual 32Gb FC||64Gb = = 8GB||16||22|
|Dual 1Gb ETH||2Gb == 0.25GB||1||1|
|Dual 10Gb ETH||20Gb == 2.5GB||5||7|
So these figures might surprise you. Now the latest generation of flash technology NVMe is on average 5x the performance of an SSD, divide the numbers from the table above by 5 and this is how many next generation drives will saturate the network! Moving on from NVMe, we have 3D XPoint memory currently and development and due to ship within the next 2-3 years. The performance of this memory is 1,000x faster than NVMe. As we adopt these newer technologies the network connectivity will become more of an issue for both latency and network bandwidth.
The next phase of Virtualisation
Whilst HCI go beyond the initial deployments of a virtualised infrastructure there are limitations how far you can scale for performance and capacity as the HCI is based on component blocks i.e. data storage arrays, network switches, servers etc, all these component parts cause latency and network bandwidth issues.
We are a Nutanix partner and they take a completely different approach to building an HCI. Whilst Nutanix can use hypervisors from Microsoft Hyper-V, VMware ESXi and Citrix XenServer it also offers its own free hypervisor Acropolis, so no additional licensing costs.
Nutanix is a converged storage, compute and virtualisation platform that provides a distributed and massively scalable cluster ready to run any application out of the box.
With Acropolis and AHV, virtualization is tightly integrated into the Enterprise Cloud OS rather than being layered on as a standalone product that needs to be licensed, deployed and managed separately.
Common tasks such as deploying, cloning and protecting VMs are managed centrally through Nutanix Prism, rather than utilising disparate products and policies in a piecemeal strategy.
Acropolis provides enterprise-grade VM-centric storage for virtualised applications. Unlike traditional storage solutions that were built in a pre-virtualization era, operations in Acropolis are optimised to work at a granularity of a single VM or vDisk. Additionally, complex storage operations such as LUN provisioning, zoning and masking are non-existent in Acropolis enabling deployment of highly available storage with just a few clicks.
Nutanix takes a completely new and different approach to overcome the issues around latency, bandwidth, scalability and performance. Nutanix uses the idea of compute nodes as building blocks allowing you to scale for performance and capacity as and when required.
Each Nutanix compute node contains:
- Computing power
- Network ports
The beauty about Nutanix is that not all compute nodes need to be identical, they don’t even need to be from the same vendor, although we advise that they are for support purposes.
Do you really care about the Hypervisor?
No not really, providing your applications are running and performing as expected it shouldn’t really matter.
Nutanix virtualisation offers an attractive alternative when streamlining datacentre operations and driving costs out of the datacentre. It’s done with Nutanix AHV, a built in, license-free hypervisor delivering virtualisation capabilities needed by the most demanding applications.
With thousands of deployments worldwide, AHV provides an open platform for virtualisation, network virtualisation, security, and application mobility. When combined with comprehensive operational insights and virtualisation management from Nutanix Prism, Nutanix provides a complete solution for virtualisation and enterprise cloud.
By adopting AHV, your organisation can not only eliminate the direct costs associated with the hypervisor licensing but drive down soft costs and reduce the OpEx associated with virtualisation.
The Nutanix Enterprise Cloud OS offers multiple advantages versus VMware vSphere:
- Platform Security
- Application Security • Analytics
- Automation & Orchestration
If you would like to know “How to stop paying for Virtualisation” by Nutanix please complete our form or call us on 01256 331614.
[wpforms id=”1101″ title=”false” description=”false”]