Hi, Jen-Wei. We haven't made any decisions about removing support for bridge compatibility. We had an internal discussion about this earlier today, and libvirt support was brought up as a possible issue. Before we remove support from the distribution, we'll make sure to seek input from the community. We should be able to find some time to fix the bugs Ben mentioned before long.
Thank you for giving your feedback and making us aware of your use-case! --Justin On May 3, 2011, at 8:20 PM, Jen-Wei Hu wrote: > Hi all, > > Currently, we use ovs to be the vSwitch in OpenNebula and work properly after > loading kernel module ovs-brcompatd. If we are right, we must load > ovs-brcompatd, the vm tool virt-manager could manage VMs smoothly. If we > don't do this, that is, we create bridge from ovs command, virt-manager will > complain that it didn't know the bridge and fail to create VM. But, today I > got the forum message from > http://openvswitch.org/pipermail/discuss/2011-May/005127.html, the experts > say it will be remove this module in the later time. My question is if it > really remove ovs-brcompatd later, how ovs to take this work? Or currently, > the ovs could do this while we are not work hard to know it? > > Thanks > > Jen-Wei > _______________________________________________ > discuss mailing list > discuss@openvswitch.org > http://openvswitch.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
