Windows Client-Side Hypervisor
l The client-side Hypervisor known as Client Hyper-V was introduced in Windows 8 Operating system. In Windows 10, the Client-side Hyper-V has got its features enhanced.
Need for client Hyper-V-
l Client Hyper-V is used to test or perform demo of operating system features or particular application software.
l Client Hyper-V can also be used to Run a legacy application that are not supported by Windows 10 .
It is used for User support and Troubleshooting.
Features of Client Hyper-V are :
l Client Hyper-V supports 32 bit or 64-bit Virtual Machines.
l Used for storage migration or can also be used to create a virtual storage pool.
l Client Hyper-V uses VHD with maximum limit 2TB or VHDX with maximum limit of 64 TB software disk files.
l It can use local software Disk or LAN based storage also known as NAS Network Attached Storage.
l Client Hyper-V supports Import and Export of the VMs to Server Hyper-V or any other machines Client Hyper-V.
Client Hyper-V Requirements -
The Client Hyper-V Requirements are as follows :
l A 64-bit CPU with assisted virtualization like Intel VTx or AMD-V is required along with a 64- bit version of Windows 10.
l SLAT, Second Level Address Translation, is a CPU feature required for virtualization. It is also known as nested paging.
l The machine must have 4GB or higher RAM.
l Adequate Disk Space to Store the Operating System and the Virtual Machines.
l Since, virtual machines share memory with the Hyper-V host, you will need to provide enough memory to handle the expected virtual workload.
Installation of Hyper-V feature in Windows 10-
The various methods to install Hyper-V feature in Windows 10 are : l Method 1 : Enable the Hyper-V feature inside the answer file that is used during the Hyper-V deployment.
l Method 2 : Enable the Hyper-V feature using PowerShell command.
l Method 3 : Enable the Hyper-V feature from Programs and Features Control Panel.
Hyper-V Manager
l Post-installation of the Hyper-V feature, you get a MMC, Microsoft Management Console, snap- in, named as HyperV manager.
l To open Hyper-V Manager,
l Open Run > virtmgmt.msc OR l Windows 10 Search, type “Hyper-V manager”.
Hyper-V Generations -During the creation of new Virtual Machine, the New VM creation Wizard asks to select the Generation type of the VM. There are 2 types of VM Generations:
Generation 1 VM
l It consists of IDE and SCSI, Small Computer System Interface controller, note that a controller is used to attach Virtual Hard Disks. l It consists of Non-Secure BIOS boot.
l COM port and Virtual Floppy is available to support legacy machines.
l Gen 1 VMs support Operating system from Windows XP and higher.
Generation 2 VM :
l IDE controller is not accepted as the new generation of hardware does not support IDE technology.
l Generation 2 VMs support UEFI Boot. The secure boot option is available and can be enabled. The benefit of secure boot is, during booting if the operating system is not verified, system will not start, and this is useful for prevention on rootkit virus.
l COM port and Floppy technology is obsolete and are unacceptable in generation 2 VMs.
l Generation 2 supports Windows 8 and higher OS that has 64-bit architecture.
Hyper-V Disk Options-
Fixed Disk -Fixed Disk option uses maximum space. It is faster in indexing and has no fragments. Remember more fragmented data leads to slower performance of disk. Fixed Disk is recommended for business-critical servers that host databases like ERP, SQL etc.
l Dynamic Disk- It starts with small, grows as needed. The size increases ondemand, with a maximum limit size as decided by the administrator. Note Differencing is the default option while creating virtual hard disk.
Hyper-V Networking-
l A virtual Switch is a virtual device with an objective to connect VM to VM, and VM to Physical Host.
l Various networking options, virtual switches, available in Hyper-V are:
l External Switch
l Internal Switch
l Private Switch
External Switch : It enables communication between virtual machines, and from Virtual Machine to Physical Host or other machines connected through Physical network.
Internal Switch : It enables communication between virtual machines and from virtual machines to the physical host.
Private Switch : It enables the communication between virtual machines on the same physical host. Take a look at the image, it illustrates the various virtual switch options available in Client Hyper-V.
Comments
Post a Comment