WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] openvswitch on xen 4.1

To: Mario <mario@xxxxxxxxxxxxxx>
Subject: Re: [Xen-users] openvswitch on xen 4.1
From: Todd Deshane <todd.deshane@xxxxxxx>
Date: Thu, 9 Jun 2011 20:44:54 -0400
Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 09 Jun 2011 17:46:27 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=lSzK9duTKcCb/8GZwGZTH0NABuRl7ubd9YxzhBDdRFE=; b=ryhKGPyo/OJoDhwC6D4Eup4avN0k2Ki71GYY8nsGANH2ECqOC703iSzyp9p1yTMEum f70YlZ4PcQox1zo0tvy+ciaT5ciq1YKJqDMRQ/o6RYwPyhXAowFlvklpOekBm26fBvSu jaiTyFGOkfaiPhZ1zB74AzIobJCf3AdxLilQ8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=vfrLl3hUVbWD1KagfI92GrssNAGVtBtlHQVtMAS47S0xMiIjPNR4cdHCYhXruJCcOq Q19zS/GmaFYUc0p5oEjw1CBnbFudhzxZppBEHCnf/zMTsQl4c1zzj9Qnoqk9toVyL9My n0oDP6NJqQrlypTn9YsKdQStUFzn6kgvyBvsY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DF11C8D.70502@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4DF0D09B.7010109@xxxxxxxxxxxxxx> <BANLkTinScmXPBwJdbgvcghZMZ6zF9qP3vw@xxxxxxxxxxxxxx> <4DF11C8D.70502@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Jun 9, 2011 at 3:18 PM, Mario <mario@xxxxxxxxxxxxxx> wrote:
> On 06/09/2011 08:44 PM, Todd Deshane wrote:
>>
>> On Thu, Jun 9, 2011 at 9:54 AM, Mario<mario@xxxxxxxxxxxxxx>  wrote:
>>>
>>> Hello,
>>>
>>> It seems that /etc/xen/scripts/qemu-ifup is being ignored by xl.
>>
>> This may happen if you have an existing bridge device, since Xen 4.1
>> networking works a bit differently.
>>
>> http://wiki.xensource.com/xenwiki/MigrationGuideToXen4.1%2B
>>
>> It might still be a bug, but let's try to narrow that down a bit.
>>
>
> I start my networking with:
>
> if [ -x /etc/rc.d/rc.openvswitch ]; then
>  echo "Starting Open vSwitch:  /etc/rc.d/rc.openvswitch"
>  /etc/rc.d/rc.openvswitch start
>  /sbin/ifconfig eth1 down
>  /sbin/ifconfig eth1 0.0.0.0 up
>  /usr/bin/ovs-vsctl -- --may-exist add-br public
>  /sbin/ifconfig public 0.0.0.0 up
>  /usr/bin/ovs-vsctl -- --may-exist add-port public eth1
>  for i in $(ovs-vsctl list-ports public|grep -v eth1); do
>    ovs-vsctl del-port $i
>  done
> fi
>
> This brings up a bridge called "public" and it lets me add vif/tap's into
> it, not pretty but it works.
>
>
>>> My xl.conf has: vifscript="/etc/xen/scripts/vif-openvswitch", and this
>>> works
>>> fine for vifX.X devices. In order to make tapX.X work i hacked in the
>>> following:
>>>
>>> ovs-vsctl -- --may-exist add-port ${bridge} ${vif/vif/tap}
>>>
>>
>> Where did you put this line?
>>
>
> To make it easier, here is a script that i modified to get things worknig:
>
> http://dev.slackverse.org/tmp/openvswitch
>
> Basicly i have only added "/sys/class/net/${vif/vif/tap}/uevent" check, wich
> overwrites $vif variable so that script can be used for both vif and tap
> interfaces. As i said before, qemu-ifup gets ignored, so i had no other
> alternative.
>
> One more thing i noticed is that "offline" is never called, so interfaces
> never get cleaned up from bridge.
>
> When testing with 'xm' i remove $vif override, and everything works fine.
> Interfaces get added/removed from bridge, and tap gets added with qemu-ifup
> script.
>

So are you saying that this is perhaps a bug in xl? (as compared to xm)

> Can i help any more?
>
>
>>> Is there a better way to make tap interfaces work ?
>>>
>>> Thanks,
>>> mario
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-users
>>>
>>
>>
>>
>



-- 
Todd Deshane
http://www.linkedin.com/in/deshantm
http://www.xen.org/products/cloudxen.html
http://runningxen.com/

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>