Bug 801524 - [RFE] Add syntactic sugar to enable guest agent communication
Summary: [RFE] Add syntactic sugar to enable guest agent communication
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-08 18:08 UTC by Dave Allan
Modified: 2016-04-26 16:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-08 20:09:04 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dave Allan 2012-03-08 18:08:57 UTC
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.

Comment 2 Daniel Berrangé 2012-03-08 18:25:54 UTC
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.

Comment 3 Dave Allan 2012-03-08 20:09:04 UTC
Ok, I'll buy that.


Note You need to log in before you can comment on or make changes to this bug.