RHBA-2010:0205: bug fix and enhancement update
153
BZ#519204
1379
•
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.
BZ#521053
1380
• A typographical error in an XML domain file caused
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.
BZ#523418
1381
• Devices that are assigned below a non-ACS switch can cause transactions to bypass the VT-d
hardware and the validation process.
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.
BZ#526713
1382
• When querying Xen remotely virsh would sometimes raise an "unknown failure" error. The
semantics were modified and where possible, the error is now more informative.
BZ#531729
1383
• When using
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.
BZ#531735
1384
• When a network created a bridge, it would only be enabled if the host had an IP on that bridge. This
would cause the bridge creation to fail quietly, and packets would not be passed as expected. The
error messages were improved for bridge creation and deletion, and if a failure occurs, it will now
produce an informative error.
BZ#532834
1385
• HVM VT-d PCI passthrough attach and detach was not working correctly and devices could not be
hotplugged. The attach and detach code now has additional checks and hotplugging functions as
expected.
BZ#546671
1386
• When
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.
BZ#555309
1387
• When the host was running the KVM hypervisor, the
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
Summary of Contents for ENTERPRISE LINUX 5.5 - S 2010
Page 10: ...x ...
Page 308: ...298 ...
Page 310: ...300 ...
Page 468: ...458 ...
Page 470: ...460 ...