Red Hat ENTERPRISE LINUX 5.5 - TECHNICAL NOTES Manual page 162

Chapter 1. Package Updates
allocation and permissions information, but not capacity information, and the command now works
as expected.
1371
BZ#510450
• When an XML configuration file was generated using 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.
1372
BZ#512069
• Running concurrent TLS connections under the libvirt python wrapper caused libvirt to
crash. Changes were made to the way that GNUTLS handles threading and the crash no longer
occurs.
1373
BZ#512367
• 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.
1374
BZ#514082
• Creating npiv devices works as expected, but puts error messages into the /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.
1375
BZ#514324
• The 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.
1376
BZ#514532
• Guests that use the default source clock try to compensate for lost ticks by reading the TSC as well.
This can cause the guest clock to go out of synchronization. All Red Hat Enterprise Linux guests
now unconditionally add --no-kvm-pit-reinjection to the qemu command line, and the guest
no longer falls out of synchronization.
1377
BZ#517278
• 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.
1378
BZ#517460
• When a migration was performed to a virtual machine that had been paused, the virtual machine
would no longer be paused after the migration had completed. The behavior of qemu-kvm was
changed so that it no longer 'forgets' the virtual machine is paused, and it will now stay paused
during a migration.
152