Should I create a generation 1 or 2 virtual machine in Hyper-V?35(共 157)对本文的评价是有帮助 - 评价此主题
Updated: July 24, 2015
Applies To: Microsoft Hyper-V Server Technical Preview, Windows Server Technical Preview
This content is preliminary and subject to change.
Your choice to create a generation 1 or generation 2 virtual machine will depend on which guest operating system you want to install and the boot method you want to use to deploy the virtual machine. We recommend that you create a generation 2 virtual machine to take advantage of features like Secure Boot unless one of the following statements is true:
Generation 2 doesn’t support the operating system you want to run on the virtual machine.
Generation 2 doesn’t support the boot method you want to use.
You can’t change a virtual machine’s generation after you’ve created it. So review the following sections in this article to make sure the generation you pick supports the operating system, boot method, and features you want to use.
[url=]Which guest operating systems are supported?[/url]
Generation 1 virtual machines support most guest operating systems. Generation 2 virtual machines support most 64-bit versions of Windows and more current versions of Linux and FreeBSD operating systems. Use the following sections to see which generation of virtual machine will support the guest operating system you want to install.
CentOS and Red Hat Enterprise Linux guest operating system support
The following table shows what generation 1 and generation 2 virtual machines support for versions of Red Hat Enterprise Linux (RHEL) and CentOS as guest operating systems.
The following table shows what generation 1 and generation 2 virtual machines support for Red Hat Compatible Kernel Series versions as guest operating systems.
Red Hat Compatible Kernel Series versions
Generation 1
Generation 2
Oracle Linux 7.x Series
✔
✔
Oracle Linux 6.6, 6.5, and 6.4
✔
✖
The following table shows what generation 1 and generation 2 virtual machines support for Unbreakable Enterprise Kernel versions as guest operating systems.
The following table shows which boot methods are supported by generation 1 and generation 2 virtual machines.
Boot method
Generation 1
Generation 2
PXE boot by using a standard network adapter
✖
✔
PXE boot by using a legacy network adapter
✔
✖
Boot from a SCSI virtual hard disk (.VHDX) or virtual DVD (.ISO)
✖
✔
Boot from IDE Controller virtual hard disk (.VHD) or virtual DVD (.ISO)
✔
✖
Boot from floppy (.VFD)
✔
✖
[url=]What are the advantages of using generation 2 virtual machines?[/url]
Here are some of the advantages you get when you use a generation 2 virtual machine:
Secure Boot – This is a feature that verifies the boot loader is signed by a trusted authority in the UEFI database to help prevent unauthorized firmware, operating systems, or UEFI drivers from running at boot time. Secure Boot is enabled by default for generation 2 virtual machines. If you need to run a guest operating system that’s not supported by Secure Boot, you can disable it after the virtual machine’s created. For more information, see Secure Boot.
To Secure Boot generation 2 Linux virtual machines, you need to choose the UEFI CA Secure Boot template when you create the virtual machine.
Larger boot volume - The maximum boot volume for generation 2 virtual machines is 64TB. This is the maximum disk size supported by a .VHDX. For generation 1 virtual machines, the maximum boot volume is 2TB for a .VHDX and 2040GB for a .VHD. For more information, see Hyper-V Virtual Hard Disk Format Overview.