What are Generation 2 VMs in Hyper-V 2012 R2, and why are they important?
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
One of the big changes that Microsoft is making in the forthcoming Windows Server Hyper-V 2012 R2 is a feature known as Generation 2 virtual machines. Generation 2 VMs are an attempt to modernize the virtual machine structure, which has remained relatively unchanged since Windows Server 2008.
Generation 2 VMs will be able to run more efficiently than first generation VMs because they are hypervisor aware and do not rely on synthetic or emulated hardware.
As you can imagine, with this modernization comes a lot of changes and many of the changes will directly impact storage admins.
Probably the biggest change affecting storage admins is that when you create a Generation 2 virtual machine, Hyper-V 2012 R2 uses virtual SCSI disks by default. Previous versions of Windows used virtual IDE disks instead. This means that Generation 2 VMs are not subject to the limits of IDE. It therefore becomes easier to create and attach multiple virtual hard disks to a virtual machine. Doing so was possible in some of the previous versions of Hyper-V, but the virtual SCSI controller was not created by default as it is now.
The move away from IDE also means that Generation 2 VMs will not be able to access physical DVD drives. It is possible, however, to create a virtual SCSI DVD drive. A virtual SCSI DVD drive appears to the guest operating system as a DVD drive but is actually linked to an ISO file rather than to a physical DVD drive.
Another big change with Hyper-V 2012 R2 is that you can boot a Generation 2 VM from a virtual SCSI controller. Previous versions of Hyper-V only supported booting from virtual IDE devices. Of course, since Generation 2 VMs do not support the use of virtualized IDE devices, booting from them is not even an option.
Incidentally, Microsoft has also made it possible to perform a Preboot Execution Environment (PXE) boot from a standard network adapter. Previously, if you wanted to perform a PXE boot, you had to create a legacy synthetic virtual network adapter. This is no longer a requirement for Generation 2 VMs.
One last thing to know about Generation 2 VMs is that they can only host 64-bit editions of Windows Server 2012 R2 or Windows 8.1. These VMs cannot be live migrated to a Windows Server 2012 host, and there is no way to change a VM's generation once you have created the VM.
Dig Deeper on Microsoft Hyper-V management
Related Q&A from Brien Posey
Setting up Office 365 generally involves multiple devices. With nonpersistent VDI, the rules of the game change for IT admins.continue reading
Much has been said about the inability to scale storage separately from other resources in a hyper-converged system, but are there any advantages to ...continue reading
The definition of hyper-converged infrastructure has evolved as the technology has grown. But the phrase still means different things depending on ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.