On Tue, May 16, 2017 at 10:28:27AM +0300, Vasiliy Tolstov wrote: > 2017-05-16 9:32 GMT+03:00 Peter Krempa <pkrempa@xxxxxxxxxx>: > > 3.3.2? We dropped micro versions some time ago. > > > > This is copy/paste from link element, sorry. > > >> + </p> > >> + > >> <h5><a name="mtu">MTU configuration</a></h5> > >> <pre> > > > > > > There already is an element called <link> with attribute "state" which > > modifies the link state in qemu. So that maps to guest link state. So > > this patch has a naming collision going on. > > Yes, but some times ago Laine Stump says that for host side link > status we can use source element with link state. > > > > > I also don't really see how modifying the host side link state would be > > useful. Could you elaborate why you think it would be useful? > > OSPF - tap device have addresses assigned to it and bird/quagga create > routing based on interface link status and addresses on device. > So if i have host side device in up state no matter that have guest - > host system forward traffic to it. So i need to modify host side link > status too. Shouldn't we just tie the host & guest link state together then. This doesn't seem like enough of a reason to introduce new XML elements. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
