Either way, you will have to tailor Xen to use OVS, in approximately the same way.
On Tue, Jun 28, 2011 at 10:09:43AM -0700, James Hongyi Zeng wrote: > Does that mean installing OVS in RHEL+XEN is same to the installation in > RHEL? > > On Tue, Jun 28, 2011 at 10:03 AM, Ben Pfaff <[email protected]> wrote: > > > On Tue, Jun 28, 2011 at 09:55:21AM -0700, James Hongyi Zeng wrote: > > > First, I got "openvswitch_mod: exports duplicate symbol > > > br_should_route_hook (owned by bridge)". When I try to remove bridge.ko, > > I > > > got "ERROR: Module bridge is in use by xt_physdev". When I try to remove > > > xt_physdev, I got "ERROR: Module xt_physdev is in use". How can I > > workaround > > > this? > > > > > > And, how can I make sure the openvswitch_mod is always loaded before > > > bridge? When I run modprobe, it seems to me that openvswitch_mod is not > > > loaded in the ko pool after make install. > > > > You have two choices regarding the kernel module. You can upgrade to > > a kernel new enough that the bridge and the Open vSwitch kernel > > modules can coexist, or you can refrain from loading the bridge module > > at all. > > > > "make install" by itself doesn't install the kernel module. To > > install the kernel module, run "make modules_install" from > > datapath/linux-2.6 in the source tree. > > > > > [hyzeng@nms-oexp2 drivers]$ sudo modprobe openvswitch_mod > > > FATAL: Module openvswitch_mod not found. > > > > > > Is there anything I should pay attention to when installing OVS in > > > opensource Xen on RHEL? > > > > Another option is to use the RHEL RPM packaging available in the > > "master" branch of the Open vSwitch Git repository. > > _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
