Red Hat ENTERPRISE LINUX 5.5 - S 2010, Manual

Page: 148 / 470

Chapter 1. Package Updates
138
• If one or more VCPUs was disabled, VCPUs would appear in Windows Server 2008
Device
Manager
as devices with the
!
symbol indicating an error. Windows does not handle CPUs marked
as present (bit 0 in ACPI spec), but not enabled (bit 1), which causes this issue.
However, there are situations where Linux expects CPUs to be present but not enabled. This is a
heuristic test used by Linux to determine if a CPU is hot-pluggable.
The updated package fixes virtualized CPU detection for Windows but breaks the ability to hot-add
CPUs into Linux guests. (
BZ#495844
1250
)
• Using the numeric keypad of a keyboard with or without
Num Lock
produced erroneous input on
guests accessed with VNC through the QEMU monitor application. The number pad keys should
now work for input on guests accessed with VNC. (
BZ#497507
1251
)
• An unhandled interrupt from the kvm_vcpu_block() call unhalted a VCPU outside of the interrupt
window. As a consequence, when the "
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
1252
)
• Windows Server 2008 R2 guests would hang after a restart if the guest was created with multiple
VCPUs. This was caused by not properly filtering non-maskable interrupts (NMIs) from the guests
during the restart procedure. The updated packages fix this issue and Windows Server 2008 R2
guests can successfully use multiple VCPU. (
BZ#502543
1253
BZ#503322
1254
)
• Migrating a paused guest caused the guest to resume at the destination. Paused guests now remain
paused after a migration. (
BZ#503367
1255
)
• Multiple virtualized guests using the hypercall device resulted in one or more of the guests using
100% of their assigned CPUs or becoming unresponsive. The updated packages fix the hypercall
device, preventing this issue. (
BZ#503759
1256
)
• VCPUs were not reported correctly to Windows XP guests. On the Windows XP guest the number
for CPUs listed in
Task Manager
was lower than the number of CPUs assigned to the guest.
Windows XP guests should now use and display the number of VCPUs assign if the guest can
handle that number of CPUs. (
BZ#508040
1257
)
• A segmentation fault occurred when a guest used a
i82551
emulated network interface card was
used. The segmentation fault is fixed in the packages. (
BZ#510706
1258
)
• Creating guests that use both 64k and 4k image block cluster sizes and virtualized IDE as the
storage device driver would cause a segmentation fault in the
qemu-kvm
process. The updated
packages resolve this issue. (
BZ#542923
1259
)
• Running the
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
1260
)
• A segmentation fault occurred when using the
qemu-img rebase
command to rebase an image
snapshot. (
BZ#563141
1261
)
• The
qemu-img rebase
command failed with an "Operation not supported" error message when it
was run on locally-attached block devices. (
BZ#569762
1262
)