Red Hat ENTERPRISE LINUX 5.5 - TECHNICAL NOTES Manual page 313

use the Red Hat Network with the hosted Web user interface, a Red Hat Network Satellite, the local
graphical Updater, or the yum command line.
• Anaconda's graphical installer fails to start at the default 800x600 resolution on systems utilizing
Intel Graphics Device Next Generation (IGDNG) devices. To work around this issue, ensure
anaconda uses a higher resolution by passing the parameters resolution=1024x768 or
resolution=1280x1024" to the installer using the boot command line.
• The NFS default for RHEL5 is "locking". Therefore, to mount nfs shares from the %post section of
anaconda, use the mount -o nolock,udp command to start the locking daemon before using nfs
(BZ#426053)
to mount shares.
• If you are using the Virtualized kernel when upgrading from Red Hat Enterprise Linux 5.0 to a later
5.x release, you must reboot after completing the upgrade. You should then boot the system using
the updated Virtualized kernel.
The hypervisor ABI changes in an incompatible way between Red Hat Enterprise Linux 5 and 5.1. If
you do not boot the system after upgrading from RHEL 5.0 using the updated Virtualized kernel, the
upgraded Virtualization RPMs will not match the running kernel.
• When upgrading from Red Hat Enterprise Linux 4.6 to Red Hat Enterprise Linux 5.1 or later, gcc4
may cause the upgrade to fail. As such, you should manually remove the gcc4 package before
(BZ#432773)
upgrading.
• When provisioning guests during installation, the RHN tools for guests option will not be available.
When this occurs, the system will require an additional entitlement, separate from the entitlement
used by dom0.
To prevent the consumption of additional entitlements for guests, install the rhn-
virtualization-common package manually before attempting to register the system to Red Hat
(BZ#431648)
Network.
• When installing Red Hat Enterprise Linux 5 on a guest, the guest is configured to explicitly use a
temporary installation kernel provided by dom0. Once installation finishes, it can then use its own
bootloader. However, this can only be achieved by forcing the guest's first reboot to be a shutdown.
As such, when the Reboot button appears at the end of the guest installation, clicking it shuts down
the guest, but does not reboot it. This is an expected behavior.
Note that when you boot the guest after this it will then use its own bootloader.
• Using the swap --grow parameter in a kickstart file without setting the --maxsize parameter at
the same time makes anaconda impose a restriction on the maximum size of the swap partition. It
does not allow it to grow to fill the device.
For systems with less than 2GB of physical memory, the imposed limit is twice the amount of
physical memory. For systems with more than 2GB, the imposed limit is the size of physical memory
(BZ#462734)
plus 2GB.
• Existing encrypted block devices that contain vfat file systems will appear as type foreign in the
partitioning interface; as such, these devices will not be mounted automatically during system boot.
To ensure that such devices are mounted automatically, add an appropriate entry for them to /etc/
fstab. For details on how to do so, refer to man fstab.
10
12
13
15
9
(BZ#494033)
(BZ#251669)
(BZ#467202)
anaconda
11
14
(BZ#328471)
16
303