- 1 Creating Azure Virtual Machines Quickly and Painlessly
- 2 Tips and Considerations When Creating Virtual Machines in Azure
- 3 The End of the Road for Windows Server 2003 and 2008
- 4 Move-VM, Move-VMStorage and Compare-VM PowerShell cmdlets for Hyper-V
- 5 Key Considerations for WSUS 6.2 on Windows Server 2012 R2
- 1 Red Hat Enterprise Linux 7.2 Enters Beta with Improved Container Support
- 2 VMware CEO Pat Gelsinger Gives VMworld 5 Imperatives for Success
- 3 VMware vSphere Integrated Containers Previewed at VMworld
- 4 Worldwide Server Revenues Top $13.5 Billion in 2Q15
- 5 Blue Box OpenStack Lands on IBM Softlayer Servers
Hyper-V 2012 R2: Pros and Cons of Generation 1 vs. Generation 2 VMs
Microsoft recently announced Windows Server 2012 R2 during TechED 2013, with general availability expected by the end of the year. With Windows Server 2012 R2, a number of new features and improvements over existing ones have been introduced for Hyper-V running on the 2012 R2 release.
In earlier versions of Hyper-V, it was not possible to boot a Virtual Machine from a SCSI Virtual Hard Drive. It was also not possible to copy files from a Hyper-V Host to virtual machines without having a network connection in the virtual machine.
In fact, the Hyper-V BIOS was not aware of SCSI Controllers unless you installed the Integration Services component. In Virtual Machines running on Windows Server 2012 and earlier, the Hyper-V BIOS only supported legacy drives such as IDE Controller and Legacy Network Adaptors, which allowed a virtual machine to boot only from a Legacy IDE Controller.
Starting with Windows Server 2012 R2, there are two types of Hyper-V Boot architectures available: Hyper-V BIOS and Hyper-V Unified Extensible Firmware Interface (UEFI) BIOS. Hyper-V running on Windows Server 2012 R2 supports two types of Generation Virtual Machines now: Generation 1 and Generation 2.
A virtual machine created with Generation 1 supports legacy drivers and uses Hyper-V BIOS-based architecture. Hyper-V BIOS-based virtual machines can only initialize IDE Controller for Operating System to initialize a file system, which is shown in the below image:
On the other hand, a virtual machine created with Generation 2 supports UEFI-based architecture, in which a subset of Integration Service components has been included to allow SCSI Controller to initialize before the Operating System starts loading. This is shown in the below image:
What you see in the above screenshot is that the Generation 2 Virtual Machine no longer loads the legacy drivers (IDE and Legacy Network Adaptors). A majority of the legacy drivers have been removed from a virtual machine that has been created using Generation 2, but a subset of Integration Services components has been included to initialize at boot and before control is returned to the Operating System. This includes initializing and loading SCSI Controller driver before the Operating System starts loading.
Benefits of Generation 2 Architecture
A Generation 2 virtual machine provides the following functionality over a Generation 1 virtual machine:
- Boot from a SCSI Virtual Hard Drive
In earlier versions of Hyper-V, it was not possible to boot from a SCSI Virtual Hard Drive. With support to boot from a SCSI Virtual Hard Drive in Windows Server 2012 R2, it is not only possible to boot from a SCSI Virtual Hard Drive, you can also relocate the paging file to a SCSI Virtual Hard Drive.
The ability to relocate the paging file to a SCSI Virtual Hard Drive helps in improving the overall performance for applications that frequently require paging operations.
- PXE Boot Option
In earlier versions of Virtual Machine, if you wanted to install an Operating System using network boot, you were required to install the Legacy Network Adaptor after installing the Operating System. With a Generation 2 Virtual Machine, it is now possible to install a Guest Operating System by connecting to a Remote Installation Service using the PXE Boot option.
- Secure Boot
Secure Boot, which is enabled by default for Generation 2 Virtual Machines, is a feature that helps prevent unauthorized firmware or UEFI drivers from running at boot time. This option can be modified after the virtual machine has been created.
- Faster Boot Time and Faster Installation of Guest Operating System
The boot time with Generation 2 Virtual Machine is up to 20% faster now and also installing a Guest Operating System in Virtual Machine using Generation 2 does not take as much time. In fact, the installation of a Guest Operating System under Generation 2 is 50% faster!
- Native VMBUS Support at Boot
A Generation 2 Virtual Machine provides support for VMBUS drivers at the boot. In earlier versions of virtual machines, or virtual machines that use Generation 1, VMs can only load Legacy IDE drivers for initializing file systems. The SCSI controller was available only after Integration Services had been installed in the virtual machine.
In Generation 2, the Operating System is provided with the Synthetic drivers, which enable Operating System to use SCSI drivers at the boot. A virtual machine created with Generation 1 will always use Device Emulation unless Integration Service components have been installed.
Since virtual machines using Generation 2 can boot from a SCSI Driver, the emulation is no longer required. These VMs can use VSP/VSC and VMBUS design effectively to communicate with the parent partition.
- Fewer Devices
There are fewer devices running in a Generation 2 Virtual machine compared to a Generation 1 Virtual Machine. This is because support for all emulated drivers such as IDE and Legacy Network adaptors have been removed and replaced with VMBUS drivers.
Read more on "Server OS Spotlight" »