On Tue, 2017-07-11 at 14:56 -0400, Laine Stump wrote:
> The cleanest way to make this work would be to enhance the function
> qemuDomainChangeNet() to know what to do when it detects that the
> vlan
> tag was changed with a device update ("virsh update-device") - this
> command can take effect immediately rather than waiting until the
> next
> time the domain is started, so the XML that is migrated would have
> the
> new vlan tag already in place (and also you wouldn't need to issue
> the
> ovs-vsctl command for it out of band any more!).
>
> Currently that function notices that the vlan tag has changed, but
> this
> just leads to an "UNSUPPORTED" error. If the network type is OVS,
> then
> it *should* work to just reconnect the bridge (libvirt sets the vlan
> tag
> as part of connecting to the ovs bridge).
>
> So how are your programming chops? :-)
>
Hi Laine,
Thank you for the answer!
I finally achieved to implement what you suggested. :-) I'll post the
patch on the developer ML in a few days.
Antoine
_______________________________________________
libvirt-users mailing list
libvirt-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvirt-users
