The use of SHA1-based signatures to perform SecureBoot image verification on UEFI (PE/COFF) executables is deprecated. Instead, use signatures that are based on SHA-2 or later.

In place of the deprecated Virtual Machine Manager (virt-manager), use the web console, otherwise known as Cockpit.

Support for creating snapshots of VMs is limited only to those that do not use UEFI firmware. However, the operation might cause the QEMU monitor to become blocked and affects hypervisor operations.

As an alternative, use external snapshots.

As a replacement of the deprecated libvirtd daemon, use the modular daemons in the libvirt library. For example, the virtqemud handles QEMU drivers.

The isa-fdc driver controls virtual floppy disk devices. To ensure compatibility with migrated virtual machines (VMs), you should not use floppy disk devices in virtual machines that you subsequently host on Oracle Linux 9.

For virtual disk images, use the qcow2-v3 format instead.

The following legacy CPU models are deprecated for use in VMs:

• For Intel® : models prior to Intel® Xeon 55xx and 75xx Processor families (also known as Nehalem)

• For AMD: models prior to AMD Opteron G4

To check whether a VM is using a deprecated CPU model, use the virsh dominfo command, and look for a line similar to the following in the Messages section:

tainted: use of deprecated configuration settings
deprecated configuration: CPU model 'i486'

In this release, RDMA-based live migration of virtual machines is deprecated.

These are deprecated because they are no longer supported by Microsoft.

Use the following binary files from the ipxe-bootimgs package to provide NIC device drivers for iPXE network boot:

• /usr/share/ipxe/ipxe-snponly-x86_64.efi
• /usr/share/ipxe/undionly.kpxe

Dividing select Intel vGPUs into multiple virtual GPUs and assigning them to VMs is no longer supported.

The non-volatile memory library (nvml) packages are deprecated. When they are removed in a future release, you will be unable to pass persistent memory (pmem) devices to VMs. You also will be unable to configure emulated NVDIMM devices backed by volatile memory or files as persistent, but the devices will remain available.