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.
Currently a user of the qemu guest agent must manually configure a virtio-serial communication channel to enable libvirt to talk to the agent. IMO it would make things easier on users to create a tag in the domain XML like <enable-agent/> or similar to set up the channel automatically.
The way we currently configure virtio serial devices is not the way it will be done long term. Currently libvirt manages comms with the guest agent, so we must specify a full set of config parameters for a UNIX socket backend. In the future QEMU will manage comms, and so the setup will be more like the spice agent config.
Either way, I don't think we should be adding syntactic sugar to the XML in this way. If ease of use if the desire, then you've already lost big time, by being near the XML, and there are many many other areas of libvirt XML that are just as verbose as agent config is, without syntactic sugar.
The focus should be on making virt-manager/virt-install do the right thing, for usability, and documenting the fine details for libvirt XML, not sugaring the XML schema.