Red Hat Enterprise Linux 6 Essentials eBook now available in PDF and ePub formats for only $9.99 RHEL 6 Essentials contains 40 chapters and over 250 pages.
23.4. Configuration changes
As well as configuring libvirt appropriately, virt-v2v will make certain changes to a guest 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 pertain to supported Red Hat based Linux distributions and Windows.
23.4.1. Configuration changes for Linux virtualized guests
Table 23.1. virt-v2v changes to Linux virtualized guests
Un-bootable, that is, xen para-virtualized, 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.
If the guest has X configured, its display driver will be updated. See GUEST DRIVERS for which driver will be used.
Rename block devices
If changes have caused block devices to change name, these changes will be reflected in /etc/fstab
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 23.2. Configured drivers in a Linux Guest
Para-virtualized driver type
In addition, initrd will preload the virtio_pci driver