Windows VMs 编辑

Installing Windows VMs on the Citrix Hypervisor server requires hardware virtualization support (Intel VT or AMD-V).

Note:

Nested virtualization is not supported for Windows VMs hosted on Citrix Hypervisor.

Basic procedure for creating a Windows VM

The process of installing a Windows on to a VM consists of the following steps:

  1. Selecting the appropriate Windows template

  2. Choosing the appropriate boot mode

  3. Installing the Windows operating system

  4. Installing the Citrix VM Tools for Windows (I/O drivers and the Management Agent)

Warning:

Windows VMs are supported only when the VMs have the Citrix VM Tools for Windows installed.

Windows VM templates

Windows operating systems are installed onto VMs by cloning an appropriate template using either Citrix Hypervisor Center or the xe CLI, and then installing the operating system. The templates for individual guests have predefined platform flags set which define the configuration of the virtual hardware. For example, all Windows VMs are installed with the ACPI Hardware Abstraction Layer (HAL) mode enabled. If you later change one of these VMs to have multiple virtual CPUs, Windows automatically switches the HAL to multi-processor mode.

The available Windows templates are listed in the following table:

Template NameSupported boot modesDescription
Windows 10 (32-bit)BIOSUsed to install Windows 10
Windows 10 (64-bit)BIOS, UEFI, UEFI Secure BootUsed to install Windows 10 (64-bit)
Windows Server 2016 (64-bit)BIOS, UEFI, UEFI Secure BootUsed to install Windows Server 2016 or Windows Server Core 2016 (64-bit)
Windows Server 2019 (64-bit)BIOS, UEFI, UEFI Secure BootUsed to install Windows Server 2019 or Windows Server Core 2019 (64-bit)
Windows Server 2022 (64-bit)BIOS, UEFI, UEFI Secure BootUsed to install Windows Server 2022 or Windows Server Core 2022 (64-bit)

Attach an ISO image library

The Windows operating system can be installed either from an install CD in a physical CD-ROM drive on the Citrix Hypervisor server, or from an ISO image. See Create ISO images for information on how to make an ISO image from a Windows install CD and make it available for use.

Guest UEFI boot and Secure Boot

Citrix Hypervisor enables recent versions of Windows guest operating systems to boot in UEFI mode. UEFI boot provides a richer interface for the guest operating systems to interact with the hardware, which can significantly reduce Windows VM boot times.

For these Windows operating systems, Citrix Hypervisor also supports Windows Secure Boot. Secure Boot prevents unsigned, incorrectly signed or modified binaries from being run during boot. On a UEFI-enabled VM that enforces Secure Boot, all drivers must be signed. This requirement might limit the range of uses for the VM, but provides the security of blocking unsigned/modified drivers. If you use an unsigned driver, secure boot fails and an alert is shown in Citrix Hypervisor Center.

Secure Boot also reduces the risk that malware in the guest can manipulate the boot files or run during the boot process.

Citrix Hypervisor supports UEFI boot and Secure Boot on newly created Windows 10 (64-bit), Windows Server 2016 (64-bit), Windows Server 2019 (64-bit), and Windows Server 2022 (64-bit) VMs. You must specify the boot mode when creating a VM. It is not possible to change the boot mode of a VM between BIOS and UEFI (or UEFI Secure Boot) after booting the VM for the first time. However, you can change the boot mode between UEFI and UEFI Secure Boot at any time.

Consider the following when enabling UEFI boot on VMs:

  • Ensure that the UEFI-enabled VM has at least two vCPUs.
  • You can import or export a UEFI-enabled VM created on Citrix Hypervisor as an OVA, OVF, or an XVA file. Importing a UEFI-enabled VM from OVA or OVF packages created on other hypervisors is not supported.
  • To use PVS-Accelerator with UEFI-enabled VMs, ensure that you are using Citrix Provisioning 1906 or later.
  • Use the UEFI settings menu to change the screen resolution of the Citrix Hypervisor Center console. For detailed instructions, see Troubleshooting.

Consider the following when enabling UEFI Secure Boot on VMs:

  • The Citrix Hypervisor server must be booted in UEFI mode. For more information, see Network boot installations
  • Your resource pool or standalone server must have access to Secure Boot certificates.

    Only one Citrix Hypervisor server in the pool requires access to the certificates. When a server joins a pool the certificates on that server are made available to other servers in the pool.

Note

UEFI-enabled VMs use NVME and E1000 for emulated devices. The emulation information does not display these values until after you install Citrix VM Tools for Windows on the VM. UEFI-enabled VMs also show as only having 2 NICs until after you install Citrix VM Tools for Windows.

Enabling UEFI boot or UEFI Secure Boot

You can use Citrix Hypervisor Center or the xe CLI to enable UEFI boot or UEFI Secure Boot for your VM.

For information about creating a UEFI-enabled VM in Citrix Hypervisor Center, see Create a VM by using Citrix Hypervisor Center.

Using the xe CLI to enable UEFI boot or UEFI Secure Boot

When you create a VM, run the following command before booting the VM for the first time:

    xe vm-param-set uuid=<UUID> HVM-boot-params:firmware=<MODE>
    xe vm-param-set uuid=<UUID> platform:secureboot=<OPTION>
<!--NeedCopy-->

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据

词条统计

浏览:97 次

字数:7048

最后编辑:7 年前

编辑次数:0 次

    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
    原文