Thank you for the information. I did found and test the script you linked , without success.
But, we decided to switch to xl toolstack so I am no more investigation solutions for xm. With XL I have no more errors starting a VM (on the same server), the VIF are created but it doesn't get up nor attached to the bridge. However I am able to attach it manually and bring everything up and working. I guess I still miss some kind of ifup/ifdown script for Xen over OVS. If anybody has some to share... Thanks anyway, for the help and for this great software. Jean-François -----Original Message----- From: Hans van Kranenburg [mailto:od...@xs4all.nl] Sent: samedi 19 janvier 2013 20:31 To: discuss@openvswitch.org Cc: jf.la...@exxoss.com Subject: Re: [ovs-discuss] Installing OVS on open-source XEN (Debian) On 01/17/2013 03:44 PM, Jean-François Lalau wrote: > > Being new to OVS, I performed a clean install of > - Debian Wheezy (weekly release for January 14) > - XEN 4.1.3 > - OVS from Debian package [...] > I found some replacement scripts for the XEN supplied vif-bridge > scripts but none works and hours of searching for the issue in various > place brought nothing else than a headache. Did you find this post? http://lists.xen.org/archives/html/xen-users/2011-08/msg00071.html > So : > - Or is there some working scripts to replace native XEN scripts ? I haven't tested wheezy yet, but we've been using a slightly modified version of the vif-openvswitch script you can find in the post above since about a year in production with squeeze and backported openvswitch packages from wheezy. No bridge compat, the script directly issues openvswitch commands to attach the virtual interface of the domU to openvswitch. To use it, we set (vif-script vif-openvswitch) in /etc/xen/xend-config.sxp. You can find my version attached, diff it against the other one to see the changes. The author of the script chose to encode a specific (access-port) vlan to use into the bridge parameter of a vif in guest configuration, which could look like this (I use ovs0 instead of br0 for openvswitch): vif = [ "vifname=domU-0b-cb,mac=00:16:3e:00:0b:cb,bridge=ovs0.11", ] It's a bit weird because normally I use the dot-notation for vlan subinterfaces (like eth0.3) but while trying to fix that (refactoring it into e.g. bridge=ovs0,tag=11) we quickly discovered that's a pita, because adding an option name requires hacking around in lots of python files from xen. Anyway, it works (tm). I don't know how it fits together with xl instead of xm in Xen 4.1, not tested yet here. Hans van Kranenburg _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
