2015-10-30 13:00 GMT+03:00 Michal Privoznik <mprivozn@xxxxxxxxxx>: > Oh right, libvirt only know how to deal with channels. ISA serials are > ignored when it comes to qemu-ga. The problem is that from looking at > <serial/> we don't know which one is suppose to be for the agent. For > instance: > > <serial type='pty'> > <source path='/dev/pts/28'/> > <target port='1'/> > <alias name='serial1'/> > </serial> > > <serial type='unix'> > <source mode='bind' path='/tmp/serial.sock'/> > <target port='0'/> > <alias name='serial2'/> > </serial> > > which one of these should be agent listening to? And subsequently which > one should libvirt connect to? > > We can add an attribute somewhere to denote that fact, but you'd still > need to configure the guest agent inside the guest to run properly. This is not problem - i'm create fallback (if virtio-serial is absent, try to isa-serial) Now i'm need only libvirt side, may be use alias name org.qemu.... to determine on which channel works qemu-ga ? -- Vasiliy Tolstov, e-mail: v.tolstov@xxxxxxxxx -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list