On Thu, Jan 19, 2012 at 03:18:00PM -0700, Eric Blake wrote: > On 01/17/2012 04:44 AM, Michal Privoznik wrote: > > There is now a standard QEMU guest agent that can be installed > > and given a virtio serial channel > > > > <channel type='unix'> > > <source mode='bind' path='/var/lib/libvirt/qemu/f16x86_64.agent'/> > > Do we really want to be documenting a path in the libvirt-controlled > hierarchy? This is an artifact of the way we are doing the guest agent support today. If you look at the SPICE guest agent, there is a special channel type 'spicevmc' that is used, and QEMU deals with that internally. In the future, QEMU will deal with its own guest agent internally and thus we'll have a new channel type kinda like 'spicevmc' which does not expose any paths. For now though, we're using the externally managed agent for which we do want to expose the path IMHO. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list