Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
qemu 0.12 introduced -chardev arguments, but libvirt 0.8.7 doesn't know how to parse those back into XML. As a result, the conversion from qemu command line to libvirt XML ends up sucking in the <qemu:commandline> namespace, even though a proper conversion to <devices> would be more appropriate.
Round-tripping ALL libvirt-generated qemu command lines back to libvirt is not quite possible, at least, not without further enhancing virsh domxml-to-native to support a new 'argz' or 'shell' mode (where the arguments are either NUL-terminated or shell-quoted); the current output is ambiguous for any qemu argument that legitimately contains whitespace (such as smbios entries). But that may also be worth fixing upstream.
Version-Release number of selected component (if applicable):
libvirt-0.8.7-4.el6
How reproducible:
100%
Steps to Reproduce:
1. find a simple libvirt XML for a domain with at least one device. To save me typing, I did cp libvirt/tests/qemuxml2argvdata/qemuxml2argv-console-virtio.xml dom.xml
2. convert the xml to native: virsh domxml-to-native qemu-argv dom.xml > dom.args
3. try to convert it back: virsh domxml-from-native dom.args
Actual results:
the resulting output is full of <qemu:arg> entries that libvirt couldn't parse, even though the original XML was completely understood by libvirt to generate the qemu command line in the first place
Expected results:
the output should be more or less identical to the original input (this doesn't completely have to be true, since libvirt may have modernized old xml constructs into newer), at least to the point of no <qemu:...> namespace elements.
Additional info:
So far, no one has reported this as a bug upstream, so it might not be a very-often used feature. But since RHEL supports only libvirt and not direct qemu invocation, getting this to work well would ease conversion from people with qemu setups into supported libvirt setups.
Comment 2RHEL Program Management
2011-04-04 02:07:35 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.