[ Pobierz całość w formacie PDF ]

guests, use parted within dom0 on the guest's disk; for example, parted
/var/lib/xen/im ages/pv_guest_disk_im age.im g.
When setting up NFSROOT, BOOTPROTO must be set as BOOTPROTO=dhcp in
/etc/sysconfig/network-scripts/ifcfg-eth0.
If your environment requires a different setting for BOOT PROT O, then temporarily set
BOOTPROTO=dhcp in /etc/sysconfig/network-scripts/ifcfg-eth0 before initially
42
3. Release Notes for ia64
creating the initrd. You can reset the original value of BOOT PROT O after the initrd is created.
When attempting to create a fully-virtualized guest, the hypervisor may hang if you allocate too much
of available RAM to the guest. In some cases, a kernel panic may occur.
Both events are caused by hypervisor memory shortage. To ensure that hypervisor overhead is
accounted for each time you allocate memory to a guest, consider the following equation:
26MB + [(number of virtual CPUs used by guest) x 17MB] = (amount of memory to be left unallocated
for each existent guest)
For example, if you have 2048MB of RAM on your system and you intend to use 4 virtual CPUs for
only one guest, you should leave 94MB unallocated. If you intend to have two guests, both using 4
virtual CPUs, leave 188MB unallocated (and so on).
Currently, live migration of fully virtualized guests is not supported on this architecture. The release
notes included in the distribution incorrectly states that it is.
In addition, kexec and kdum p is also not supported for virtualization in this architecture.
Crash dumping through kexec and kdum p may not function reliably with HP Smart Array controllers.
Note that these controllers use the cciss driver.
A solution to this problem, which is likely to involve a firmware update to the controller, is being
investigated.
The QLogic iSCSI Expansion Card for the IBM Bladecenter provides both ethernet and iSCSI
functions. Some parts on the card are shared by both functions. However, the current qla3xxx and
qla4xxx drivers support ethernet and iSCSI functions individually. Both drivers do not support the
use of ethernet and iSCSI functions simultaneously.
As such, using both ethernet and iSCSI functions simultaneously may hang the device. This could
result in data loss and filesystem corruption on iSCSI devices, or network disruptions on other
connected ethernet devices.
When using virt-m anager to add disks to an existing guest, duplicate entries may be created in
the guest's /etc/xen/ configuration file. These duplicate entries will prevent the
guest from booting.
As such, you should remove these duplicate entries.
Repeatedly migrating a guest between two hosts may cause one host to panic. If a host is rebooted
after migrating a guest out of the system and before migrating the same guest back, the panic will not
occur.
sysreport is being deprecated in favor of sos. To install sos, run yum install sos. This
command installs sos and removes sysreport. It is recommended that you update any existing
kickstart files to reflect this.
After installing sos, use the command sosreport to invoke it. Using the command sysreport
generates a warning that sysreport is now deprecated; continuing will invoke sosreport.
If you need to use the sysreport tool specifically, use the command sysreport.legacy to invoke
it.
For more information about sosreport, refer to man sosreport and sosreport --help.
3.1. Installation-Related Notes
This section includes information specific to Anaconda and the installation of Red Hat Enterprise Linux
5.1.
To upgrade an already-installed Red Hat Enterprise Linux 5, you can use Red Hat Network to update
those packages that have changed.
You may also use Anaconda to perform a fresh installation of Red Hat Enterprise Linux 5.1 or to
43
Red Hat Enterprise Linux 5 5.1 Release Notes
perform an upgrade from the latest updated version of Red Hat Enterprise Linux 4 to Red Hat Enterprise
Linux 5.1. Anaconda can also be used to upgrade an already-installed Red Hat Enterprise Linux 5.
Red Hat Enterprise Linux 5.1 for the 64-bit Intel Itanium2 architecture includes runtime support for
32-bit applications through the use of Intel's IA-32 Execution Layer.
The IA-32 Execution Layer is provided on the Supplem entary CD for the Intel Itanium2
architecture. In addition, a set of 32-bit libraries and applications are provided on a separate 32-bit
Compatibility Layer disc. The IA-32 Execution Layer and 32-bit compatibility packages together
provide a runtime environment for 32-bit applications on the 64-bit native distribution.
To install the IA-32 Execution Layer and required 32-bit compatibility packages, follow these steps:
1. Install Red Hat Enterprise Linux 5.1 for the Intel Itanium2 Architecture.
2. Insert the Red Hat Enterprise Linux 5.1 Supplem entary CD, which contains the ia32el
package.
3. After the system has mounted the CD, change to the directory containing the [ Pobierz całość w formacie PDF ]