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

[Xen-users] vlan id configuration on domU on Xen

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] vlan id configuration on domU on Xen
From: Bhargava Ramu Kavati <ramu.kavati@xxxxxxxxx>
Date: Mon, 11 Jan 2010 12:51:53 +0530
Delivery-date: Sun, 10 Jan 2010 23:22:35 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=07mLMEoJ8cz5t/a/b38/0wH/rhD65Vx9y/vxPnFxUzc=; b=E3dG/GnY7K6UZR/cdfGVthw48asnDWIW1/1kiDAHRrbfSeS45b+PEQZJ7GJfHuljxX QuqXpVGJ4bgCbthQhBSdr3CfNK2Y70oU1jhM2UYSAllxmlrS5nYjU28EAEUIWoid3rA2 AamtBN4wkhbSt75Um/nkJyBkS6DejGedQM/PU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=MbajmzPBITokI7N37S3b6PSpYsbNTLO5imp0vtrs4/EXndoIxuVJbyeVpRAAJwRO7W V/AhUdFbkv5GFWWOaCUIxF4IMRL/pLO17UlkxeiW5s+KL0qNTkAXWb0C2xHO84PyfkZV h84Fb5aaUc2IDwVHm11r8HKjxvZP6tkmMpoPw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,
I am using the below procedure for vlan configuration with ethernet interface sharing on Xen.
i) configure vlan on interface that is to be shared. 
   vconfig add ethx 5
ii) Call the below script from xend-config file.
    dir=$(dirname "$0")
    "$dir/network-bridge" "$@" netdev=ethx.5 vifnum=0 bridge=xenbr0V5
iii) Use the bridge created above in VM's config file.
iv) Ping from all the VMs (to which ethx.5 is shared) to external host (which is already in vlan id 5) succeeds. 
If we want to verify the same scenario on ESXi, first vswitch needs to be configured with vlan id 4095 and the VM need to be configured with vlan id 5 ("vconfig add ethx 5" on VM).  Then ping from VM to external host (already in vlan id 5) succeeds.
Whereas in case of Xen, we did not configure the VM's interface using "vconfig add".  We just attached VM's interface to xenbr created.  

Can you please clarify why the approach is different on Xen when compared to ESXi.  Is there any design/security related issue here on Xen?
Thank you in advance.....

Thanks & Regards,
Ramu
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>