| RHE Linux 6.2 Technical Notesanaconda component, BZ#676025Users performing an upgrade using the Anaconda's text mode interface who do not have a boot loader already installed on the system, or who have a non-GRUB boot loader, need to select Skip Boot Loader Configuration during the installation process. Boot loader configuration will need to be completed manually after installation. This problem does not affect users running Anaconda in the graphical mode (graphical mode also includes VNC connectivity mode). anaconda componentAnaconda fails to install to partitions of size 2.2 TB and larger. anaconda componentOn s390x systems, you cannot use automatic partitioning and encryption. If you want to use storage encryption, you must perform custom partitioning. Do not place the /boot volume on an encrypted volume. anaconda componentThe order of device names assigned to USB attached storage devices is not guaranteed. Certain USB attached storage devices may take longer to initialize than others, which can result in the device receiving a different name than you expect (for example, sdc instead of sda). During installation, verify the storage device size, name, and type when configuring partitions and file systems. kernel componentDell systems based on a future Intel processor with graphics acceleration require the selection of the install system with basic video driver installation option. A future Red Hat Enterprise Linux 6.2.z Extended Update Support update will remove this requirement. -
kernel component Recent Red Hat Enterprise Linux 6 releases use a new naming scheme for network interfaces on some machines. As a result, the installer may use different names during an upgrade in certain scenarios (typically em1 is used instead of eth0 on new Dell machines). However, the previously used network interface names are preserved on the system and the upgraded system will still use the previously used interfaces. This is not the case for Yum upgrades. -
anaconda component The kdump default on feature currently depends on Anaconda to insert the crashkernel= parameter to the kernel parameter list in the boot loader's configuration file. firstaidkit componentThe firstaidkit-plugin-grub package has been removed from Red Hat Enterprise Linux 6.2. As a consequence, in rare cases, the system upgrade operation may fail with unresolved dependencies if the plug-in has been installed in a previous version of Red Hat Enterprise Linux. To avoid this problem, the firstaidkit-plugin-grub package should be removed before upgrading the system. However, in most cases, the system upgrade completes as expected. anaconda component, BZ#623261 In some circumstances, disks that contain a whole disk format (for example, a LVM Physical Volume populating a whole disk) are not cleared correctly using the clearpart --initlabel kickstart command. Adding the --all switch-as in clearpart --initlabel --all-ensures disks are cleared correctly. squashfs-tools componentDuring the installation on POWER systems, error messages similar to: attempt to access beyond end of deviceloop0: rw=0, want=248626, limit=248624 may be returned to sys.log. These errors do not prevent installation and only occur during the initial setup. The file system created by the installer will function correctly. anaconda componentWhen installing on the IBM System z architecture, if the installation is being performed over SSH, avoid resizing the terminal window containing the SSH session. If the terminal window is resized during the installation, the installer will exit and the installation will terminate. yaboot component, BZ#613929 The kernel image provided on the CD/DVD is too large for Open Firmware. Consequently, on the POWER architecture, directly booting the kernel image over a network from the CD/DVD is not possible. Instead, use yaboot to boot from a network. anaconda componentThe Anaconda partition editing interface includes a button labeled Resize. This feature is intended for users wishing to shrink an existing file system and an underlying volume to make room for an installation of a new system. Users performing manual partitioning cannot use the Resize button to change sizes of partitions as they create them. If you determine a partition needs to be larger than you initially created it, you must delete the first one in the partitioning editor and create a new one with the larger size. system-config-kickstart componentChannel IDs (read, write, data) for network devices are required for defining and configuring network devices on IBM S/390 systems. However, system-config-kickstart-the graphical user interface for generating a kickstart configuration-cannot define channel IDs for a network device. To work around this issue, manually edit the kickstart configuration that system-config-kickstart generates to include the desired network devices. dracut component During FCoE BFS installation, when an Ethernet interface goes offline after discovering the targets, FCoE link will never come up. This is because Anaconda creates an FCoE configuration file under/etc/fcoe/ using biosdevname (new style interface naming scheme) for all the available Ethernet interfaces for FCoE BFS. However, it does not add the ifname kernel command line for the FCoE interface that stays offline after discovering FCoE targets during installation. Because of this, during subsequent reboots, the system tries to find the old style ethX interface name in the /etc/fcoe directory, which does not match with the file created by Anaconda using biosdevname. Therefore, due to the missing FCoE configuration file, an FCoE interface is never created on the Ethernet interface. To avoid this problem, ensure that the Ethernet interface does not go offline during FCoE BFS installation. If the Ethernet interface does go offline during installation after discovering the targets, add the following parameter to the kernel command line: ifname=<biosdevname_interface_name>:<mac_address>
subscription manager componentWhen registering a system with firstboot, the RHN Classic option is checked by default in the Subscription part.
cpuspeed component, BZ#626893 Some HP Proliant servers may report incorrect CPU frequency values in /proc/cpuinfo or /sys/device/system/cpu/*/cpufreq. This is due to the firmware manipulating the CPU frequency without providing any notification to the operating system. To avoid this ensure that the HP Power Regulator option in the BIOS is set to OS Control. An alternative available on more recent systems is to set Collaborative Power Control to Enabled. releng component, BZ#644778 Some packages in the Optional repositories on RHN have multilib file conflicts. Consequently, these packages cannot have both the primary architecture (for example, x86_64) and secondary architecture (for example, i686) copies of the package installed on the same machine simultaneously. To work around this issue, install only one copy of the conflicting package. releng componentThe openmpi-psm and openmpi-psm-devel packages are not provided on architectures other than AMD64 and Intel 64 for Red Hat Enterprise Linux 6.2. If the openmpi-psm.i686 or/and openmpi-psm-devel.i686 packages are installed on a AMD64 or an Intel 64 system, remove these packages before you attempt to update Open MPI. grub component, BZ#695951On certain UEFI-based systems, you may need to type BOOTX64 rather than bootx64 to boot the installer due to case sensitivity issues. grub component, BZ#698708 When rebuilding the grub package on the x86_64 architecture, the glibc-static.i686 package must be used. Using the glibc-static.x86_64 package will not meet the build requirements. parted componentThe parted utility in Red Hat Enterprise Linux 6 cannot handle Extended Address Volumes (EAV) Direct Access Storage Devices (DASD) that have more than 65535 cylinders. Consequently, EAV DASD drives cannot be partitioned using parted, and installation on EAV DASD drives will fail. To work around this issue, complete the installation on a non EAV DASD drive, then add the EAV device after the installation using the tools provided in the s390-utils package. PackageKit componentIf you are being asked repeatedly to enter your root password while using PackageKit to update your system via non-Red Hat repositories, you may be affected by the PackageKit issue described in Section 2.11, "Desktop".
ovirt-node component, BZ#747102 Upgrades from Beta to the GA version will result in an incorrect partitioning of the host. The GA version must be installed clean. UEFI machines must be set to legacy boot options for RHEV-H to boot successfully after installation. kernel componentWhen a system boots from SAN, it starts the libvirtd service, which enables IP forwarding. The service causes a driver reset on both Ethernet ports which causes a loss of all paths to an OS disk. Under this condition, the system cannot load firmware files from the OS disk to initialize Ethernet ports, eventually never recovers paths to the OS disk, and fails to boot from SAN. To work around this issue add the bnx2x.disable_tpa=1 option to the kernel command line of the GRUB menu, or do not install virtualization related software and manually enable IP forwarding when needed. kernel componentBooting Red Hat Enterprise Linux 6.2 as an HVM guest with more than one vCPU on machines that support SMEP and using Red Hat Enterprise Linux 5.7 and earlier Xen Hypervisors fails. To work around this issue, boot the guest with the nosmep kernel command line option. vdsm componentIf the /root/.ssh directory is missing from a host when it is added to a Red Hat Enterprise Virtualization Manager data center, the directory is created with a wrong SELinux context, and SSH'ing into the host is denied. To work around this issue, manually create the /root/.ssh directory with the correct SELinux context: ~]# mkdir /root/.ssh~]# chmod 0700 /root/.ssh~]# restorecon /root/.ssh vdsm componentVDSM now configures libvirt so that connection to its local read-write UNIX domain socket is password-protected by SASL. The intention is to protect virtual machines from human errors of local host administrators. All operations that may change the state of virtual machines on a Red Hat Enterprise Virtualization-controlled host must be performed from Red Hat Enterprise Virtualization Manager. libvirt componentIn earlier versions of Red Hat Enterprise Linux, libvirt permitted PCI devices to be insecurely assigned to guests. In Red Hat Enterprise Linux 6, assignment of insecure devices is disabled by default by libvirt. However, this may cause assignment of previously working devices to start failing. To enable the old, insecure setting, edit the /etc/libvirt/qemu.conf file, set the relaxed_acs_check = 1 parameter, and restart libvirtd (service libvirtd restart). Note that this action will re-open possible security issues. virtio-win component, BZ#615928 The balloon service on Windows 7 guests can only be started by the Administrator user. libvirt component, BZ#622649 libvirt uses transient iptables rules for managing NAT or bridging to virtual machine guests. Any external command that reloads the iptables state (such as running system-config-firewall) will overwrite the entries needed by libvirt. Consequently, after running any command or tool that changes the state of iptables, guests may lose access the network. To work around this issue, use the service libvirt reload command to restore libvirt's additional iptables rules. virtio-win component, BZ#612801 A Windows virtual machine must be restarted after the installation of the kernel Windows driver framework. If the virtual machine is not restarted, it may crash when a memory balloon operation is performed. qemu-kvm component, BZ#720597Installation of Windows 7 Ultimate x86 (32-bit) Service Pack 1 on a guest with more than 4GB of RAM and more than one CPU from a DVD medium often crashes during the final steps of the installation process due to a system hang. To work around this issue, use the Windows Update utility to install the Service Pack. qemu-kvm component, BZ#612788 A dual function Intel 82576 Gigabit Ethernet Controller interface (codename: Kawela, PCI Vendor/Device ID: 8086:10c9) cannot have both physical functions (PF's) device-assigned to a Windows 2008 guest. Either physical function can be device assigned to a Windows 2008 guest (PCI function 0 or function 1), but not both. virt-v2v componentIn Red Hat Enterprise Linux 6.2, the default virt-v2v configuration is split into two files: /etc/virt-v2v.conf and /var/lib/virt-v2v/virt-v2v.db. The former now contains only local customizations, whereas the latter contains generic configuration which is not intended to be customized. Prior to Red Hat Enterprise Linux 6.2, virt-v2v's -f flag defaulted to /etc/virt-v2v.conf. In Red Hat Enterprise Linux 6.2, it now defaults to both /etc/virt-v2v.conf and /var/lib/virt-v2v/virt-v2v.db. Data from both of these files is required during conversion. This change has no impact for most users. If a machine is upgraded from Red Hat Enterprise Linux 6.1 to Red Hat Enterprise Linux 6.2, the existing combined /etc/virt-v2v.conf will not be updated. If a user explicitly specifies -f /etc/virt-v2v.conf on the command line, the behavior will be identical to the one prior to update. If the user does not specify the -f command line option, the configuration will use both /etc/virt-v2v.conf and /var/lib/virt-v2v/virt-v2v.db, with the former taking precedence. However, a freshly-installed Red Hat Enterprise Linux 6.2 machine with a default configuration no longer has all required data in /etc/virt-v2v.conf. If the user explicitly specifies -f /etc/virt-v2v.conf on the command line, virt-v2v will not be able to enable virtio support for any guests. To work around this issue, do use the -f command line option, as this defaults to using both configuration files. If the -f command line option is used, it must be specified twice: first for /etc/virt-v2v.conf and second for /var/lib/virt-v2v/virt-v2v.conf. If the virt-v2v command line cannot be altered, the /etc/virt-v2v.conf file must contain a combined configuration file. This can be copied from a Red Hat Enterprise Linux 6.1 system, or created by copying all configuration elements from /var/lib/virt-v2v/virt-v2v.db to /etc/virt-v2v.conf. virt-v2v component, BZ#618091 The virt-v2v utility is able to convert guests running on an ESX server. However, if an ESX guest has a disk with a snapshot, the snapshot must be on the same datastore as the underlying disk storage. If the snapshot and the underlying storage are on different datastores, virt-v2v will report a 404 error while trying to retrieve the storage. virt-v2v component, BZ#678232 The VMware Tools application on Microsoft Windows is unable to disable itself when it detects that it is no longer running on a VMware platform. Consequently, converting a Microsoft Windows guest from VMware ESX, which has VMware Tools installed, will result in errors. These errors usually manifest as error messages on start-up, and a "Stop Error" (also known as a BSOD) when shutting down the guest. To work around this issue, uninstall VMware Tools on Microsoft Windows guests prior to conversion. spice-client componentSound recording only works when there is no application accessing the recording device at the client start-up.
2.5. Storage and File Systemsdevice-mapper-multipath componentMultipath's queue_without_daemon yes default option queues I/O even though all iSCSI links have been disconnected when the system is shut down, which causes LVM to become unresponsive when scanning all block devices. As a result, the system cannot be shut down. To work around this issue, add the following line into the defaults section of /etc/multipath.conf: queue_without_daemon no initscripts componentIf the /etc/fstab file contains an NFS mount entry that has the file system check (fsck) enabled, the netfs service responsible for mounting and unmounting NFS file systems initializes the file system check. Because NFS is not a block-level file system, this operation fails, and subsequently also fails the system boot itself. To work around this problem, disable the file system check by setting the sixth vaule for NFS mount entries to 0. iscsi-initiator-utils component, BZ#739843 iSCSI discovery via a TOE (TCP Offload Engine) interface fails when the iscsiadm -m iface has never been executed. This is due to the iscsiadm -m discovery command not checking interface settings while the iscsiadm -m iface does. To work around this issue, run the iscsiadm -m iface command at least once after installing the iscsi-initiatio-utils package. Once the interface setting is updated, discoveries are performed with no errors. vdsm componentAttempting to create/extend a storage domain on/with a device that exposes a block size different than 512 bytes such create/extend request to fail. To work around this issue, the storage must be configured to expose a block size of 512 bytes. kernel component, BZ#606260 The NFSv4 server in Red Hat Enterprise Linux 6 currently allows clients to mount using UDP and advertises NFSv4 over UDP with rpcbind. However, this configuration is not supported by Red Hat and violates the RFC 3530 standard. lvm2 componentThe dracut utility currently only supports one FiberChannel over Ethernet (FCoE) connection to be used to boot from the root device. Consequently, booting from a root device that spans multiple FCoE devices (for example, using RAID, LVM or similar techniques) is not possible. -
lvm2 component The pvmove command cannot currently be used to move mirror devices. However, it is possible to move mirror devices by issuing a sequence of two commands. For mirror images, add a new image on the destination PV and then remove the mirror image on the source PV: ~]$ lvconvert -m +1 <vg/lv> <new PV>~]$ lvconvert -m -1 <vg/lv> <old PV> Mirror logs can be handled in a similar fashion: ~]$ lvconvert --mirrorlog core <vg/lv>~]$ lvconvert --mirrorlog disk <vg/lv> <new PV> or ~]$ lvconvert --mirrorlog mirrored <vg/lv> <new PV>~]$ lvconvert --mirrorlog disk <vg/lv> <old PV>
NetworkManager componentTo ensure that RFC3442-standard classless static routes provided by a DHCP server are processed correctly when using NetworkManager, the following lines should be placed into the /etc/dhclient.conf file or, if using per-interface DHCP options, the /etc/dhclient-<ifname>.conf file: option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;option ms-classless-static-routes code 249 = array of unsigned integer 8;also request rfc3442-classless-static-routes;also request ms-classless-static-routes; The above lines will ensure that RFC3442 classless static routes are requested from the DHCP server, and that they are properly processed by NetworkManager. iprutils componentUsers of the IBM PCI-E Gen2 6GB SAS RADI adapter (FC 5913) in Red Hat Enterprise Linux 6.2 may encounter the following issues: Updating firmware on a storage drawer that is connected to the adapter mentioned above using the iprconfig command fails. Attempting to change the asymmetric access for an array results in a failure. Additionally, not specifying asymmetric access as an option to the iprconfig command results in a failure as well.
corosync component, BZ#722469A double ring failure results in the spinning of the corosync process. Also, because DLM relies on SCTP, which is non-functional, many features of the cluster software that rely on DLM do not work properly. luci component, BZ#615898 luci will not function with Red Hat Enterprise Linux 5 clusters unless each cluster node has ricci version 0.12.2-14
- Identity Management component
When transitioning to a fully supported Identity Management version in Red Hat Enterprise Linux 6.2, uninstall any previous beta version of Identity Management or Technology Preview parts of Red Hat Enterprise Identity (IPA) available in the Red Hat Enterprise Linux 6.1 Technology Preview and install Identity Management again. - Identity Management component
When an Identity Management server is installed with a custom hostname that is not resolvable, the ipa-server-install command should add a record to the static hostname lookup table in /etc/hosts and enable further configuration of Identity Management integrated services. However, a record is not added to /etc/hosts when an IP address is passed as an CLI option and not interactively. Consequently, Identity Management installation fails because integrated services that are being configured expect the Identity Management server hostname to be resolvable. To work around this issue, complete one of the following: Run the ipa-server-install without the --ip-address option and pass the IP address interactively. Add a record to /etc/hosts before the installation is started. The record should contain the Identity Management server IP address and its full hostname (the hosts(5) man page specifies the record format).
As a result, the Identity Management server can be installed with a custom hostname that is not resolvable. sssd component, BZ#750922Upgrading SSSD from the version provided in Red Hat Enterprise Linux 6.1 to the version shipped with Red Hat Enterprise Linux 6.2 may fail due to a bug in the dependent library libldb. This failure occurs when the SSSD cache contains internal entries whose distinguished name contains the \, character sequence. The most likely example of this is for an invalid memberUID entry to appear in an LDAP group of the form: memberUID: user1,user2 memberUID is a multi-valued attribute and should not have multiple users in the same attribute.
If the upgrade issue occurs, identifiable by the following debug log message: (Wed Nov 2 15:18:21 2011) [sssd] [ldb] (0): A transaction is still active inldb context [0xaa0460] on /var/lib/sss/db/cache_<DOMAIN>.ldb remove the /var/lib/sss/db/cache_<DOMAIN>.ldb file and restart SSSD. Removing the /var/lib/sss/db/cache_<DOMAIN>.ldb file purges the cache of all entries (including cached credentials). sssd component, BZ#751314When a group contains certain incorrect multi-valued memberUID values, SSSD fails to sanitize the values properly. The memberUID value should only contain one username. As a result, SSSD creates incorrect users, using the broken memberUID values as their usernames. This, for example, causes problems during cache indexing. - Identity Management component, BZ#750596
Two Identity Management servers, both with a CA (Certificate Authority) installed, use two replication replication agreements. One is for user, group, host, and other related data. Another replication agreement is established between the CA instances installed on the servers. If the CA replication agreement is broken, the Identity Management data is still shared between the two servers, however, because there is no replication agreement between the two CAs, issuing a certificate on one server will cause the other server to not recognize that certificate, and vice versa. - Identity Management component
The Identity Management (ipa) package cannot be build with a 6ComputeNode subscription. - Identity Management component
On the configuration page of the Identity Management WebUI, if the User search field is left blank, and the search button is clicked, an internal error is returned. sssd component, BZ#741264 Active Directory performs certain LDAP referral-chasing that is incompatible with the referral mechanism included in the openldap libraries. Notably, Active Directory sometimes attempts to return a referral on an LDAP bind attempt, which used to cause a hang, and is now denied by the openldap libraries. As a result, SSSD may suffer from performance issues and occasional failures resulting in missing information. To work around this issue, disable referral-chasing by setting the following parameter in the [domain/DOMAINNAME] section of the /etc/sssd/sssd.conf file: ldap_referrals = false
kernel component The Red Hat Enterprise Linux 6.2 Emulex FC (lpfc) driver does not support firmware downloads for LPe1600x 16 Gbit/s Fibre Channel adapters. Please consult your OEM for instructions on how to download new firmware on these Fibre Channel adapters. kernel componentiSCSI and FCoE boot support on Broadcom devices is not included in Red Hat Enterprise Linux 6.2. These two new features, which have been added to the bnx2i and bnx2fc Broadcom drivers in Red Hat Enterprise Linux 6.2, remain a Technology Preview until further notice. kexec-tools componentStarting with Red Hat Enterprise Linux 6.0 and later, kexec kdump supports dumping core to the Brtfs file system. However, note that because the findfs utility in busybox does not support Btrfs yet, UUID/LABEL resolving is not functional. Avoid using the UUID/LABEL syntax when dumping core to Btrfs file systems. kexec-tools component, BZ#600575 The persistent naming of devices that are dynamically discovered in a system is a large problem that exists both in and outside of kdump. Normally, devices are detected in the same order, which leads to consistent naming. In cases where devices are not detected in the same order, device abstraction layers (for example, LVM) essentially resolve the issue, through the use of metadata stored on the devices to create consistency. In the rare cases where no such abstraction layer is in use, and renaming devices causes issues with kdump, it is recommended that devices be referred to by disk label or UUID in kdump.conf. trace-cmd componentThe trace-cmd service does start on 64-bit PowerPC and IBM System z systems because the sys_enter and sys_exit events do not get enabled on the aforementioned systems. trace-cmd componenttrace-cmd's subcommand, report, does not work on IBM System z systems. This is due to the fact that the CONFIG_FTRACE_SYSCALLS parameter is not set on IBM System z systems. tuned componentRed Hat Enterprise Linux 6.1 and later enter processor power-saving states more aggressively. This may result in a small performance penalty on certain workloads. This functionality may be disabled at boot time by passing the intel_idle.max_cstate=0 parameter, or at run time by using the cpu_dma_latency pm_qos interface. libfprint componentRed Hat Enterprise Linux 6 only has support for the first revision of the UPEK Touchstrip fingerprint reader (USB ID 147e:2016). Attempting to use a second revision device may cause the fingerprint reader daemon to crash. The following command returns the version of the device being used in an individual machine: ~]$ lsusb -v -d 147e:2016 | grep bcdDevice kernel componentThe Emulex Fibre Channel/Fibre Channel-over-Ethernet (FCoE) driver in Red Hat Enterprise Linux 6 does not support DH-CHAP authentication. DH-CHAP authentication provides secure access between hosts and mass storage in Fibre-Channel and FCoE SANs in compliance with the FC-SP specification. Note, however that the Emulex driver (lpfc) does support DH-CHAP authentication on Red Hat Enterprise Linux 5, from version 5.4. Future Red Hat Enterprise Linux 6 releases may include DH-CHAP authentication. kernel componentThe recommended minimum HBA firmware revision for use with the mpt2sas driver is "Phase 5 firmware" (that is, with version number in the form 05.xx.xx.xx). Note that following this recommendation is especially important on complex SAS configurations involving multiple SAS expanders.
kernel componentWhen booted off a qla4xxx device, upgrading from Red Hat Enterprise Linux 6.1 to Red Hat Enterprise Linux 6.2 will cause the system to fail to boot up with the new kernel. There are various ways to work around this issue: You have upgraded to Red Hat Enterprise Linux 6.2 and want the qla4xxx device firmware to manage discovering and logging in to iSCSI targets. Boot up the system with the Red Hat Enterprise Linux 6.1 kernel. Disable SysfsBoot for the qla4xxx device: ~]# echo "options qla4xxx ql4xdisablesysfsboot=1" >> /etc/modprobe.d/qla4xxx.conf Rebuild initramfs for the Red Hat Enterprise Linux 6.2 kernel by re-installing the kernel: ~]# yum -y reinstall kernel
You have not upgraded to Red Hat Enterprise Linux 6.2 and want the qla4xxx device firmware to manage discovering and logging in to iSCSI targets. Boot up the system with the Red Hat Enterprise Linux 6.1 kernel. Disable SysfsBoot for the qla4xxx device: ~]# echo "options qla4xxx ql4xdisablesysfsboot=1" >> /etc/modprobe.d/qla4xxx.conf Proceed with the upgrade to Red Hat Enterprise Linux 6.2.
You have upgraded to Red Hat Enterprise Linux 6.2 and want to use open-iscsi to manage the qla4xxx discovery and login process. Boot up the system with the Red Hat Enterprise Linux 6.1 kernel. Install the iscsi-initiator-utils and dracut-network packages: ~]# yum install -y dracut-network iscsi-initiator-utils Rebuild initramfs for the Red Hat Enterprise Linux 6.2 kernel by re-installing the kernel: ~]# yum -y reinstall kernel Add the iscsi_firmware kernel option into GRUB's configuration: /boot/grub/menu.lst (for LILO, the Linux Loader, modify the /etc/lilo.conf file).
You have not upgraded to Red Hat Enterprise Linux 6.2 and want to use open-iscsi to manage the qla4xxx discovery and login process. Install the iscsi-initiator-utils and dracut-network packages: ~]# yum install -y dracut-network iscsi-initiator-utils Proceed with the upgrade to Red Hat Enterprise Linux 6.2. Add the iscsi_firmware kernel option into GRUB's configuration: /boot/grub/menu.lst (for LILO, the Linux Loader, modify the /etc/lilo.conf file).
kernel component, BZ#679262In Red Hat Enterprise Linux 6.2, due to security concerns, addresses in /proc/kallsyms and /proc/modules show all zeros when accessed by a non-root user. kernel componentkernel componentSuperfluous information is displayed on the console due to a correctable machine check error occurring. This information can be safely ignored by the user. Machine check error reporting can be disabled by using the nomce kernel boot option, which disables machine check error reporting, or the mce=ignore_ce kernel boot option, which disables correctable machine check error reporting. -
kernel component The order in which PCI devices are scanned may change from one major Red Hat Enterprise Linux release to another. This may result in device names changing, for example, when upgrading from Red Hat Enterprise Linux 5 to 6. You must confirm that a device you refer to during installation, is the intended device. One way to assure the correctness of device names is to, in some configurations, determine the mapping from the controller name to the controller's PCI address in the older release, and then compare this to the mapping in the newer release, to ensure that the device name is as expected. The following is an example from /var/log/messages: kernel: cciss0: <0x3230> at PCI 0000:1f:00.0 IRQ 71 using DAC . . . . . . kernel: cciss1: <0x3230> at PCI 0000:02:00.0 IRQ 75 using DAC If the device name is incorrect, add the pci=bfsort parameter to the kernel command line, and check again. kernel componentEnabling CHAP (Challenge-Handshake Authentication Protocol) on an iSCSI target for the be2iscsi driver results in kernel panic. To work around this issue, disable CHAP on the iSCSI target. kernel componentNewer VPD (Vital Product Data) blocks can exceed the size the tg3 driver normally handles. As a result, some of the routines that operate on the VPD blocks may fail. For example, the nvram test fails when running the ethtool -t command on BCM5719 and BCM5720 Ethernet Controllers. kernel componentRunning the ethtool -t command on BCM5720 Ethernet controllers causes a loopback test failure because the tg3 driver does not wait long enough for a link. kernel componentThe tg3 driver in Red Hat Enterprise Linux 6.2 does not include support for Jumbo frames and TSO (TCP Segmentation Offloading) on BCM5719 Ethernet controllers. As a result, the following error message is returned when attempting to configure, for example, Jumbo frames: SIOCSIFMTU: Invalid argument kernel componentThe default interrupt configuration for the Emulex LPFC FC/FCoE driver has changed from INT-X to MSI-X. This is reflected by the lpfc_use_msi module parameter (in /sys/class/scsi_host/host#/lpfc_use_msi) being set to 2 by default, instead of the previous 0. Two issues provide motivation for this change: SR-IOV capability only works with the MSI-X interrupt mode, and certain recent platforms only support MSI or MSI-X. However, the change to the LPFC default interrupt mode can bring out host problems where MSI/MSI-X support is not fully functional. Other host problems can exist when running in the INT-X mode. If any of the following symptoms occur after upgrading to, or installing Red Hat Enterprise Linux 6.2 with an Emulex LPFC adapter in the system, change the value of the lpfc module parameter, lpfc_use_msi, to 0: The initialization or attachment of the lpfc adapter may fail with mailbox errors. As a result, the lpfc adapter is not configured on the system. The following message appear in /var/log/messages: lpfc 0000:04:08.0: 0:0:0443 Adapter failed to set maximum DMA length mbxStatus x0lpfc 0000:04:08.0: 0:0446 Adapter failed to init (255), mbxCmd x9 CFG_RING, mbxStatus x0, ring 0lpfc 0000:04:08.0: 0:1477 Failed to set up hbaACPI: PCI interrupt for device 0000:04:08.0 disabled While the lpfc adapter is operating, it may fail with mailbox errors, resulting in the inability to access certain devices. The following message appear in /var/log/messages: lpfc 0000:0d:00.0: 0:0310 Mailbox command x5 timeout Data: x0 x700 xffff81039ddd0a00lpfc 0000:0d:00.0: 0:0345 Resetting board due to mailbox timeoutlpfc 0000:0d:00.0: 0:(0):2530 Mailbox command x23 cannot issue Data: xd00 x2 Performing a warm reboot causes any subsequent boots to halt or stop because the BIOS is detecting the lpfc adapter. The system BIOS logs the following messages: Installing Emulex BIOS ......Bringing the Link up, Please wait...Bringing the Link up, Please wait...
kernel componentThe minimum firmware version for NIC adapters managed by netxen_nic is 4.0.550. This includes the boot firmware which is flashed in option ROM on the adapter itself. kernel componentThe kdump kernel occasionally panics on a DELL PowerEdge R810 system with the i686 architecture. kernel componentRunning the LTP (Linux Testing Project) cgroup test suite on certain AMD systems causes NMI Watchdog to detect a hard LOCKUP and cause kernel panic. kernel component, BZ#683012 High stress on 64-bit IBM POWER series machines prevents kdump from successfully capturing the vmcore. As a result, the second kernel is not loaded, and the system becomes unresponsive. kernel componentLoading and unloading edac modules in a loop on certain HP systems may cause kernel panic. kernel componentIf the storage driver is loaded before multipathd is started, I/O errors occur. To work around this issue, use one of the following kernel command line parameters which are consumed by dracut: rdloaddriver=scsi_dh_emc or rdloaddriver=scsi_dh_rdac or rdloaddriver=scsi_dh_emc,scsi_dh_rdac The above command line parameters will cause the scsi_dh module to load before multipath is started. kernel componentTriggering kdump to capture a vmcore through the network using the Intel 82575EB ethernet device in a 32 bit environment causes the networking driver to not function properly in the kdump kernel, and prevent the vmcore from being captured. kernel component, BZ#701857 Attempting to hibernate certain laptops, including Lenovo ThinkPad T400 and Lenovo ThinkPad X200, can cause kernel panic. kernel componentOn a system configured with an HP Smart Array controller, during the kdump process, the capturing kernel can become unresponsive and the following error message is logged: NMI: IOCK error (debug interrupt?) As a workaround, the system can be configured by blacklisting the hpsa module in a configuration file such as /etc/modules.d/blacklist.conf, and specifying the disk_timeout option so that saving the vmcore over the network is possible. -
kernel component Memory Type Range Register (MTRR) setup on some hyperthreaded machines may be incorrect following a suspend/resume cycle. This can cause graphics performance (specifically, scrolling) to slow considerably after a suspend/resume cycle. To work around this issue, disable and then re-enable the hyperthreaded sibling CPUs around suspend/resume, for example: case $1 in hibernate|suspend) echo 0 > /sys/devices/system/cpu/cpu1/online echo 0 > /sys/devices/system/cpu/cpu3/online ; thaw|resume) echo 1 > /sys/devices/system/cpu/cpu1/online echo 1 > /sys/devices/system/cpu/cpu3/online ;esac kernel componentIn Red Hat Enterprise Linux 6.2, nmi_watchdog registers with the perf subsystem. Consequently, during boot, the perf subsystem grabs control of the performance counter registers, blocking OProfile from working. To resolve this, either boot with the nmi_watchdog=0 kernel parameter set, or run the following command to disable it at run time: echo 0 > /proc/sys/kernel/nmi_watchdog
To re-enable nmi-watchdog, use the following command echo 1 > /proc/sys/kernel/nmi_watchdog
kernel component, BZ#603911 Due to the way ftrace works when modifying the code during start-up, the NMI watchdog causes too much noise and ftrace can not find a quiet period to instrument the code. Consequently, machines with more than 512 CPUs will encounter issues with the NMI watchdog. Such issues will return error messages similar to BUG: NMI Watchdog detected LOCKUP and have either ftrace_modify_code or ipi_handler in the backtrace. To work around this issue, disable NMI watchdog by setting the nmi_watchdog=0 kernel parameter, or using the following command at run time: echo 0 > /proc/sys/kernel/nmi_watchdog
kernel componentOn 64-bit POWER systems the EHEA NIC driver will fail when attempting to dump a vmcore via NFS. To work around this issue, utilize other kdump facilities, for example dumping to the local file system, or dumping over SSH. kernel component, BZ#587909 A BIOS emulated floppy disk might cause the installation or kernel boot process to hang. To avoid this, disable emulated floppy disk support in the BIOS. kernel componentThe preferred method to enable nmi_watchdog on 32-bit x86 systems is to use either nmi_watchdog=2 or nmi_watchdog=lapic parameters. The parameter nmi_watchdog=1 is not supported. -
kernel component The kernel parameter, pci=noioapicquirk, is required when installing the 32-bit variant of Red Hat Enterprise Linux 6 on HP xw9300 workstations. Note that the parameter change is not required when installing the 64-bit variant.
PackageKit componentInstalling or updating packages signed with a GPG key not known or accessible to the system may throw PackageKit in a loop of password dialogues, repeatedly asking the user to confirm the installation of these packages from an untrusted source. This issue may occur if additional third party repositories are configured on the system for which the GPG public key is not imported into the RPM database, nor specified in the respective Yum repository configuration. Official Red Hat Enterprise Linux repositories and packages should not be affected by this issue. To work around this issue, import the respective GPG public key into the RPM database by executing the following command as root: ~]# rpm --import <file_containing_the_public_key> gnome-power-manager component, BZ#748704After resuming the system or re-enabling the display, an icon may appear in the notification area with a tooltip that reads: Session active, not inhibited, screen idle. If you see this test, your display server is broken and you should notify your distributor. Please see http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/ for more information. This error message is incorrect, has no effect on the system, and can be safely ignored. acroread componentRunning a AMD64 system without the sssd-client.i686 package installed, which uses SSSD for getting information about users, causes acroread to fail to start. To work around this issue, manually install the sssd-client.i686 package. kernel component, BZ#681257 With newer kernels, such as the kernel shipped in Red Hat Enterprise Linux 6.1, Nouveau has corrected the Transition Minimized Differential Signaling (TMDS) bandwidth limits for pre-G80 nVidia chipsets. Consequently, the resolution auto-detected by X for some monitors may differ from that used in Red Hat Enterprise Linux 6.0. fprintd componentWhen enabled, fingerprint authentication is the default authentication method to unlock a workstation, even if the fingerprint reader device is not accessible. However, after a 30 second wait, password authentication will become available. evolution componentEvolution's IMAP backend only refreshes folder contents under the following circumstances: when the user switches into or out of a folder, when the auto-refresh period expires, or when the user manually refreshes a folder (that is, using the menu item ⤍ ). Consequently, when replying to a message in the Sent folder, the new message does not immediately appear in the Sent folder. To see the message, force a refresh using one of the methods describe above. anaconda componentThe clock applet in the GNOME panel has a default location of Boston, USA. Additional locations are added via the applet's preferences dialog. Additionally, to change the default location, left-click the applet, hover over the desired location in the Locations section, and click the Set... button that appears. xorg-x11-server component, BZ#623169 In some multi-monitor configurations (for example, dual monitors with both rotated), the cursor confinement code produces incorrect results. For example, the cursor may be permitted to disappear off the screen when it should not, or be prevented from entering some areas where it should be allowed to go. Currently, the only workaround for this issue is to disable monitor rotation.
The cc-eal4-config-rhel62 package is now available for Red Hat Enterprise Linux 6. The cc-eal4-config-rhel62 package contains various artifacts from the Red Hat Enterprise Linux 6.2 Common Criteria evaluation. It includes a kickstart script to put the system into the certified configuration. It also includes the configuration guide to explain system administration details in managing certified systems. There is also a test plan that describes how the system is tested. Finally, the package contains the test suite used for the evaluation. This enhancement update adds the cc-eal4-config-rhel62 package to Red Hat Enterprise Linux 6. (BZ# 704340) All users who require cc-eal4-config-rhel62 should install this new package. New btparser packages are now available for Red Hat Enterprise Linux 6. The btparser is a backtrace parser and analyzer library, which works with backtraces produced by the GNU Project Debugger. It can parse a text file with a backtrace to a tree of C structures, allowing to analyze the threads and frames of the backtrace and process them. This enhancement update adds the btparser package to Red Hat Enterprise Linux 6. (BZ# 708038) All users who require btparser are advised to install this new package. A new fcoe-target-utils package is now available as a Technology Preview for Red Hat Enterprise Linux 6. The fcoe-target-utils package is a command line interface for configuring FCoE LUNs (Fibre Channel over Ethernet Logical Unit Numbers) and backstores. This enhancement update adds a new fcoe-target-utils package to Red Hat Enterprise Linux 6 as a Technology Preview. (BZ# 724035) More information about Red Hat Technology Previews is available here: All users who want to use the fcoe-target-utils Technology Preview should install this newly-released package, which adds this enhancement. A new libunistring package is now available for Red Hat Enterprise Linux 6. This portable C library implements the UTF-8, UTF-16 and UTF-32 Unicode string types, together with functions for character processing (names, classifications, and properties) and functions for string processing (iteration, formatted output, width, word breaks, line breaks, normalization, case folding, and regular expressions). This enhancement update adds the libunistring package to Red Hat Enterprise Linux 6. The libunistring package has been added as a dependency for the System Security Services Daemon (SSSD) in order to process internationalized HBAC rules on FreeIPA servers. (BZ# 726463) All users who require libunistring should install this new package. A new libvirt-qmf package is now available for Red Hat Enterprise Linux 6. The libvirt-qmf package contains a daemon to allow remote control of the libvirt API through the Qpid Management Framework (QMF). Enhancement- BZ#688194
With this update, the libvirt-qmf package obsoletes the libvirt-qpid package, which provided similar functionality. The new package uses the matahari library to provide an interface consistent with that of other Matahari agents. Note: After installation, it is advisable to convert existing QMF consoles, that previously connected to libvirt-qpid, to use libvirt-qmf as their interface. Also, when creating a new QMF console, it is recommended to use libvirt-qmf to communicate with libvirt.
All users requiring libvirt-qmf are advised to install this new package, which adds this enhancement. A new libvirt-snmp package is now available for Red Hat Enterprise Linux 6. The new package libvirt-snmp allows to control and monitor libvirt virtualization management tool by the way of the SNMP protocol. SNMP is an Internet-standard protocol for managing devices on IP networks, its modular structure allows it to be used in new fields and this new package allow virtualization management by bridging the SNMP protocol and the libvirt API. This enhancement update adds the libvirt-snmp package to Red Hat Enterprise Linux 6. (BZ# 642556, BZ# 706114) All users who require libvert-snmp are advised to install this new package. New mesa-libGLw packages are now available for Red Hat Enterprise Linux 6. The mesa-libGLw packages provide an Xt/Motif OpenGL Drawing Area Widget. This enhancement update adds the esa-libGLw package to Red Hat Enterprise Linux 6. (BZ# 729243) All users who require mesa-libGLw are advised to install these new packages. A new openslp package is now available for Red Hat Enterprise Linux 6. OpenSLP is an open source implementation of the Service Location Protocol (SLP) which is an Internet Engineering Task Force (IETF) standards track protocol and provides a framework to allow networking applications to discover the existence, location, and configuration of networked services in enterprise networks. This enhancement update adds the openslp package to Red Hat Enterprise Linux 6. (BZ# 518286) All users who require OpenSLP are advised to install this new package. A new passsync package is now available for Red Hat Enterprise Identity Replication. PassSync is a Windows service that runs on every domain controller. This intercepts clear text password updates and sends them to the directory server running on Red Hat Enterprise Linux. PassSync works together with the Windows Synchronization (WinSync) feature of the directory server to keep passwords synchronized between Active Directory (AD) and the directory server running on Red Hat Enterprise Linux. This enhancement update adds the passsync package to Red Hat Enterprise Identity Replication which is an add-on for Red Hat Enterprise Linux 6. (BZ# 690622) Users who require password synchronization together with WinSync are advised to install this new package. A new perl-Test-Inter package is now available for Red Hat Enterprise Linux 6. The Test::Inter module provides a framework for writing interactive test scripts in Perl. It is inspired by the Test::More framework. This enhancement update adds the perl-Test-Inter package to Red Hat Enterprise Linux 6. (BZ# 705752) All users who require perl-Test-Inter should install this new package. A new python-configshell package is now available for Red Hat Enterprise Linux 6. The python-configshell package provides a library for implementing configuration command line interfaces for the Python programming environment. This enhancement update adds the python-configshell package to Red Hat Enterprise Linux 6 as part of the Technology Preview of Fibre Channel over Ethernet (FCoE) target mode. (BZ# 726774) This package is provided as a dependency of the fcoe-target-utils package. It is recommended to install it only as a prerequisite for running fcoe-target-utils, and not to use it independently. All users who want to use the Technology Preview of Fibre Channel over Ethernet target mode should install this newly-released package, which adds this enhancement. A new python-ipaddr package is now available for Red Hat Enterprise Linux 6. The python-ipaddr package is a library for working with IPv4 and IPv6 addresses for the Python programming environment. This enhancement update adds the python-ipaddr package to Red Hat Enterprise Linux 6. (BZ# 726773) This is being added as part of the Tech Preview of FCoE (Fibre Channel over Ethernet) target mode, as a dependency of fcoe-target-utils. It is recommended to install this library only as a prerequisite for running fcoe-target-utils, and it should not be used independently. A new python-rtslib package is now available for Red Hat Enterprise Linux 6. The python-rtslib package provides a library for interacting with storage target-related interfaces for the Python programming environment. This enhancement update adds the python-rtslib package to Red Hat Enterprise Linux 6 as part of the Technology Preview of Fibre Channel over Ethernet (FCoE) target mode. (BZ# 726778) This package is provided as a dependency of the fcoe-target-utils package. It is recommended to install it only as a prerequisite for running fcoe-target-utils, and not to use it independently. All users who want to use the Technology Preview of Fibre Channel over Ethernet target mode should install this newly-released package, which adds this enhancement. A new python-simpleparse package is now available for Red Hat Enterprise Linux 6. The python-simpleparse package is a simple and fast parser generator for the Python programming environment. This enhancement update adds the python-simpleparse package to Red Hat Enterprise Linux 6 as part of the Technology Preview of Fibre Channel over Ethernet (FCoE) target mode. (BZ# 726776) This package is provided as a dependency of the fcoe-target-utils package. It is recommended to install it only as a prerequisite for running fcoe-target-utils, and not to use it independently. All users who want to use the Technology Preview of Fibre Channel over Ethernet target mode should install this newly-released package, which adds this enhancement. The python-suds package is now available for Red Hat Enterprise Linux 6 Server and Red Hat Enterprise Linux High Performance Compute Node. The python-suds package provides a lightweight implementation of the Simple Object Access Protocol (SOAP) for the Python programming environment. This enhancement update adds the python-suds package to Red Hat Enterprise Linux 6 Server and Red Hat Enterprise Linux High Performance Compute Node. Previously it was only available with the Red Hat Enterprise Linux High Availability and Red Hat Enterprise Linux Resilient Storage add-on products. (BZ# 765896) All users who require python-suds are advised to install this new package. A new python-suds package is now available for Red Hat Enterprise Linux 6. The python-suds package provides a lightweight implementation of the Simple Object Access Protocol (SOAP) for the Python programming environment. This enhancement update adds the python-suds package to Red Hat Enterprise Linux 6. (BZ# 681835) All users who require python-suds are advised to install this new package. A new python-urwid package is now available for Red Hat Enterprise Linux 6. The python-urwid package provides a library for development of text user interface applications in the Python programming environment. This enhancement update adds the python-urwid package to Red Hat Enterprise Linux 6 as part of the Technology Preview of Fibre Channel over Ethernet (FCoE) target mode. (BZ# 726775) This package is provided as a dependency of the fcoe-target-utils package. It is recommended to install it only as a prerequisite for running fcoe-target-utils, and not to use it independently. All users who want to use the Technology Preview of Fibre Channel over Ethernet target mode should install this newly-released package, which adds this enhancement. A new sanlock package is now available for Red Hat Enterprise Linux 6. The sanlock package provides a shared disk lock manager that uses disk paxos to manage leases on shared storage. Hosts connected to a common Storage Area Network (SAN) can use sanlock to synchronize the access to the shared disks. Both libvirt and vdsm can use sanlock to synchronize access to shared virtual machine (VM) images. This enhancement update adds the sanlock package to Red Hat Enterprise Linux 6. (BZ# 658971) All users who require sanlock are advised to install this new package. New sgabios packages are now available for Red Hat Enterprise Linux 6. The sgabios packages provide the Google Serial Graphics Adapter BIOS (SGABIOS) for legacy 86-bit software to communicate with an attached serial console. This enhancement update adds the new sgabios packages to Red Hat Enterprise Linux 6. (BZ# 725832) All users who require SGABIOS are advised to install these new packages. New spice-gtk packages are now available for Red Hat Enterprise Linux 6. spice-gtk is a GTK2 widget for SPICE clients. Both virt-manager and virt-viewer can make use of this widget to access virtual machines using the SPICE protocol. This enhancement update adds spice-gtk to Red Hat Enterprise Linux 6. (BZ# 708417) All users of SPICE clients such as virt-manager or virt-viewer are advised to install these new packages. A new tboot package is now available for Red Hat Enterprise Linux 6. The tboot package provides Trusted Boot (tboot), an open source pre- kernel/VMM module, that uses Intel Trusted Execution Technology (Intel TXT) to initialize the launch of a operating system kernels and virtual machines. This enhancement update adds tboot to Red Hat Enterprise Linux 6. (BZ# 691617) All users wishing to evaluate trusted boot capabilities are advised to install this new package. A new vios-proxy package is now available as a Technology Preview for Red Hat Enterprise Linux 6. The vios-proxy program suite creates a network tunnel between a server in the QEMU host and a client in a QEMU guest. The proxied server and client programs open normal TCP network ports on localhost and the vios-proxy tunnel connects them using QEMU virtioserial channels. This enhancement update adds a new vios-proxy package to Red Hat Enterprise Linux 6 as a Technology Preview. (BZ# 721119) More information about Red Hat Technology Previews is available here: All users who want to use the vios-proxy Technology Preview should install this newly-released package, which adds this enhancement. A new virt-who package is now available for Red Hat Enterprise Linux 6. The virt-who package provides an agent that collects information about virtual guests present in the system and reports them to the Red Hat Subscription Manager tool. This enhancement update adds the virt-who package to Red Hat Enterprise Linux 6. (BZ# 725832) All users are advised to install this new package. A new wdaemon package is now available for Red Hat Enterprise Linux 6. The new wdaemon package contains a daemon to wrap input driver hotplugging in the X.Org implementation of the X Window System server. The wdaemon package emulates virtual input devices to avoid otherwise non-persistent configuration of Wacom tablets to persist across device removals. This enhancement update adds the wdaemon package to Red Hat Enterprise Linux 6. All users who require wdaemon should install this new package. |
| |
