As well as configuring libvirt appropriately,
virt-v2v will make certain changes to a virtual machine to enable it to run on a KVM hypervisor either with or without virtIO drivers. These changes are specific to the guest operating system. The details specified here apply to supported Red Hat Enterprise Linux versions and Windows.
7.2.1. Configuration changes for Linux virtual machines
Table 7.1. virt-v2v changes to Linux virtual machines
|Kernel||Unbootable kernels (such as Xen paravirtualized kernels) will be uninstalled. No new kernel will be installed if there is a remaining kernel which supports VirtIO. If no remaining kernel supports VirtIO and the configuration file specifies a new kernel it will be installed and configured as the default.|
|X reconfiguration||If the guest has X configured, its display driver will be updated. See Table 7.2, “Configured drivers in a Linux guest” for which driver will be used.|
|Rename block devices||If reconfiguration has caused block devices to change name, these changes will be reflected in |
|Configure device drivers||Whether VirtIO or non-VirtIO drivers are configured, |
virt-v2v will ensure that the correct network and block drivers are specified in the modprobe configuration.
virt-v2v will ensure that the initrd for the default kernel supports booting the root device, whether it is using VirtIO or not.
virt-v2v will initiate a relabel of the guest on the next boot. This ensures that any changes it has made are correctly labeled according to the guest's local policy.
virt-v2v will configure the following drivers in a Linux guest:
Table 7.2. Configured drivers in a Linux guest
|Paravirtualized driver type||Driver module|
|In addition, initrd will preload the virtio_pci driver|| |
|Other drivers|| |