Krb5; Kvm - Red Hat ENTERPRISE LINUX 5.5 - TECHNICAL NOTES Manual

Table of Contents

Advertisement

Chapter 5. Known Issues
This work around prevents the forcedeth network driver from using high memory resources in the
kdump kernel, allowing the network to function properly.
• The system may not successfully reboot into a kexec/kdump kernel if X is running and using a
driver other than vesa. This problem only exists with ATI Rage XL graphics chipsets.
If X is running on a system equipped with ATI Rage XL, ensure that it is using the vesa driver in
order to successfully reboot into a kexec/kdump kernel.
• kdump now serializes drive creation registration with the rest of the kdump process. Consequently,
kdump may hang waiting for IDE drives to be initialized. In these cases, it is recommended that IDE
disks not be used with kdump.
• It is possible in rare circumstances, for makedumpfile to produce erroneous results but not have
them reported. This is due to the fact that makedumpfile processes its output data through a
pipeline consisting of several stages. If makedumpfile fails, the other stages will still succeed,
effectively masking the failure. Should a vmcore appear corrupt, and makedumpfile is in use,
it is recommended that the core be recorded without makedumpfile and a bug be reported.
87
(BZ#475487)
• kdump now restarts when CPUs or DIMMs are hot-added to a system. If multiple items are added
at the same time, several sequential restarts may be encountered. This behavior is intentional, as
it minimizes the time-frame where a crash may occur while memory or processors are not being
(BZ#474409)
tracked by kdump.
The following note applies to ia64 Architecture:
• Some Itanium systems cannot properly produce console output from the kexec purgatory code.
This code contains instructions for backing up the first 640k of memory after a crash.
While purgatory console output can be useful in diagnosing problems, it is not needed for
kdump to properly function. As such, if your Itanium system resets during a kdump operation,
disable console output in purgatory by adding --noio to the KEXEC_ARGS variable in /etc/
sysconfig/kdump.

5.16. krb5

Kerberos 5 is a network authentication system which authenticates clients and servers to each other
using symmetric key encryption and a trusted third party, the KDC.
• The format of a stash file, while not architecture-specific, is endian-specific. Consequently, a
stash file is not directly portable between big-endian and little-endian systems. When setting up a
secondary KDC where the endianness differs from that of the master KDC, the stash file should be
recreated by running 'kdb5_util create -s' on the secondary and supplying the original master
(BZ#514741)
password.

5.17. kvm

Kernel-based Virtual Machine (KVM) is a full virtualization solution for Linux on x86 hardware.
KVM is a Linux kernel module built for the standard Red Hat Enterprise Linux kernel. KVM can run
multiple unmodified, virtualized guest Windows and Linux operating systems. KVM is a hypervisor
which uses the libvirt virtualization tools (virt-manager and virsh).
318
(BZ#473852)
88
89
(BZ#436426)
90
(BZ#221656)
86
84

Advertisement

Table of Contents
loading

This manual is also suitable for:

Enterprise linux 5.5

Table of Contents