Red Hat Bugzilla – Bug 212272
libxc does not propagate errors during domain creation back to XenD
Last modified: 2007-11-30 17:07:36 EST
Description of problem:
The libxc library is used by XenD for creating guest domains. When a problem
occurs, it simply returns -1, sets errno to -EINVAL and does an printf to stderr
with the actual error message. This means that XenD does not get back any useful
information about the failure. In turn applications like virt-manager can not
give the user any useful info about what went wrong.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to create a VM using a non-PAE kernel on a PAE i686 hypervisor
Error message '-EINVAL'
Message about PAE mismatch in guest kernel
Another scenario where current lack of error reporting caused issues
Patches for libxc posted upstream, but not accepted in current form
We absolutely must get the patches accepted upstream before trying to
incorporate this change in RHEL, because it will require addition of new APIs &
we definitely don't want to supporting APIs which don't get accepted.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Plus some further fixes / cleanups:
Should be possible to apply to 3.0.3 without too much change.
This fix was picked up as part of the rebase of libxc to 3.1.0. The fix is built
into xen-3.0.3-27.el5 in dist-5E-qu-candidate
When trying to start a 32-bit non-PAE kernel on a PAE hv I now see
# virsh start break
libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating
domain: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32
not supported by xen kernel, sorry\\n')")
error: Failed to start domain break
Which is desired behaviour
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.