On 21/03/13 02:47, Ian Campbell wrote: > On Wed, 2013-03-20 at 23:32 +0100, Daniel Pocock wrote: > >> Should the script be using the ovs-vsctl command instead of brctl? >> > As a general rule one should be using the ovs tools directly wherever > possible and not the brctl compat layer. > > >> Or >> have I misconfigured something and the wrong script is being run? >> > This is something which AFAIR differs between upstream Xen and XCP. With > upstream Xen we disable the qemu script explicitly and expect the xen > vif hotplug scripts (which handle Xen tap devices too) to do the job, > that is the scripts under /etc/xen/scripts/vif-foo (for foo in bridge, > openvswitch etc) > As you explained earlier, my dom0 had both a tap20.0 and a vif20.0 for the HVM domU
I noticed that the vif20.0 interface was successfully added to the bridge during VM creation, presumably the script responsible for that used the ovs command instead of brctl While I could add some permanent hack to the script I modified above, and this might be important to include in the wheezy release, I don't want to second-guess the strategic way of sorting this out, would you know who is maintaining this part of XCP and how we can get some direction on this? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
