Migrating paravirtualized guests through xm migrate [domain] [dom0 IP address]
does not work.
Creating a guest more than 1,000 times will cause dom0
to reboot suddenly. Red Hat recommends that you pre-empt this by rebooting dom0
before the domain ID of any guest reaches 1000.
If you encounter a guest installation failure, Red Hat recommends that you restart the xend
daemon before attempting to install a new guest.
On some Itanium systems configured for console output to VGA, the dom0
virtualized kernel may fail to boot. This is because the virtualized kernel failed to properly detect the default console device from the Extensible Firmware Interface (EFI) settings.
When this occurs, add the boot parameter console=tty
to the kernel boot options in /boot/efi/elilo.conf
.
On some Itanium systems (such as the Hitachi Cold Fusion 3e), the serial port cannot be detected in dom0
when VGA is enabled by the EFI Maintenance Manager. As such, you need to supply the following serial port information to the dom0
kernel:
Speed in bits/second
Number of data bits
Parity
io_base
address
These details must be specified in the append=
line of the dom0
kernel in /boot/efi/elilo.conf
. For example:
append="com1=19200,8n1,0x3f8—quiet rhgb console=tty0 console=ttyS0,19200n8"
In this example, com1
is the serial port, 19200
is the speed (in bits/second), 8n1
specifies the number of data bits/parity settings, and 0x3f8
is the io_base
address.
Virtualization does not work on architectures that use NUMA. As such, installing the virtualized kernel on systems that use NUMA will result in a boot failure.
Some installation numbers install the virtualized kernel by default. If you have such an installation number and your system uses NUMA (or cannot disable NUMA), deselect the Virtualization option during installation.
Currently, live migration of fully virtualized guests is not supported on this architecture. In addition, kexec
and kdump
are also not supported for virtualization on this architecture.