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-devel

[Xen-devel] 802.1Q VLAN support

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] 802.1Q VLAN support
From: Luis Vinay <luisvinay@xxxxxxxxx>
Date: Wed, 05 Dec 2007 10:48:56 -0300
Delivery-date: Wed, 05 Dec 2007 05:55:48 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=EtMOZwECJViJj5suRMr24LCqtMAn25atI/wxFyI1y/M=; b=rncC6yDFsBkAZ9ina/LRJfK7QmtvZPrjOCC8IpqIUs39mz1v5f64cBloWHX5S7PVm+YxkdlN94NN6XADHlduNVRb/9cezWNaxMrW39r/ENT7o/8rcAEUZ6RtJeanQk6D2SpmbbxZEC1vrD4Qnj1dmf3hGUn4BG3Hi9DauLrrpdk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:subject:from:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=bDIeTZq/zZvg8oX332Ldf3T7xUlIpEjoF+hx/MmkBKHKuHFg+gtbs0+lvtyU2NbZNqhQhoQrgeWW/8a5WCpF8O3BUXXNoEtxY8XKEn/FZPRyMGcsWxwz0OnYexk4tKp3EM2sWlnj8Nx3bVbuBU5DxsBd2M+isaKnrgO6yk8HetA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
  I'm working on adding the 802.1Q vlan suport to Xen. Half of the work
is done. The idea is that we can specify something like this on the domU
configuration file:

vlan = [ 'pdev=eth1, vlanid=123, bridge=xenbr1123',
         'pdev=eth1, vlanid=100 ' ]

perhaps even specify an IP address (I founded this usefull in some
implementations), and then, as allways:

vif = [ 'bridge=xenbr1123, mac=00:16:3e:00:00:00',
        'bridge=xenbr1101, mac=00:16:3e:00:00:01' ]

and perhaps also specify a list in xend-config.spx.

I'll check if the bridge is already created before connecting the VIF,
at domU creation, if not bring it up, and when destroying the domU, also
check if other domU is using the same bridge before shuting it down.

All this raises me some questions:

  - Suggestions/advices regarding on where/how put my code?
  - Could it bring problems if I add this code in 'xen/xm/create.py'?

gopts.var('vlan', val="iface=IFACE,vlanid=VLANID,vlanbridge=VLANBRIDGE",
          fn=append_value, default=[],
          [...]

  - Other suggestions/advices?

best regards

-- 
/* ---
 Luis Vinay
 XTech - Soluciones linux para Empresas
 lvinay@xxxxxxxxxxxx
                                  --- */


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

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