RHBA-2010:0294: bug fix and enhancement update
275
The updated packages resolve this issue by fixing the virtualized ATA driver. The updated packages
cause the following issue on the guest:
ata2.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 complete
After this error the guest should successfully boot. (
BZ#480317
2156
)
• The Xen daemon would hang if a user attempted to shut down or save a paused guest. Guests
cannot be saved or shut down if the guest is in a paused state as those operations can only
be conducted on running guests. The updated Xen daemon will no longer hang but the user is
presented with the following warning:
Error: Can't shutdown/save the domain since the domain is paused; unpaused it first if you
want to shutdown/save
To shut down or save a guest in a paused state, the guest must first be unpaused by the user.
(
BZ#504910
2157
)
• Sufficient memory was not reserved for fully virtualized guests when creating new guests. Memory
listed as available by the
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)')
This issue has been resolved by improving the memory balloon driver to correctly allocate memory
for fully virtualized guests and fully virtualized guests using the Intel VT-d extensions for PCI
passthrough. (
BZ#512041
2158
)
• An error message appeared when attempting to detach a PCI device from a para-virtualized guest.
The error is corrected in the updated packages. PCI passthrough is only supported by Xen full
virtualization and not by para-virtualization. (
BZ#512307
2159
)
• Scheduling was reset if a guest was saved and restored. Scheduling data is now preserved when a
guest is saved and restored. (
BZ#513211
2160
)
• A race condition between the
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
2161
)
• The
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
2162
)
• An uninformative error message appeared when the
xm pci-list-assignable-devices
command was executed. The
pciback
kernel module must be loaded before executing the
xm
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 ...