Edition 0
1801 Varsity Drive
Raleigh, NC 27606-2072 USA
Phone: +1 919 754 3700
Phone: 888 733 4281
Fax: +1 919 754 3701
OEMDRV for driver updates and applies any updates that it finds there. Previously, anaconda searched for this label on the devices listed in /proc/partitions. However, /proc/partitions does not identify CD or DVD media, so anaconda overlooked optical disks that had the correct label. Anaconda now examines the devices listed in /sys/block. Therefore, anaconda correctly identifies CDs and DVDs labelled OEMDRV as driver discs and automatically applies any driver updates contained on them. (BZ#485060)
HOTPLUG when writing the system's networking configuration files, although it did write a value for ONBOOT. Because HOTPLUG is enabled by default, the effect of disabling ONBOOT was limited because any interface not activated at boot time would be enabled anyway whenever probed by the system. Anaconda now writes a value for HOTPLUG, setting it to the same value as ONBOOT. Therefore, any network interface not meant to be enabled at boot time will not be automatically enabled by probing either. (BZ#498086)
part kickstart command accepts an option called --label that allows a label to be applied to a disk partition during a kickstart installation. However, the code that implemented this option was previously missing from anaconda. Any label specified in a kickstart file was therefore ignored. Anaconda now includes code to transfer the specified label from the kickstart file to the disk partition. Users can now label disk partitions during kickstart installations. (BZ#498856)
fstab by label rather than by device name. Therefore, if the root (/) partition were identified in this way, the usefulness of rescue mode would be limited. Anaconda in rescue mode now uses the getLabels() method to find partitions and therefore properly detects root partition even if it resides on a logical volume and is identified by label in fstab. (BZ#502178)
NETTYPE for IBM System z systems did not mention HiperSockets. Users new to System z might therefore not have known to choose qeth to configure HiperSocket interfaces on their hardware. The help text has now been updated to indicate the correct choice and users can select the appropriate option. (BZ#511962)
RUNKS was set to 0 in the CMSCONFFILE file on IBM System z systems, anaconda should have performed an installation in interactive mode. However, a rewrite of linuxrc.s390 changed the behavior of RUNKS and led to anaconda ignoring this variable. Installation would therefore proceed in non-interactive mode regardless of what value was set in CMSCONFFILE. A new test is now included in the version of linuxrc.s390 in Red Hat Enterprise Linux 5.5 so that anaconda honors RUNKS=0 and performs an interactive install if this value is set. (BZ#513951)
OEMDRV as a driver disc and searches it for a driver update. However, anaconda previously failed to examine dev nodes and therefore, it would not recognize this label on USB storage devices mounted as a partitionless block devices. Anaconda now examines dev nodes for the label OEMDRV and treats them the same as partitions with this label. It is therefore possible to use a partitionless device as a driver disc. (BZ#515437)
[address]:port form to comply with the relevant RFCs. This form removes ambiguity, since IPv6 addresses are still valid if they omit a sequence of bytes with zero values. When IPv6 addresses are specified in this format, anaconda parses them correctly and installation continues as normal. (BZ#525054)
#) at the start of the line. However, anaconda did not previously account for the possibility that users might mark a comment with multiple pound symbols (for example, #####). Anaconda would therefore attempt to parse lines that started with multiple pound symbols and installation would fail. Anaconda now recognizes lines that start with multiple pound symbols as comments and does not attempt to parse them. Users can now safely mark comments in kickstart files in this way. (BZ#525676)
mpath boot option, iSCSI devices detected on more than one path would be represented in the installer multiple times, one for each path. Anaconda now automatically loads the mpath boot option and therefore represents multipath devices correctly. (BZ#538129)
ksdevice=link is set in a kickstart file, anaconda should automatically select the first available network interface and use it during installation. This avoids the need for user input and allows installation to proceed unattended. However, if interfaces were in a state where anaconda could not determine their status, anaconda would revert to interactive more and prompt the user to select a network interface, thus making unattended installation impossible on systems where network interfaces could be in such a state. Anaconda now forces the network interfaces on the system into IFF_UP and IFF_RUNNING states before it attempts to obtain link status. Because the interfaces are now in a state where they can report their link status to anaconda, Anaconda can automatically choose one to use during installation and kickstart installations can proceed unattended. (BZ#549751)
IPADDR in the conf file has changed recently, network interfaces take longer to respond. Anaconda now prompts the user only when three pings have failed and therefore avoids prompting the user for gateway information that is already correctly specified in the conf file. (BZ#506742)
--hvargs and sets Hypervisor parameters accordingly. (BZ#501438)
multipath kickstart command with --name and --device options that allow users to specify a LUN for root. (BZ#502768)
ks= boot option, users can provide a passphrase to allow anaconda to retrieve the kickstart files fom a protected server. (BZ#505424)
/tmp together with a log. These records make troubleshooting kickstart installations easier. (BZ#510636)
#! /usr/bin/python instead of #! /usr/bin/env python). This ensures that anaconda functions correctly when more than one Python stack is present on a system. (BZ#521337)
@ prefix, it was not possible to exclude package groups from installation, only individual packages. Anaconda now supports excluding package groups with the -@ prefix (BZ#558516)
xmlCleanupParser concurrently from multiple threads, as this function is not re-entrant. autofs has been changed to call this function only once from its main thread, when the application exits. (BZ#513289)
gfs2_glock_hold function was called within the gfs2_process_unlinked_inode function. This was due to the fact that gfs2_glock_hold was being called without a reference already held on the inode in question. This update, resolves this problem by changing the order in which it acquires references to match that of the NFS code, thus, kernel panic no longer occurs.
GFS2 hang. This update fixes the problems with inodes getting stuck in certain states, thus, the hangs no longer occur.
bfsort whitelist, however the HP ProLiant DL580 G7 Server was not. This caused the scripts running under HP ProLiant DL580 G7 Server to not work properly. With this update, the HP ProLiant DL580 G7 Server has been added to the bfsort whitelist.
tg3 driver interface with vlan support from bond, a "scheduling while atomic" error (i.e. a thread has called the schedule() function during an operation which is supposed to be atomic, i.e uninterrupted) occurred and, consequently, the system encountered a deadlock. With this update, the aforementioned error no longer occurs and removing a slave tg3 driver interface works as expected.
kstopmachine threads which repeat acquiring and releasing of each spinlock of their local run queue by calling the yield() function. If an interruption occurs at that time and its handler requires one of those spinlocks, the operation fails to acquire the lock and the system hangs up. With this update, run queue spinlock starvation is avoided, thus, the system no longer hangs.
transitioning states did not work properly due to a faulty SCSI (Small Computer System Interface) ALUA handler. With this update, optimized state transitioning prevents the aforementioned behavior.
qla24xx_queuecommand function, a Red Hat Enterprise Linux 5.5.z QLogic Fibre Channel host would panic during I/O with controller faults. This update fixes the null pointer dereference, thus, the system no longer panics.
qla4xxx driver and FC (Fibre Channel) drivers using the fc class, a device might have been put in the offline state due to a transport problem. Once the transport problem was resolved, the device was not usable until a user manually corrected the state. This update enables the transition from the offline state to the running state, thus, fixing the problem.
uhci_irq() function was called between the uhci_stop() and free_irq() functions. This update avoids the aforementioned crash and the system works as expected.
bnx2-based devices, frames could drop unexpectedly. This was shown by the increasing rx_fw_discards values in the ethtool --statistics output. With this update, frames are no longer dropped and all bnx2-based devices work as expected.
balance-rr bonding did not work properly. This resulted in non-functioning network interfaces unless the the bond0 interface had the promiscuous mode enabled. With this update, network balance-rr bonding works as expected, thus, preventing the aforementioned issue.
dentry unused counter (nr_unused) failed to update properly. As a result, the counter would contain negative values. When trying to reference the counter, dcache would loop indefinitely. With this update, the nr_unused counter has been updated, thus, it now works properly and no longer causes indefinite loops.
GFS and GFS2 file systems performed poorly when compared to, for example, the ext3 file system. With this update, steps have been taken to ensure the best performance possible with the aforementioned file systems.
execve() function was transferring the data. With this update, fatal signals (like CTRL-c) can now be received and handled and a process is allowed to yield to higher priority processes during the data transfer.
create_by_name() function tested an error pointer (ERR_PTR) against dentry instead of *dentry. If "*dentry" was an ERR_PTR, it would be dereferenced in either the mkdir() function or the create() function which could cause kernel panic. With this update, the typographical error has been fixed, thus, kernel panic no longer occurs in the aforementioned case.
lpfc driver would incorrectly panic due to a null pnode dereference. This update addresses the issue and was tested successfully under the same test conditions without the panic occurring.
lpfc driver panicked during error handling. With this update, kernel panic no longer occurs.
off.
netback driver failed to transition from the InitWait state to the Connected state after it was closed once. This was due to the fact that at the moment the netdev_state_change function was called, the interface was still down, so the NETDEV_CHANGE event was not called. This update makes sure the interface is up (via the NETDEV_UP event) and correctly changes the states.
gso_size variable that did not conform to the specification. With this update, faulty values are no longer generated and kernel panic no longer occurs.
sync/noac of NFSv4 could cause kernel panic. This problem did not occur when an optional mount was set as a default. The kernel panic was caused by improperly setting the lock_context field in nfs_writepage_sync. With this update, the aforementioned issue has been fixed and kernel panic no longer occurs.
nfs_flush_incompatible. This was caused by problematic calls to the nfs_clear_context function. With this update, calls to the nfs_clear_context function work as expected and the system no longer crashes.
sync/noac of NFSv4 could cause kernel panic. This problem did not occur when an optional mount was set as a default. The kernel panic was caused by the lock_context field being added to the nfs_writedata but missing the functionality to be filled out in the nfs_writepage_sync codepath. With this update, a new function was added to properly handle the lock_context field, thus, kernel panic no longer occurs.
sfc driver adds support for the Solarstorm SFC9000 family of Ethernet controllers.
NULL pointer dereference flaw was found in the io_submit_one() function in the Linux kernel asynchronous I/O implementation. A local, unprivileged user could use this flaw to cause a denial of service. (CVE-2010-3066, Moderate)
xfs_ioc_fsgetxattr() function in the Linux kernel XFS file system implementation. A data structure in xfs_ioc_fsgetxattr() was not initialized properly before being copied to user-space. A local, unprivileged user could use this flaw to cause an information leak. (CVE-2010-3078, Moderate)
__futex_atomic_op1, __futex_atomic_op2, and futex_atomic_cmpxchg_inatomic() macros replaced the LOCK prefix with a NOP instruction. A local, unprivileged user could use this flaw to cause a denial of service. (CVE-2010-3086, Moderate)
tcf_act_police_dump() function in the Linux kernel network traffic policing implementation. A data structure in tcf_act_police_dump() was not initialized properly before being copied to user-space. A local, unprivileged user could use this flaw to cause an information leak. (CVE-2010-3477, Moderate)
sys_io_submit() function in the Linux kernel asynchronous I/O implementation. A local, unprivileged user could use this flaw to cause an information leak. (CVE-2010-3067, Low)
802.3ad link aggregation did not work properly when using the ixgbe driver. This was caused due to an inability to form 802.3ad-based bonds. With this update, the issue causing 802.3ad link aggregation to not work properly has been fixed. (BZ#644822)
IGMP join packets. With this update, the driver sends IGMP join packets and the multicast domain is rejoined immediately. (BZ#640973)
UP and PV drivers, may have caused the guest to stop responding. With this update, HVM guest migration works as expected. (BZ#630989)
lvextend during an intensive Virtual Guest power up caused this operation to fail. Since lvextend was blocked, all components became non-responsive: vgs and lvs commands froze the session, Virtual Guests became Paused or Not Responding. This was caused by a faulty use of a lock. With this update, performing an lvextend operation works as expected. (BZ#632255)
iomem resources, which were enumerated using the PNP Motherboard resource descriptions, were not recognized and taken into consideration when gathering resource information. This could have caused MMIO-based requests to receive allocations that were not valid. With this update, system board iomem resources are correctly recognized when gathering resource information. (BZ#629861)
NOT_READY on standby path. (BZ#634977)
megaraid_sas driver (for SAS based RAID controllers) handled physical disks and management IOCTLs (Input/Output Control). All physical disks were exported to the disk layer, allowing an oops in megasas_complete_cmd_dpc() when completing the IOCTL command if a timeout occurred. One possible trigger for this bug was running mkfs. This update resolves this issue by updating the megaraid_sas driver to version 4.31. (BZ#619365)
RELEASE_LOCKOWNER operation has been implemented for NFSv4 in order to avoid an exhaustion of NFS server state IDs, which could result in an NFS4ERR_RESOURCE error. Furthermore, if the NFS4ERR_RESOURCE error is returned by the NFS server, it is now handled correctly, thus preventing a possible reason for the following error:
NFS: v4 server returned a bad sequence-id error!
pmt_update_time() function. With this update, time is kept accurately and no longer drifts backwards. (BZ#641915)
dasd_sleep_on functions use a global wait queue when waiting for a CQR (Channel Queue Request). Previously, the wait condition checked the status and devlist fields of the CQR to determine if it is safe to continue. This evaluation may have returned true, although the tasklet did not finish processing the CQR and the callback function had not been called yet. When the callback was finally called, the data in the CQR could have already been invalid. With this update, the sleep_on wait condition has a safe way to determine if the tasklet has finished processing, thus, preventing the aforementioned behavior. (BZ#638579)
ICMP packets corrupted the kernel memory. This was caused by a flaw in net/ipv4/proc.c. With this update, kernel memory is no longer corrupted when receiving 8 or more different types of ICMP packets. (BZ#634976)
/proc/acpi/ibm/video in order to prevent the aforementioned crash. (BZ#629241)
NULL pointer in the lpfc_nlp_put() function may have caused the system to crash. With this update, several changes have been made to ensure the correct reference count, resolving this issue. (BZ#637727)
dd command on an iSCSI device with the qla3xxx driver may have caused the system to crash. This error has been fixed, and running the dd command on such device no longer crashes the system. (BZ#637206)
divider=x kernel parameter set to a value greater than 1 and that showed the following line of text in the kernel boot messages were the subject of the aforementioned behavior:
time.c: Using 3.579545 MHz WALL PM GTOD PM timer
log_mtts_per_seg was increased from 5 to 7, increasing the amount of memory that can be registered. Machines with larger memory are now able to register more memory. (BZ#643806)
64-bit PowerPC-specific.
libfc bug fixes and improvements. BZ#526259
smp_call_function_[single|many] in x86_64 and i386. BZ#526043
smp_call_function_single() and smp_call_function_many() functions. This update provides a single function that can refer to the appropriate function as required, thereby simplifying the creation of further updates.
zfcp parameter to dynamically adjust scsi_queue_depth size. BZ#508355
/proc/acpi/processor BZ#537395
sched_rr_get_interval() is compiled on x86 and is executed on x86_64, it will destroy the user stack. This problem is solved by calling sys32_sched_rr_get_interval() instead of sys_sched_rr_get_interval() when sched_rr_get_interval() is called.
clock_gettime(CLOCK_REALTIME) and the time returned by gettimeofday(), even if a program executes one call right after the other.
iucv_query_maxconn(). BZ#524251
max_connections. This is because the wrong output register was used when querying the maximum number of IUCV connections.
set online or set offline routines failed for a DASD device. Afterwards this device could neither be set online nor offline.
set online, set offline, and related rollback and error routines are only processed if the device is in a FINAL or DISCONNECTED state.
n paths and that device is not path-grouped, and an internal I/O command fails, then the control unit presents the error sense n times on each different path. Because CIO only performs five retries, devices with five or more paths run out of retries before their functional status can be correctly determined.
__setup()) was being called twice. This update removes those function calls, and the affected kernel parameters now behave as expected.
/proc/cpuinfo BZ#517928
/proc/cpuinfo only showed the original set of flags supported from the base kernel release. It did not include new features present in supported CPUs. This update addresses this problem, and applies to both x86 and x86_64 architectures.
xen/arch/x86/ioport_emulate.c in the Xen variants of Red Hat Enterprise Linux 5. BZ#536677
kvm_get_tsc_khz() BZ#531025
xsave and osxsave bits to prevent this problem from occurring.
ida flag on Xen kernels. BZ#522846
ida flag, which indicates the presence of the Turbo Boost feature, was not seen in the cpuflags section of /proc/cpuinfo on Xen kernels. This occurred on both 32-bit and 64-bit Xen kernels.
xenheap_megabytes hypervisor option to address this problem. For example, if the installed memory exceeds 64GB, it is suggested to set the option to a value equal to the memory size in gigabytes. For example, on a system with 128GB of memory, the elilo.conf file should include the directive: append="xenheap_megabytes=128 --"
/proc/sys/net/ipv4/route/secret_interval to 0, you could not reset it to another value, and /bin/bash would hang on the echo.
/proc/sys/net/ipv4/route/secret_interval can now be set to 0 and successfully reset to another value without causing /bin/bash to hang. BZ#510067
dprintk() macro works everywhere. BZ#532701
nfs4_do_open_expired() to prevent infinite loops. BZ#526888
nfs4_do_open_expired() that could lead to the reclaimer thread going into an infinite loop. This bug was triggered when the client received an NFS4ERR_DELAY from the server, and the exception.retry bit was set, enforcing a timeout. This bit was never reset to zero (0) when the server recovered, leading to an infinite loop.
statfs on NFS partitions always returned a zero (0) value, regardless of success or fail. On fail, statfs should return a negative number.
statfs behaves as expected.
open() with the O_APPEND flag, and then issuing a write() without first performing another operation on the inode, such as stat() or read().
httpd Sendfile problems reading from a CIFS share. BZ#486092
CIFSGetSrvInodeNumber BZ#529431
aio_complete() code path.
ki_flags to address this problem.
drop_pagecache_sb(). BZ#528070
dcache_lock. BZ#526612
lock_super with explicit resize lock. BZ#525100
resize2fs BZ#515759
/proc/1/task/1/ as DT_UNKNOWN BZ#509713
/proc/<pid>/smaps file cannot be read because the file's permissions only allow access from a task with the original root UID value.
/proc/<pid>/smaps file is now created with S_IRUGO permissions (-r--r--r--), which means it can be read even when running a setuid binary. BZ#322881
unblock function of the SCSI layer.
snapshot_status() function, the counts were being read without holding the lock. This could result in invalid intermediate values being reported.
mmap() with PROT_WRITE on Red Hat Enterprise Linux 5 was incompatible with Red Hat Enterprise Linux 4. BZ#562761
munmap() would fail with an ENOMEM error if:
ioremap to prevent kernel hang when using recent NVIDIA display drivers. BZ#549465
BUG() call in the __change_page_attr() routine.
vfs_check_frozen() after unlocking the spinlock. BZ#541956
audit_tree.c BZ#549750
auditctl -R audit.rules which unloads and then loads rules that include (for exeample) "-F dir=/var/log/audit" or "-F dir=/lib", it would result in a kernel OOPS.
platform_device_add_data(). BZ#564399
platform_device_add_data(). BZ#560944
platform_device_add_data(). BZ#559950
platform_device_add_data(). BZ#557172
khungtaskd not stopped during suspend. BZ#550014
0 = enable traditional pin-based interrupt mechanism 1 = enable MSI-X interrupt mechanism 2 = enable MSI interrupt mechanism
scsi_dh_activate() asynchronous to address the slower LUN failovers with large numbers of LUNs. BZ#537514
max_lun BZ#531488
rwsem_is_locked() function. BZ#526092
cpufreq_get on DL785-G6. BZ#523505
cpufreq_get which sometimes causes a kernel panic on HP DL785-G6 machines running Red Hat Enterprise Linux 5.3 and 5.4.
pci_bus_show_cpuaffinity() BZ#519633
/sys/class/pci_bus/0000:ff/cpuaffinity (using cat or a similar function) would cause the kernel to crash and the system to reboot. This update provides a solution to this problem.
pipe() is called with an invalid address. BZ#509625
sprintf() use were found in the Linux kernel Bluetooth implementation. Creating a large number of Bluetooth L2CAP, SCO, or RFCOMM sockets could result in arbitrary memory pages being overwritten. A local, unprivileged user could use this flaw to cause a kernel panic (denial of service) or escalate their privileges. (CVE-2010-1084, Important)
CIFSSMBWrite() function in the Linux kernel Common Internet File System (CIFS) implementation. A remote attacker could send a specially-crafted SMB response packet to a target CIFS client, resulting in a kernel panic (denial of service). (CVE-2010-2248, Important)
mext_check_arguments() function in the ext4 file system code. A local user could use this flaw to cause the MOVE_EXT IOCTL to overwrite the contents of an append-only file on an ext4 file system, if they have write permissions for that file. (CVE-2010-2066, Low)
possible circular locking dependency detected warning was triggered. With this update, the warning is no longer displayed and the loading of a USB mass storage driver under kernel-debug works as expected. BZ#607483
bnx2x network driver (10 Gb), TCP bandwidth problems occurred, causing transfer rate slowdowns (down to 400 Kb) and network delays. The network traces shown that the reason for the TCP bandwidth problems were TCP delayed ACK mechanisms. This update improves the packet-handling code so that network ACKs are not delayed when using TPA, GRO (Generic Receive Offload), or LRO (Large Receive Offload) with the bnx2x driver, thus leading to increased networking performance. BZ#613900
/var/log/messages directory during IO runs. With this update, the firmware dump errors no longer appear in the /var/log/messages directory. BZ#613688
CNIC driver, occasionally, data structures were freed when the device was down. If at that moment an ISCSI netlink message was received, a crash occurred. With this update, the crash no longer occurs. BZ#615260
acpiphp module (using the /sbin/modprobe command) on a Intel Xeon processor 7500 series system caused kernel panic. With these updates, an error message is produced when the aforementioned case occurs and the machine does not panic. BZ#607486
ecryptfs_uid_hash() function in the Linux kernel eCryptfs implementation. On systems that have the eCryptfs netlink transport (Red Hat Enterprise Linux 5 does) or where the /dev/ecryptfs file has world writable permissions (which it does not, by default, on Red Hat Enterprise Linux 5), a local, unprivileged user could use this flaw to cause a denial of service or possibly escalate their privileges. (CVE-2010-2492, Important)
msleep() calls with the MDELAY() macro and handles the locking properly. BZ#620661
msi_nolock, which allows for better simultaneous processing of MSIs. BZ#621940
mmap() or munmap() function on /dev/zero decreased the performance on multiple threads. This update allows the user to switch off the optimization by typing echo 0 > /proc/sys/vm/vm_devzero_optimization at a shell prompt as superuser. BZ#623141
/proc/cpuinfo when running a kernel-xen kernel. This has been fixed, and /proc/cpuinfo now contains all CPU flags as expected. BZ#624365
ccw_device_set_options() in dasd_generic_probe() unset the CWDEV_ALLOW_FORCE flag set in dasd_eckd_probe() and the unconditional reserve was not allowed on ECKD dasds. This update sets flags only in discipline specific probe functions. BZ#627194
cpu_set variable to 1 online in the qemu Monitor and then shutting down the guest would cause the host or the guest to crash. The updated package resolves this issue and prevents the host or guest from crashing in this scenario. (BZ#487857)
virtio-net) lacked non-maskable interrupt (NMI) injection masking on AMD-based hosts. This caused Windows XP guests using the para-virtualized network driver could fail with a Blue Screen error during certain tests. The updated packages resolve this issue. (BZ#492290)
there is no bootable disk" error presented the qemu process used 100% of the available CPUs. The updated packages resolve this issue and the interrupt is now handled correctly. (BZ#502086)
i82551 emulated network interface card was used. The segmentation fault is fixed in the packages. (BZ#510706)
qemu-kvm process. The updated packages resolve this issue. (BZ#542923)
migrate_set_speed command in the QEMU console after running migrate_cancel causes segmentation fault in KVM. The updated packages fix this issue and the code causing the segmentation fault is fixed. (BZ#522887)
qemu-img rebase command to rebase an image snapshot. (BZ#563141)
qemu-img rebase command failed with an "Operation not supported" error message when it was run on locally-attached block devices. (BZ#569762)
qemu-img command failed to copy a RAW image to a Fibre Channel storage device. The qemu-image command can now copy, convert and create images on Fibre Channel storage devices. (BZ#511072)
raw_pread system call. The offset was larger than the file size of the read failures which causes the system to infinitely loop I/O requests. This could, in certain circumstances lead to file system corruption on virtualized guests. The updated pacakges add a result test which prevents the infinite request loop. (BZ#515655)
msrs) in kvm_arch_save_regs() function. The array was sized too small for the function and may cause stack corruption. (BZ#528917)
virtio_blk_dma_restart_bh() function previously handled write errors. The function was not updated for this, causing read errors to be resubmitted as writes. This caused guest image corruption in some cases.
bdrv_aio_write() and bdrv_aio_read() functions were ignored. If an immediate failure occurred in one of these functions, errors would be missed and the guest could hang or read corrupted data. (BZ#552487)
qemu-kvm command's -drive "werror=stop" option now applies not only to write errors but also to read errors. When using this option, guests will pause on disk read and write errors.
"werror=stop" option. This option is not used by default for guests managed by libvirt. (BZ#533390)
vm8086 mode, bugs in the emulated hardware task switching implementation may have caused older guest operating systems to malfunction. (BZ#517324)
unhandled vm exit: 0x31 vcpu_id 0" error message could appear when installing certain guest operating systems, such as SUSE Linux Enterprise Server 11, using a para-virtualized block device (virtio-blk). The updated packages resolve this issue and installation with the para-virtualized drivers is supported and working. (BZ#518081)
__kvm_mmu_free_some_pages list was not verified empty before it was used. The updated package verifies the __kvm_mmu_free_some_pages list is empty before attempting to look at list entries. (BZ#519397)
cr8 call which executed a vmexit call. This caused performance issues for Windows Server 2008 guests. The updated packages use a different call method to handle cr8 calls which significantly improves the performance of Windows Server 2008 64 bit guests. (BZ#520285)
snd_playback_stop: ASSERT playback_channel->base.active failed" error message to appear and the resume process to fail and the guest to crash. The updated package resolves this issue. (BZ#520394)
Setup will continue after restarting your computer". This issue is resolved and Windows Server 2008 R2 Datacenter guests now successfully install. (BZ#521749)
aio threads to return. The updated packages resolve this issue by correctly timing out threads which do not return. (BZ#525114)
.zrom file. KVM would always used the default, the ne.zrom file. Guests could not get an IP address or access PXE servers. The updated packages resolve this issue and guests can access PXE server when using non-default network devices. (BZ#526124)
initrd images greater than 4GB would cause the guest to crash. KVM now limits the size of initrd images to less than 4GB. (BZ#529694)
qemu-kvm command's -net user option was used, unattended Windows XP installations would not receive an IP address after rebooting. The guest requests a second DHCP address which makes the list of free DHCP addresses run out much quicker. This issue is fixed by reassigning the same addressed requested with DHCP to the guest after the guest reboots. (BZ#531631)
BAD_POOL_HEADER" stop error. (BZ#531887)
HAL_RTC_IRQF_WILL_NOT_CLEAR" stop error. (BZ#556455)
unhandledvm exit error during reboot. The hypervisor now handles this error, resolving the issue. (BZ#532086)
grow_refcount_table() error handling caused infinite recursion in some cases. This caused the qemu-kvm process to hang and eventually crash. (BZ#537075)
qemu-img command, Fibre Channel devices could not be formatted using RAW or use preallocated RAW devices. The qemu-img command is updated to handle Fibre Channel devices in the RAW format. (BZ#537655)
qcow2 file format unnecessarily rounded up the length of the backing format string to the next multiple of 8. The array in BlockDriverState can only store 15 characters, causing backing formats with 9 characters or more to fail. This issue effected devices using the host_device format. The updated packages resolve this issue by determining the length of the backing format of qcow2 devices. (BZ#540893)
qxl_display_update: waiting for command" error message to be printed in the logs. The updated packages resolve this issue. (BZ#544785)
qemu-kvm man page incorrectly described the qcow2 default as cache=writeback. The default is cache=none for qcow2 images and cache=writethrough for all other disk types. The man page for qemu-kvm has been updated to reflect this. (BZ#545194)
kvm-qemu-img command failed to convert sparse RAW image files to qcow2 sparse snapshot image files. (BZ#558195)
-M rhel5.5.0 parameter did not work for migration to or from Red Hat Enterprise Linux 5.5. Migration with the -M parameter is now supported and functional. (BZ#559163)
-initrd option was used. (BZ#512672)
paging64_sync_page() call was executed on a system using PCI passthrough devices. This kernel panic error could occur if a guest with an attached PCI device was started. The updated packages resolve this issue. (BZ#566385)
qemu_popen: returning result of qemu_fopen_ops that displayed when saving a virtualized guest state into a compressed file. (BZ#530533)
MSR_KERNEL_GS_BASE intercept calls for Windows Server 2008 guests. This improves performance of Windows Server 2008 guests under heavy loads. (BZ#488130)
qemu-kvm command are now compiled out of the kvm pacakges. (BZ#516672)
fsync to fdatasync. This allows write caches to be exposed to guests and allows the guest to request for flushing I/O buffers. This improves I/O performance for some guests. (BZ#537646)
libvirt packages that fix several bugs and introduce feature enhancements are now available for Red Hat Enterprise Linux 5.
libvirt would not attempt to reset the PCI bus if other functions or devices were present on the same bus. Some PCI devices could not utilized for virtualization as a result. Attempts to reset the PCI bus will now be made, allowing affected devices to be used for virtualization.
virsh edit command to change the name of a Xen domain would make a new copy of the configuration file with the new name, but not alter the original configuration file. UUIDs and names for guest domains are now checked to ensure they match. Attempting to change the name of a domain using the virsh edit command will now return an error message and not make any change to the system.
0-65534. A value of 65535 was being accepted as valid, but would not alter the scheduler configuration. With this release, only values within the valid range are accepted.
info command to change memory values on a KVM guest showed that inactive KVM guest memory was not being reported correctly. Memory reporting for unused domains was corrected in the qemu driver and the info command now returns the correct value.
virsh vol-key volname was sometimes resulting in a segmentation fault. A change was made to the way pool objects are handled and the key lookup no longer crashes.
virsh vol-path command would result in errors. The virsh vol-path command was altered to support the pool parameter and the errors no longer occur.
virsh find-storage-pool-sources command failed to find any dir/nfs/netfs pool sources and failed with unknown failure. The error reporting was fixed and the command now works as expected.
virsh nodedev-create command resulted in an out of memory error. This was found to be a false positive. The checks were updated, and the error now only occurs if there is an actual memory problem.
libvirt entry points, which created a device error when creating nodes. One of the methods was renamed and node creation now works as expected.
virsh nodedev-destroy command to destroy a NIC interface caused libvirtd to hang indefinitely. The locking issue was found and rectified and the libvirtd crash no longer occurs.
virsh vol-delete command produced a failed to connect to the hypervisor error and libvirtd needed to be restarted. The code was altered to refresh allocation and permissions information, but not capacity information, and the command now works as expected.
virsh dumpxml for a running virtual machine, it contained parameters used for backwards compatibility with previous versions. virt-xml-validate would report that the generated file was not valid because of these legacy parameters. The validate program was altered to accept the parameters used in the generated XML file, which now validates correctly.
libvirt python wrapper caused libvirt to crash. Changes were made to the way that GNUTLS handles threading and the crash no longer occurs.
libvirt was not reporting current vCPU and pCPU placement or the vCPU execution time counter accurately. The behavior was changed so that libvirt doesn't find out the affinity when set with taskset, but does when set with virsh vcpupin. The reporting is now correct.
/var/log/messages file. The Opened WWN path /sys/class/fc_host//host5/port_name for reading message was updated and the error messages no longer appear in the log file.
virsh man page described “most operations” as being asynchronous, which is not the case. The man page was updated to state that most operations are synchronous except creation and shutdown of domains.
--no-kvm-pit-reinjection to the qemu command line, and the guest no longer falls out of synchronization.
libvirt would not perform a power management reset if there were other functions on the device. The PCI Power Management reset only affects individual functions, and not the whole device. The check for other functions was removed, so that where both are available, the whole device reset is preferred over individual function resets.
qemu-kvm was changed so that it no longer 'forgets' the virtual machine is paused, and it will now stay paused during a migration.
libvirt was ordering disks unecessarily. When a new disk was added, it would sometimes shift the boot disk later in the list, causing the user to be unable to boot. The sorting algorithm was changed, and will now insert a new disk as far to the end of the list as possible, while being ordered correctly with other disks on the same bus. This resolved booting errors caused by disk ordering.
libvirtd to suffer a segmentation fault. A check was added, and a typing mistake will now cause libvirtd to fail gracefully and produce a meaningful error report.
libvirt now successfully blocks devices between non-ACS switches, unless the user specifies the permissive='yes' attribute for <hostdev>, so all transactions now undergo validation by default.
xen+ssh:// to connect to a host, sometimes an RPC entry point would not be available and dominfo would raise an uninformative error: unknown procedure error. The error reporting was changed and it now reports as an unsupported entry point.
virt-manager tried to attach a PCI device to a Xen guest, it called virNodeDeviceReset and subsequently crashed. The Xen driver was updated, and it now checks if a given PCI device is assigned to another guest, so that PCI devices can be attached as expected.
libvirtd process was occasionally unable to connect to the hypervisor. In this case, qemu-kvm failed to start, and gave a false NUMA out of memory error. The error handling was changed so that NUMA errors are now non-fatal. Errors are now logged, and connection progresses as expected.
libvirt was found to be incorrectly detecting machine types supported by KVM. This meant that KVM guests which did not specify any machine type could not be created. This also caused some rare problems that would cause /distribution/virt/install to fail. libvirt was updated to correctly detect and identify KVM-supported machine types.
qemu guests.
virsh dump command for QEMU/KVM guests is included in this release.
libvirt for KVM PCI device assignment hotplug.
-mem-prealloc to the KVM command line when using hugepage.
libvirt now allows the creation of more than 256 guests, and more than 150 DHCP leases.
-M rhel5.4 arguments are now passed by default when launching qemu-kvm. This improves backward migration ability.
libvirt are advised to upgrade to these updated packages, which resolve these issues and add these enhancements.
mkinitrd utility creates file system images for use as initial ramdisk (initrd) images.
multipath.conf has the correct stanzas for both multipath devices.
mkinitrd again.
multipath.conf in the initrd does not blacklist the new LUN and;
/var/lib/multipath/bindings in the initrd is either empty or contains an entry binding mpath0 (or the device originally installed to) to the replicated LUN's WWID.
scsi_model devflag options appended to /etc/modprobe.conf can be of the form: “options scsi_mod dev_flags="HITACHI:OPEN-9 -SUN:0x240” to specify more than one SCSI model. These strings are written as arguments to the insmod command within the initrd script. The leading spaces of the second model name in the above example were incorrectly read as a single space by the nash command resulting in the /proc/scsi/device_info file containing invalid strings. A user specifying a SCSI model in this way would have to manually edit the /proc/scsi/device_info file as a result. A patch has been applied to nash.c to correctly handle the quoted string following the dev_flag argument. The string is now written to the /proc/scsi/device_info file in the correct format. (BZ#467850)
mkinitrd uses a global variable rootdev to store the name of the root device. This is either auto-detected or passed in via the command line --rootdev= parameter. Changes applied to mkinitrd to support boot from multipath introduced the local rootdev variable. This variable overrides the global variable resulting in an incorrect root device, such as a component SCSI device, being written to the /init script preventing the system from booting. The local variable has been renamed to avoid the conflict. Running mkinitrd on a multipath boot system now results in a successful boot of the system. (BZ#503567)
mkinitrd runs nash on each logical volume. The block_find_fs_by_key() method calls the nashDmGetDevName() method for each logical volume. The nash command does not run to completion in a reasonable time-frame as the nashDmGetDevName() recurses through all devices each time it is called. This update allows nashDmGetDevName() to cache its results, so nash no longer uses 100% of the CPU when installing RPMs. (BZ#516047)
mkinitrd copied the lvm.conf file verbatim to the initrd without parsing it properly. If the logical volume manager (LVM) was configured to use host tags, Red Hat Enterprise Linux would not boot because a host name could not be set at initrd time. lvm --dumpconfig is now used to retrieve the LVM configuration file. (BZ#517868)
mkinitrd attempted to explicitly activate the subsets of a nested RAID 10 set. Error messages would then be printed to the log during boot. These messages could safely be ignored. They have now been removed to avoid confusion. (BZ#526246)
mkinitrd copied the symbolic link of a bootpath driver instead of the actual bootpath driver. This caused kernel panic due to an unavailable driver on first boot of the operating system. mkinitrd now checks the full path of symbolically linked drivers. (BZ#540641)
nash received a segmentation fault reference if some modules did not load during post-installation reboot. This caused unwarranted kernel panic. Kernel panic no longer occurs as a result of the non-loading of modules. (BZ#560567)
mkinitrd. This meant that mkinitrd built incorrectly upon installation if virtio block or network devices were used within the Kernel Based Virtual Machine (KVM). The final result was kernel panic. These updated packages contain the required modules which allow mkinitrd to build and install correctly. (BZ#560672)
scsi_dh_rdac module is needed to support many LSI Engenio based (IBM and non-IBM) storage devices. With the inclusion of a module such as the scsi_dh_rdac module in initrd, the time to boot a system with multiple rdac devices is minimized. A patch has been applied to mkinitrd to load every scsi_dh_* module in the event that multipath devices are detected. The patch currently succeeds in loading xscsi_dh_rdac modules for installations on DS4K storage and further work is being undertaken to ensure the successful loading of modules independent of the host device. (BZ#460899)
mkinitrd is responsible for ensuring that all drivers, applications, and configuration information needed to mount the root filesystem are packaged into each kernel's initrd. Unlike the Logical Volume Manager (LVM) component of mkinitrd, multipath operates on only the logical volume associated with the root filesystem and not the volume group containing the root filesystem. As a consequence, when installing a system with multipath devices, only disks currently in use by the root's logical volume have multipath configured within the initrd. A patch has been applied that wraps the find_mpath_deps in a loop that iterates through every primary volume in the root volume group. Non-LVMs are handled in a separate case by runnning find_mpath_deps against the root device. Installing a system with multipath devices will now result in the primary volumes in the root virtual group being on multipath devices. (BZ#501535)
.odt file in Firefox would generate a segmentation fault, causing Firefox to crash on x86_64 architectures. A patch has been applied to define the uint32 and int32 variables as the appropriate type of int or long depending on the architecture. (BZ#496033)
.sxi or .odt file into an OpenOffice.org Calc document, the application would crash due to the SfxMedium* pMed pointer in ScDocShell::DialogClosedHdl() being set to NULL. A patch has been applied to the docsh4.cxx file to test the state of this variable prior to affecting the merge. (BZ#504551)
viewfunc.cxx file has been updated to ensure that the insert operation is functional even if the original cell contents are misspelt. (BZ#504967)
cell.hxx file has been modified to simplify a list range (for example: the list A2;A1;A3 would become A1:A3). By condensing the list, the → → command now works as expected. (BZ#504971)
RPMs for OpenOffice.org would fail when a Java version above version 1.4 was installed. This occurred because the ANT scripts used to build some of the components were not configured to generate version 1.4 compatible bytecode upon which OpenOffice.org is dependent. This bug has since been fixed by enforcing RPMs to be built with the GNU Compiler for Java (GCJ) or the Eclipse Compiler for Java (EJC). GJC specific options have been omitted as these are not recognized by EJC. This ensures that OpenOffice.org RPMs are generated without error when using the rpmbuild command. (BZ#506036)
None as the first value for each newly inserted key. Under these circumstances the second insertion returns a NULL pointer and the following statement causes the crash by dereferencing the pointer. To correct this bug the jobset.cxx file has been modified to only insert a value of None as the first value for each newly inserted key if it is not already present. (BZ#515488)
Open XML (OOXML) file formats resulting in the inability to open files of this type. The OpenOffice.org 3.1.1-19.5 suite provides the necessary support to open OOXML file formats including pptx, xlsx and docx. (BZ#444052)
selinux-policy packages that fix numerous bugs are now available.
coolkey library used by some Kerberos implementations caused an SELinux denial when credentials were sent to an NFS server, and during the creation of a cache directory. This package modifies SELinux policy so that the coolkey Kerberos library is excluded from being audited when performing this operation. (BZ#294651)
cupsd caused an SELinux error or denial. SELinux policy has been modified to allow this activity and not to cause a denial when this activity takes place. (BZ#483395)
/root/.ssh directory contained incorrect SELinux permissions if it was deleted and re-created. This permission error caused the ssh-keygen command to fail when creating keys in this directory from an init script, as it was not labelled correctly. SELinux policy has been modified to enable the correct permissions on the /root/.ssh directory if it is removed and re-added. Having the correct permission on this directory results in ssh-keygen now being able to successfully generate keys as expected. (BZ#492519)
service cman start because aisexec could not allocate shared memory. Support has been added in SELinux policy for Cluster Suite, which resolves these issues. (BZ#503141)
coolkey command integrated with samba to join an Active Directory service. SELinux policy has been modified to allow for proper coolkey cache management in the samba policy module. (BZ#507797)
rsync command when it is used via the SSH protocol. (BZ#510748)
sqlplus command caused an SELinux denial. Policy has been modified to label this file correctly to allow for its unexpected behavior. The sqlplus command functions normally after applying this update. (BZ#512375)
sysadm SELinux role can now use the setkey utility from the ipsec-tools package. (BZ#513447)
vbetool the permissions it needs to operate normally. (BZ#515491)
setkey was executed from a network startup script, an SELinux denial was triggered. An interface has been added to enable integration with temporary files when using setkey within the MLS SELinux policy. (BZ#515687)
rsync command has changed. rsync is now protected only when started from inetd or xinetd. Other usages of rsync are considered client-side operations and are not protected any further than that of utilities such as cp or scp. (BZ#516780)
sudo command was not properly launching an intermediary shell to authenticate users with correct sudo role privileges. This fix allows transitions to operate normally and allows users to execute commands as root via sudo, when configured to do so. (BZ#519017)
ipsec connection by using the service network restart command did not succeed. The ipsec connection did not start as it was started from the init_t domain. Policy for setkey has been modified so that it can now read temporary data from init scripts, and ipsec connections now start normally from the init_t domain. (BZ#519363)
mod_fcgid, a CGI plugin for the Apache HTTP server caused SELinux permission errors when used. Policy has been modified to both allow mod_fcgid scripts the required permissions, and to allow CGI applications to use their own mail modules to send mail, instead of calling sendmail. (BZ#519369)
#!/usr/bin/env python have been removed from SELinux policy source code, as using this technique to call python in the top of an executable python file is being discontinued by Red Hat developers. (BZ#521284)
cyrus-imapd is now able to register its SNMP sub-agent by connecting to a socket upon startup. (BZ#523548)
SNMP daemon to listen on TCP or UDP ports for AgentX sub-agents. Policy has been modified so that this daemon can now bind TCP/UDP sockets to AgentX ports. (BZ#523773)
NFS (Network File System) shares. Policy has been modified to properly allow for the normal operation of quotas when using NFS shares. (BZ#525420)
udev daemon to the latest version and restarting it, the SELinux context for udev was changed from the default, causing errors. This update ensures that this context remains correct when restarting udev. (BZ#526640)
qemu-kvm. (BZ#530552)
procmail was causing an AVC denial when attempting to read files used by spamassassin. Rules have been added to policy so that these applications can communicate normally via pipes. (BZ#530750)
aisexec were not properly met. The strict policy can now be installed as expected. (BZ#531196)
e4fsck command was not properly labeled, causing execution to fail. Policy permissions have been fixed so that e4fsck is now correctly labeled. (BZ#532565)
pluto to write logs properly. (BZ#537106)
IPsec, fixing the AVC denials that prevented pluto from running properly. After applying this update, pluto runs as expected. Note that this is necessary for FIPS-140 security compliance. (BZ#537133)
vhostmd is a daemon that provides a communication channel between a host and its hosted virtual machines. Implementing a vhostmd daemon caused AVC denial errors when launching it via service vhostmd start. SELinux policy rules have been added to protect the vhostmd daemon. The daemon starts and operates normally after applying the update. (BZ#543941)
racoon using a UNIX domain stream socket. After applying this update, access functions as expected. (BZ#545369)
iptables can now start properly and has proper permissions to read configuration files. (BZ#546604)
smartd daemon the ability to read from and write to generic SCSI devices. (BZ#547387)
bnx2i interface type. (BZ#548599)
/var/vdsm directory was incorrectly labeled by SELinux, showing two different SELinux contexts. After applying this update, the directory is now correctly labeled with a single label. (BZ#549492)
lpadmin command to set an interface script for a printer, SELinux error messages are triggered. A new type, cupsd_interface_t, has been added to policy to allow cupsd to properly utilize a System V style interface script. (BZ#550015)
postgresql regression tests include libraries that need to be dynamically loaded by the postgresql server. Some of these libraries were incorrectly labeled, which caused the regression tests to fail and SELinux errors to appear. This update applies the correct permissions to the libraries, and the postgresql regression tests now operate as expected. (BZ#551063)
prelink is a utility that can reduce the startup times of applications by linking to libraries and storing the linking in the executable. prelink is now allowed under SELinux policy to load and execute functions from shared libraries, with legacy support included for older libraries. (BZ#551664)
qemu-kvm caused SELinux errors when creating or starting a virtual machine when Transport Layer Security (TLS) is enabled in qemu.conf for an environment using a Public Key Infrastructure (PKI). This error occurred because qemu-kvm did not have sufficient permission to read from a random number generator (/dev/random and /dev/urandom) in order to gather its entropy. Permissions have been modified so that qemu-kvm can now read from these random number generators. (BZ#552763)
postfix_postdrop command was unable to use sockets. This resulted in emails not being sent. After applying this update, postfix is able to read and write sendmail unix_stream_sockets and emails can be sent using sendmail as expected. (BZ#553492)
/etc/xen was incorrectly labeled. This caused errors when using automated scripts for staging Xen guest virtual machines. A fix was applied to correctly label the directory, which resolved the problem. Xen guests are now functioning as expected. (BZ#554777)
service network restart command resulted in an AVC denial caused by dhcpc_t being unable to relabel to and from net_conf_t. This update allows this with the result that restarting networking succeeds without SELinux denials. (BZ#559355)
iscsid daemon, which implements the control path of the iSCSI protocol along with management functions, could not create its log file due to an incorrect SELinux context. (BZ#562303)
named name server daemon, when running in a chrooted environment, was incorrect, and with this update is labeled correctly. (BZ#562833)
service iptables save command triggered an AVC denial. This update changes the default context for the /sbin/iptables-save application to iptabels_exec_t so that the firewall configuration can be saved. (BZ#564376)
cgi-bin directory mounted on an NFS share resulted in an AVC denial, whereas serving static pages from a public_html directory worked as expected. CGI scripts can now be run from NFS-mounted directories given the correct permissions. (BZ#566557)
kmod-gfs2 was installed on a Red Hat Enterprise Linux 5 system, it was possible to have a situation whereby its version of gfs2.ko would take precedence over that supplied with the kernel. As a consequence, the wrong version of the Global File System would be used and it also would be incorrectly set to weak-update. SOS has now been modified to warn system administrators if gfs2.ko has been set to use weak updates and instructs them there is a need to remove kmod-gfs2 and reboot the system before proceeding any further. (BZ#507390)
groupd can erroneously assign the fence domain id 00000000. This can result in LVM commands becoming permanently locked. To alert system administrators to this issue, a check has been added to SOS that examines the output of group_tool -v for a string of zeroes against fence and, if it finds this to be the case, it generates a warning message that instructs administrators on how to remedy the problem. (BZ#499468)
/tmp. (This problem did not occur if absolute link entries were used.) A change has been made so that SOS no longer traverses directories relative to the current working directory. As a result, this potentially large amount of data is no longer copied erroneously. (BZ#530385)
group_tool -v to detect if CMAN services are set to anything other than none. A warning is then produced to prompt the system administrator to investigate the cause of the potential problem. (BZ#499472)
sosreport command was run from a terminal, the percentage completed figure would go up and down. Furthermore, after it has reached 100%, the real time and estimated finish time would continue to grow together for several more seconds. A new, more reliable progress indication system has been added. As a result, the progress indication will be reliable from now on. (BZ#502442)
cluster.py file which was only searching the services tag and not the resources tag, in which fsid is set (as part of best practice) if the file system is a share resource. cluster.py has now been patched to account for all scenarios so false reports of missing fsids will no longer be generated. (BZ#507674)
sosreport -k general.syslogsize=15 command did not limit log file sizes to 15 Mb, contrary to expected behavior. This was because the limits were being erroneously applied to /var/log/messages.* instead of /var/log/messages. As a result, huge reports were generated and sosreport could even potentially die if all space in /tmp was used by the process. To fix this problem, the limits are now being applied to /var/log/messages meaning the huge reports are no longer being generated. (BZ#516551)
name-[epoch:]version-release.arch, it was in the form of name-version-release-arch. This was inconvenient to users wishing to paste output to programs such as yum. To fix this issue, changes have been made to ensure that the list of installed RPMs is now in the name-[epoch:]version-release.arch format to make it usable with yum and rpm commands. (BZ#482755)
sosreport deliberately obscured fencing passwords in /etc/cluster/cluster.conf. It would break the XML formatting by removing the quotation marks that surrounded the masked version of the password. A further problem was that the passwords in backup files (such as /etc/cluster/cluster.conf.1) were not obscured. To resolve this issue, changes have been made to password masking to ensure the XML remains well-formed and the process is applied to any back-up configuration files that may exist. As a result, security is enhanced and files no longer need manual rectification before tests can be run on cluster.conf. (BZ#497588)
/tftpboot directory, which resulted in huge files (potentially greater than 1 GB), if multiple boot media had been created in that location. To address this issue the contents of /tftpboot are now excluded from the report. (BZ#523263)
sar plugin included in SOS ignored the locale setting and created sar files with time data presented in the default format. With this update, the plugin now honors the locale setting and generates sar files with time data in the expected format (ie the same format as sar files created by sysstat cron jobs). (BZ#525010)
/var/log/cron*
partedhard disk deviceprint
tune2fs -lfilesystem
/etc/inittab
serviceservice namestatus
/etc/inittab
/etc/kdump.conf
/sbin/mdadm -D /dev/md*
/etc/lvm
/proc/buddyinfo
dmraid -V
dmraid -b
dmraid -r
dmraid -s
dmraid -tay
dmraid -rD
/etc/cobbler
/var/log/cobbler
/var/lib/rhn/kickstarts
/var/lib/cobbler/snippits
/var/lib/cobbler/config
/var/lib/cobbler/kickstarts
/var/lib/cobbler/triggers
/etc/iscsi/iscsid.conf
/etc/iscsi/initiatorname.iscsi
/var/lib/iscsi/
netstat -agn
ip mroute show
ip maddr show
systemtap-testsuite package contained test cases that were incorrectly not configured as 'executable' (systemtap.base/bz10078.stp, buildko/two.stp, and buildok/thirty.stp). Any test runs involving these cases failed unexpectedly. This release fixes the permissions for all test cases; it also fixes minor test case issues relating to an incorrect header file reference in systemtap.base/sdt.exp, an incorrect execution sequence in systemtap.base/labels.exp, and an incorrect reference to a missing script in systemtap.base/crash.exp. (BZ#506959, BZ#559643, and BZ#513654)
man pages of stap-server and stap-client. (BZ#516691)
task_pid() function in a SystemTap script while the kernel-debuginfo package was not installed could incorrectly result in a semantic error. This update applies an upstream patch to the task.stp tapset, which fixes the issue. (BZ#519314)
memory/mmanonpage.stp
memory/mmfilepage.stp
memory/mmreclaim.stp
memory/mmwriteback.stp
network/dropwatch.stp
process/schedtimes.stp
staprun processes could result in a kernel panic. This was because runtime/procfs.c only checked if /proc/systemtap was being used before deleting it, resulting in a race condition that made it possible for /proc/systemtap to be deleted while a module was still loaded inside. This update fixes the race condition by adding instructions to lock the transport directory and check for files under /proc/systemtap before deleting it. (BZ#510282)
tcpmib.stp and ipmib.stp tapsets have been updated to provide per-socket network statistics and dynamic TCP connection tracing. (BZ#512202)
SIGKILL on the stap process will not terminate its child process, stapio. As such, users may not be aware that a SystemTap module is still probing the system, which will result in performance degradation. This update adds a note in man stap warning users of this behavior. (BZ#523356)
stap. This could cause problems in third-party tools that use SystemTap to probe kernel functions. This update reverts the order of parameters to its original sequence, which is also consistent with their order in the kernel source code. (BZ#560890)
sys32_pipe function was removed in updated kernels, but the system call tapsets for the x86_64 kernel still contained an alias that used this function. As a result, using the probe syscall.* resulted in a semantic error. With this release, the system call tapsets for the x86_64 kernel make the syscall.pipe probe alias (which uses sys32_pipe) optional, thereby avoiding the error. (BZ#563114)
literal_addr_to_sym_addr() function did not correctly compute for marker addresses. As such, markers became inaccessible after running prelink; this prevented scripts that used markers from compiling. This release fixes the literal_addr_to_sym_addr(), ensuring that marker addresses are accessible after running prelink. (BZ#564445)
loc2c.c) was not updated accordingly to understand this new format. This could prevent some variables from initializing properly. With this release, the loc2c.c file is updated to correctly process the new format used by GCC for variable locations. (BZ#536807)
xen packages contain tools for managing the virtual machine monitor in Red Hat Enterprise Linux Virtualization.
ata2.00: configured for MWDMA2
ata2: EH complete
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
cdb 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
res 41/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x3 (HSM violation)
ata2.00: status: { DRDY ERR }
ata2: soft resetting linkata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.00: BMDMA stat 0x5
ata2.00: cmd a0/01:00:00:80:00/00:00:00:00:00/a0 tag 0 dma 16512 in
ata2.00: status: { DRDY DRQ }
ata2: soft resetting link
ata2.00: configured for MWDMA2
ata2: EH completeError: Can't shutdown/save the domain since the domain is paused; unpaused it first if you want to shutdown/save
xm info command could not be fully allocated to the guest. When attempting create a fully virtualized guest with more than or equal to the maximum available memory value, the following error message would appear:
Error: (1, 'Internal error', 'Could not allocate memory for HVM guest.\n (16 = Device or resource busy)')
xend daemon and the hotplug scripts caused a recently rebooted guest to disappear from the xm list command output. The race condition is fixed and guests will now always appear in the xm list command output after the guest is rebooted. (BZ#513604)
xm pci-list command would fail due to an unhandled error in the output parsing functions for para-virtualized guests. The output is now handled correctly by the xm pci-list command which resolves this issue in the updated packages. (BZ#514025)
xm pci-list-assignable-devices command was executed. The pciback kernel module must be loaded before executing the xm pci-list-assignable-devices command. The updated package provides an error that informs the user the module is not loaded. (BZ#514448)
rename-restart for the on_reboot parameter caused guests to not start when the guest was rebooted. Using rename-restart now causes guests to start successfully after a reboot with a different name. (BZ#521799)
libxc and the libxenstore python binding libraries caused increasing memory usage over time. The memory leaks in the libxc and the libxenstore libraries are fixed in the updated package and the libraries memory usage should remain steady. (BZ#524308)
xm dump-core command could not dump memory while a guest is running. The memory dump functionality has been improved, however, there are still issues with generating live dumps. The guest core dump image may be in an inconsistent state if the guest is under load. Users are now warned about this issue. (BZ#382591)
xendomains service now has less confusing and better formatted output. (BZ#251666)
maxvcpus parameter for Xen configuration files. The maxvcpus parameter sets a maximum number of VCPUs available that is separate from the initial VCPUs assigned to the guest. (BZ#453042)
bfa driver for Brocade Fibre Channel Host Bus adapters has been added to Red Hat Enterprise Linux 5.5 as a Technology Preview. BZ#475695
ext4, is available in this release as a Technology Preview. Ext4 is an incremental improvement on the ext3 file system developed by Red Hat and the Linux community. The release name of the file system for the Technology Preview is ext4dev.
ext4dev.ko kernel module, and a new e4fsprogs package, which contains updated versions of the familiar e2fsprogs administrative tools for use with ext4. To use, install e4fsprogs and then use commands like mkfs.ext4dev from the e4fsprogs program to create an ext4-base file system. When referring to the filesystem on a mount commandline or fstab file, use the filesystem name ext4dev.
tpm-tools are included in this release to enable use of Trusted Platform Module (TPM) hardware.TPM hardware features include (among others):
tpm-tools is a suite of tools used to manage and utilize TPM hardware.
ecryptfs-mount-helper-gui).
/etc/fstab entries. For information about these changes, refer to man ecryptfs.
mount -t ecryptfs /mnt/secret /mnt/secret
ecryptfs-utils-56-4.el5 or newer.
/etc/sysconfig/readonly-root for more details).
firewire-sbp2 module is still included in this update as a Technology Preview. This module enables connectivity with FireWire storage devices and scanners.
SBP2 driver may cause the machine to become unresponsive.
ktune (from the ktune package), a service that sets several kernel tuning parameters to values suitable for specific system profiles. Currently, ktune only provides a profile for large-memory systems running disk-intensive and network-intensive applications.
ktune do not override those set in /etc/sysctl.conf or through the kernel command line. ktune may not be suitable on some systems and workloads; as such, you should test it comprehensively before deploying to production.
ktune and revert to your normall settings by simply stopping the ktune service using service ktune stop (as root).
gcc44 packages, the default for the gnu89-inline option has been changed to -fgnu89-inline, whereas upstream and future updates of Red Hat Enterprise Linux 5 will default to -fno-gnu89-inline. This is necessary because many headers shipped as part of Red Hat Enterprise Linux 5 expect GNU in-line semantics instead of ISO C99 semantics. These headers have not been adjusted to request GNU in-line semantics through attributes.
/sys/module/fcoe/parameters/create file, for example:
echo eth6 > /sys/module/fcoe/parameters/createTo logout, write the network interface name to the
/sys/module/fcoe/parameters/destroy file, for example:
echo eth6 > /sys/module/fcoe/parameters/destroyFor further information on software based FCoE refer to: http://www.open-fcoe.org/openfc/wiki/index.php/FCoE_Initiator_Quickstart.
fnic driver, the Emulex lpfc driver, and the Qlogic qla2xx driver.
scsi-target-utils package as a Technology Preview. In this release, single portal and multiple portals on different subnets are supported. There are known bugs when using multiple portals on the same subnet.
cxgb3 driver the libcxgb3 package is needed, and for host channel adapters using the mthca driver the libmthca package is needed.
scsi-target-utils package as a Technology Preview. In this release, single portal and multiple portals on different subnets are supported. There are known bugs when using multiple portals on the same subnet.
cxgb3 driver the libcxgb3 package is needed, and for host channel adapters using the mthca driver the libmthca package is needed.
| Certified | |
|---|---|
| x86 | 32 |
| Itanium2 | 256 |
| AMD64/Intel64 | 64 |
| Power | 128 |
| System z | 64 (z10 EC) |
| Certified | |
|---|---|
| x86 | 16GB |
| Itanium2 | 2TB |
| AMD64/Intel64 | 256GB |
| Power | 512GB |
| System z | 1.5TB (z10 EC) |
clearpart --initlabel [disks]BZ#530465
$TARGET_IP: IP address of the iscsi target (drive) $TARGET_IQN: name of the iscsi target as printed by the discovery command $ROOT_DEV: devicenode (/dev/.....) where your root fs lives
$ mkdir /etc/iscsi $ cat << EOF>> /etc/iscsi/initiatorname.iscsi InitiatorName=iqn.1994-05.com.fedora:d62f2d7c09f EOF
$ iscsid
$ iscsiadm -m discovery -t st -p $TARGET_IP $ iscsiadm -m node -T $TARGET_IQN -p $TARGET_IP --login
$ lvm vgscan $ lvm vgchange -ay
$ mount /dev/path/to/root /mnt/sysimage $ mount -t bind /dev /mnt/sysimage/dev $ mount -t proc proc /mnt/sysimage/proc $ mount -t sysfs sysfs /mnt/sysimage/sys
$ chroot /mnt/sysimage /bin/su -
resolution=1024x768 or resolution=1280x1024" to the installer using the boot command line.
mount -o nolock,udp command to start the locking daemon before using nfs to mount shares. (BZ#426053)
dom0.
rhn-virtualization-common package manually before attempting to register the system to Red Hat Network. (BZ#431648)
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.
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.
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. (BZ#467202)
# -R <region_size_in_MiB> lvcreate -m1 -L 2T -R 2 -n mirror vol_groupFailure to increase the region size will result in the LVM creation process hanging and may cause other LVM commands to hang. (BZ#514814)
rpmbuild on the compiz source RPM will fail if any KDE or qt development packages (for example, qt-devel) are installed. This is caused by a bug in the compiz configuration script.
qt development packages before attempting to build the compiz package from its source RPM. (BZ#444609)
dm-multipath, if features "1 queue_if_no_path" is specified in /etc/multipath.conf then any process that issues I/O will hang until one or more paths are restored.
no_path_retry [N] in /etc/multipath.conf (where [N]features "1 queue_if_no_path" option from /etc/multipath.conf as well.
"1 queue_if_no_path" and experience the issue noted here, use dmsetup to edit the policy at runtime for a particular LUN (i.e. for which all the paths are unavailable).
dmsetup message [device] 0 "fail_if_no_path", where [device]mpath2; do not specify the path) for which you want to change the policy from "queue_if_no_path" to "fail_if_no_path". (BZ#419581)
lvm commands will hang indefinitely when dm-multipath is used, as the LUN has now become stale.
mpath link entries in /etc/lvm/.cache specific to the stale LUN.
ls -l /dev/mpath | grep [stale LUN]
[stale LUN]lrwxrwxrwx 1 root root 7 Aug 2 10:33 /3600d0230003414f30000203a7bc41a00 -> ../dm-4 lrwxrwxrwx 1 root root 7 Aug 2 10:33 /3600d0230003414f30000203a7bc41a00p1 -> ../dm-5
mpath links: dm-4 and dm-5.
/etc/lvm/.cache:
/dev/dm-4 /dev/dm-5 /dev/mapper/3600d0230003414f30000203a7bc41a00 /dev/mapper/3600d0230003414f30000203a7bc41a00p1 /dev/mpath/3600d0230003414f30000203a7bc41a00 /dev/mpath/3600d0230003414f30000203a7bc41a00p1
multipath command with the -ll option can cause the command to hang if one of the paths is on a blocking device. Note that the driver does not fail a request after some time if the device does not respond.
multipath state without hanging the command, use multipath -l instead. (BZ#214838)
/etc/cron.d/dmeventd-logwatch crontab file does not specify the user that the logwatch process should be executed by. To work around this issue, the functional portion of this crontab must be changed to:
* * * * * root /usr/sbin/logwatch --service dmeventd --range today --detail med(BZ#516892)
dmraid -ay isw_effjffhbi_Volume0
mkdir /tmp/raid mount /dev/mapper/isw_effjffhbi_Volume0p1 /tmp/raid
mkdir /tmp/raid/tmp/image cd /tmp/raid/tmp/image gzip -cd /tmp/raid/boot/inird-2.6.18-155.el5.img | cpio -imd –quiet
dmraid –ay –I –p –rm_partition “/dev/mapper/isw_effjffhbi_Volume0” kpartx –a –p p “/dev/mapper/isw_effjffhbi_Volume0” mkrtootdev –t ext3 –o defaults,ro /dev/mapper/isw_effjffhbi_Volume0p1
cd /tmp/raid/tmp/image find . –print | cpio –c –o | gzip -9 > /tmp/raid/boot/inird-2.6.18-155.el5.img
umount /dev/mapper/isw_effjffhbi_Volume0p1 dmraid -an
sniff may result in an error. This is because some required packages are not installed with dogtail. (BZ#435702)
/usr/bin/setup — provided by the setuptool package.
/usr/bin/rhn_register — provided by the rhn-setup package.
fsck.gfs2: invalid option -- a". To work around this issue:
mount -o remount,rw /dev/VolGroup00/LogVol00 /
/dev/VolGroup00/LogVol00 / gfs2 defaults 1 1to
/dev/VolGroup00/LogVol00 / gfs2 defaults 1 0
/media:
mount /dev/[device name] /media/var/log/boot.log is not available in Red Hat Enterprise Linux 5.3. (BZ#223446, BZ#210136)
iscsiadm -m node -T target -p ip -I default -u(BZ#500273)
kernel /xen.gz edd=off(BZ#568336)
(XEN) [VT-D]intremap.c:73: remap_entry_to_ioapic_rte: index (74) is larger than remap table entry size (55)!To work around this issue, disable the interrupt remapping feature in the BIOS and reboot the system. (BZ#563546)
kernel unaligned access to 0xe0000034f327f0ff, ip=0xa0000002040c4870 kernel unaligned access to 0xe0000034f327cbff, ip=0xa0000002040c4870 kernel unaligned access to 0xe00000300c9581ff, ip=0xa0000002040c4870These messages do not indicate a serious error. The data alignment issue will be fixed in a future release. BZ#570000
nogbpages" parameter on the guest kernel command-line. (BZ#502826)
title Red Hat Enterprise Linux Server (2.6.18-152.el5xen)
root (hd0,1)
kernel /xen.gz-2.6.18-152.el5 com1=115200,8n1 console=com1 iommu=1
module /vmlinuz-2.6.18-152.el5xen ro root=LABEL=/ console=ttyS0,115200
pci_pt_e820_access=on
This enables the MMCONF access method for the PCI configuration space, a requirement for VF device support
testing NMI watchdog ... <4> WARNING: CPU#0: NMI appears to be stuck (0->0)!This issue is caused by an implementation issue with the Xen hypervisor and can be safely ignored. (BZ#500845)
dom0) system to Red Hat Enterprise Linux 5.2 may render existing Red Hat Enterprise Linux 4.5 SMP paravirtualized guests unbootable. This is more likely to occur when the host system has more than 4GB of RAM.
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.
console=tty to the kernel boot options in /boot/efi/elilo.conf. (BZ#249076)
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:
io_base address
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"
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. (BZ#433771)
sky2 eth<N>: receiver hang detectedCurrently, the only work around to make the device online again is to reboot the system. This bug will be repaired in an upcoming update to Red Hat Enterprise Linux 5.4. (BZ#509891, BZ#517976)
ramdisk=/boot/initrd-2.6.18-<kernel-version-number>.el5.img
to
ramdisk=/boot/initrd-2.6.18-<kernel-version-number>.el5.img,0x02000000
The command zipl -V should now show 0x02000000 as the starting address for the inital RAM disk (initrd). Stop the logigal partiton (LPAR), and then manually increase the the storage size of the LPAR.
bnx2i.ko and cnic.ko) is loaded. To work around this do not manually load the bnx2i or cnic modules, and temporarily disable the iscsi service from starting. To disable the iscsi service, run
chkconfig --del iscsi chkconfig --del iscsidOn the first boot of your system, the
iscsi service may start automatically. To bypass this, during bootup, enter interactive start up and stop the iscsi service from starting.
# rmmod kvm_intel # echo 0 > /sys/devices/system/cpu/cpu6/online # modprobe kvm_intel
Stopping tasks: ====================================================================== stopping tasks timed out after 20 seconds (1 tasks remaining): cciss_scan00 Restarting tasks...<6> Strange, cciss_scan00 not stopped done(BZ#513472)
malloc memory approximately larger than the size of the physical memory on the node on a NUMA system may hang or appear to stall. This issue may occur on a NUMA system where the remote memory distance, as defined in SLIT, is greater than 20 and RAM based filesystem like tmpfs or ramfs is mounted.
sysctl vm.zone_reclaim_mode=0
bnx2 driver.
/etc/modprobe.d/ containing the following line:
options bnx2 disable_msi=1
pci=nomsi. (BZ#432451)
smartctl tool cannot properly read SMART parameters from SATA devices. (BZ#429606)
acpi_sleep=s3_bios. (BZ#439006)
qla3xxx and qla4xxx drivers support ethernet and iSCSI functions individually. Both drivers do not support the use of ethernet and iSCSI functions simultaneously.
ifdown/ifup commands) may hang the device. To avoid this, allow a 10-second interval after an ifup before issuing an ifdown. Also, allow the same 10-second interval after an ifdown before issuing an ifup. This interval allows ample time to stabilize and re-initialize all functions when an ifup is issued. (BZ#276891)
ib_mthca driver reports a catastrophic error on this hardware, it is usually related to an insufficient completion queue depth relative to the number of outstanding work requests generated by the user application.
opensm is running at the time the error occurs, then you need to manually restart it in order to resume proper operation. (BZ#251934)
radeonfb module.
hal-system-power-suspend to /usr/share/hal/scripts/ containing the following lines:
chvt 1 radeontool light off radeontool dac off
restore-after-standby to the same directory as well, containing the following lines:
radeontool dac on radeontool light on chvt 7
edac module is loaded, BIOS memory reporting will not work. This is because the edac module clears the register that the BIOS uses for reporting memory errors.
edac module) by default. If you wish to ensure BIOS memory reporting on your system, you need to manually blacklist the edac modules. To do so, add the following lines to /etc/modprobe.conf:
blacklist edac_mc blacklist i5000_edac blacklist i3000_edac blacklist e752x_edac
/etc/modprobe.conf:
alias wlan0 iwlagn options iwlagn swcrypto50=1 swcrypto=1(where wlan0 is the default interface name of the first Intel WiFi Link device)
Please wait, loading kernel... /pci@8000000f8000000/ide@4,1/disk@0:2,vmlinux-anaconda: No such file or directory boot:To work around this:
setenv real-base 2000000
0> dev /packages/gui obe
kdump on an IBM Bladecenter QS21 or QS22 configured with NFS root will fail. To avoid this, specify an NFS dump target in /etc/kdump.conf. (BZ#368981)
forcedeth based devices may encounter difficulty accessing memory above 4GB during operation in a kdump kernel. To work around this issue, add the following line to the /etc/sysconfig/kdump file:
KDUMP_COMMANDLINE_APPEND="dma_64bit=0"This work around prevents the forcedeth network driver from using high memory resources in the kdump kernel, allowing the network to function properly.
kexec/kdump kernel if X is running and using a driver other than vesa. This problem only exists with ATI Rage XL graphics chipsets.
kexec/kdump kernel. (BZ#221656)
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. (BZ#475487)
kexec purgatory code. This code contains instructions for backing up the first 640k of memory after a crash.
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. (BZ#436426)
kdb5_util create -s' on the secondary and supplying the original master password. (BZ#514741)
virsh edit GUEST
<interface type='network'> ... <model type='e1000' /> </interface>
virsh dumpxml GUEST > /tmp/guest.xml
cp /tmp/guest.xml /tmp/new-guest.xml vi /tmp/new-guest.xml
<interface type='network'> ... <model type='e1000' /> </interface>
virsh define /tmp/new-guest.xml virsh start new-guest
kmod-kvm package do not support kernels prior to version 2.6.18-159.el5. Error messages similar to the following will be returned if attempting to install these modules on older kernels:
FATAL: Error inserting kvm_intel (/lib/modules/2.6.18-155.el5/weak-updates/kmod-kvm/kvm-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg)(BZ#509361)
libgcrypt package. Consequently, if the libgcrypt package installed on a system is earlier than version 1.4.4, the qemu-kvm process may refuse to start, returning a libgcrypt initialization error message. To work around this issue, update libgcrypt to the version provided by Red Hat Enterprise Linux 5.5. (BZ#503118)
kmod-kvm package are loaded automatically at boot time if the kmod-kvm package is installed. To make these KVM modules available after installing the kmod-kvm package the system either needs to be rebooted or the modules can be loaded manually by running the /etc/sysconfig/modules/kvm.modules script. (BZ#501543)
lvchange command is used to change the attributes of a logical volume. Issuing the lvchange command on a volume group that contains a mirror or snapshot may result in messages similar to the following:
Unable to change mirror log LV fail_secondary_mlog directly Unable to change mirror image LV fail_secondary_mimage_0 directly Unable to change mirror image LV fail_secondary_mimage_1 directlyThese messages can be safely ignored. (BZ#232499)
glxgears window (when glxgears is run). Doing so can lock the system.
Device section of /etc/X11/xorg.conf:
Option "Tiling" "0"
insmod: error inserting '/lib/aes_generic.ko': -1 File existsThis message can safely be ignored. (BZ#466296)
install.log:
Installing kernel-2.6.18-158.el5.s390x cp: cannot stat `/sbin/dmraid.static': No such file or directoryThis message can be safely ignored.
perftest will fail if different CPU speeds are detected. As such, you should disable CPU speed scaling before running perftest. (BZ#433659)
mvapich and mvapich2 in Red Hat Enterprise Linux 5 are compiled to support only InfiniBand/iWARP interconnects. Consequently, they will not run over ethernet or other network interconnects. (BZ#466390)
cannot open `/tmp/openmpi-upgrade-version.*' for reading: No such file or directoryThe message is harmless and can be safely ignored. (BZ#463919)
openmpi and lam may prevent you from upgrading these packages. This bug manifests in the following error (when attempting to upgrade openmpi or lam:
error: %preun(openmpi-[version]) scriptlet failed, exit status 2openmpi and lam in order to install their latest versions. To do so, use the following rpm command:
rpm -qa | grep '^openmpi-\|^lam-' | xargs rpm -e --noscripts --allmatches (BZ#433841)
systemtap-testsuite package fail with an Unknown symbol in module error on some architectures. These test cases include (but are not limited to):
systemtap.base/uprobes.exp
systemtap.base/bz10078.exp
systemtap.base/bz6850.exp
systemtap.base/bz5274.exp
uprobes.ko module. Some updated user-space probe tests provided by the systemtap-testsuite package use symbols available only in the latest uprobes.ko module (also provided by the latest SystemTap update). As such, running these user-space probe tests result in the error mentioned earlier.
rmmod uprobes to manually remove the older uprobes.ko module before running the user-space probe test again.(BZ#499677)
i810 driver. You should use the default intel driver instead. (BZ#468218)
EDID information from the monitor. When this occurs, the graphics driver will be unable to display resolutions highers than 800x600.
ServerLayout section of /etc/X11/xorg.conf:
Option "Int10Backend" "x86emu"
FINAL File Size = 8948021 bytes. load-base=0x4000 real-base=0xc00000 DEFAULT CATCH!, exception-handler=fff00300The firmware for IBM Power6 and IBM Power7 systems contains a fix for this issue. (BZ#550086)
dom0, the default network-bridge script may cause bonded network interfaces to alternately switch between unavailable and available. This occurrence is commonly known as flapping.
network-script line in /etc/xen/xend-config.sxp with the following line:
(network-script network-bridge-bonding netdev=bond0)
Domain attempted WRMSR. These messages can be safely ignored; furthermore, they are rate limited and should pose no performance risk. (BZ#477647)
hda: lost interrupt errors.
| Revision History | |||
|---|---|---|---|
| Revision 1.01 | Thu Apr 22 2010 | ||
| |||
| Revision 1.0 | Wed Nov 26 2009 | ||
| |||