Red Hat ENTERPRISE LINUX 5.5 - S 2010, Manual

Page: 152 / 470

Chapter 1. Package Updates
142
• Guests could not eject CD-ROMs from physical CD-ROM drives attached to the guest. The updated
packages resolve this issue and guests can now eject CD-ROMs from physical CD-ROM drives.
(
BZ#539250
1302
)
• The
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
1303
)
• Migrations could fail due to invisible physical CPU states. A new set of IOCTL exports report user-
invisible states related to exceptions, interrupts, and Non-Maskable Interrupts (NMIs). These
functions allow management tools to prevent this type of failed migration. (
BZ#541084
1304
)
• Guests could not PXE boot with gPXE and an emulated
e1000
network interface card. The updated
packages fix this issue and guests can boot images using gPXE and the emulated
e1000
driver.
(
BZ#543979
1305
and
BZ#550265
1306
)
• The KVM process could become non-responsive if a networked or local connect to the QXL driver
was lost while the driver was running. This cause a "
qxl_display_update: waiting for
command
" error message to be printed in the logs. The updated packages resolve this issue.
(
BZ#544785
1307
)
• The
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
1308
)
• KVM did not verify if barriers were required for migration. KVM now verifies if barriers are required
for guest migration and disables barriers if they are not required. (
BZ#549938
1309
)
• The hypercall driver for Windows guests did not reset the device when the guest was shut down or
rebooted. This occasionally caused the driver to use 100% of the CPU and cause the guest to hang.
(
BZ#550755
1310
)
• The
kvm-qemu-img
command failed to convert sparse RAW image files to qcow2 sparse snapshot
image files. (
BZ#558195
1311
)
• Migration with the
-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
1312
)
• Removed a warning message which appeared when the
-initrd
option was used.
(
BZ#512672
1313
)
• The KVM kernel module would panic if the
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
1314
)
• Various issues with compiling the KVM modules and packages. (
BZ#533453
1315
,
BZ#533059
1316
,
BZ#539589
1317
and
BZ#533197
1318
)
• Removed a debugging message
qemu_popen: returning result of qemu_fopen_ops
that
displayed when saving a virtualized guest state into a compressed file. (
BZ#530533
1319
)