Is there anyway to avoid bridging for VM to VM communication?
Fasiha Ashraf
Unlimited freedom, unlimited storage. Get it now
Add more friends to your messenger and enjoy! Go to
http://messenger.yahoo.com/invite/
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2009/3/19 Fasiha Ashraf <feehapk@yahoo.co.in>:> Is there anyway to avoid bridging for VM to VM communication?I don''t think so. Is there a reason why you want to avoid bridging? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Mar 19, 2009 at 8:05 PM, Fasiha Ashraf <feehapk@yahoo.co.in> wrote:> It causes much overhead in case of virtualizing wireless networks thats why!Ah, wireless :) It''s not simply overhead, bridging a wireless interface (AFAIK) won''t work. One option is network-route http://wiki.xensource.com/xenwiki/XenNetworking#head-740e3cf58c2ac48051f74c4f72cc6df52117e87e I believe you need to setup NAT manually to allow domU to access outside world using this method. The other option is go with what redhat does. Using libvrtd, they create another bridge called virbr0. You can put domU''s vif on that bridge and it will behave similar to Vmware''s NAT networking (NAT and dhcp is configured automatically). Note that the bridge is on virbr0, not on the wireless interface. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
what if i use Vyatta''s product VC5 for VM to VM communication? Fasiha Ashraf --- On Thu, 19/3/09, Fajar A. Nugraha <fajar@fajar.net> wrote: From: Fajar A. Nugraha <fajar@fajar.net> Subject: Re: [Xen-users] To avoid Bridging To: "Fasiha Ashraf" <feehapk@yahoo.co.in> Cc: "xen-users@lists.xensource.com" <xen-users@lists.xensource.com> Date: Thursday, 19 March, 2009, 6:19 PM On Thu, Mar 19, 2009 at 8:05 PM, Fasiha Ashraf <feehapk@yahoo.co.in> wrote:> It causes much overhead in case of virtualizing wireless networks thats why!Ah, wireless :) It''s not simply overhead, bridging a wireless interface (AFAIK) won''t work. One option is network-route http://wiki.xensource.com/xenwiki/XenNetworking#head-740e3cf58c2ac48051f74c4f72cc6df52117e87e I believe you need to setup NAT manually to allow domU to access outside world using this method. The other option is go with what redhat does. Using libvrtd, they create another bridge called virbr0. You can put domU''s vif on that bridge and it will behave similar to Vmware''s NAT networking (NAT and dhcp is configured automatically). Note that the bridge is on virbr0, not on the wireless interface. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users Did you know? You can CHAT without downloading messenger. Go to http://in.webmessenger.yahoo.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Why do you want to avoid bridging??>>> On 2009/03/19 at 06:13, Fasiha Ashraf <feehapk@yahoo.co.in> wrote:Is there anyway to avoid bridging for VM to VM communication? Fasiha Ashraf Unlimited freedom, unlimited storage. Get it now ( http://in.rd.yahoo.com/tagline_mail_2/*http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/ ) Share files, take polls, and make new friends - all under one roof. Click here. ( http://in.rd.yahoo.com/tagline_groups_8/*http://in.promos.yahoo.com/groups/ ) This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Mar 19, 2009 at 8:42 PM, Fasiha Ashraf <feehapk@yahoo.co.in> wrote:> what if i use Vyatta''s product VC5 for VM to VM communication?So I''m guessing what you''re trying to do is : - test Vyatta in a virtual environment (Xen) - have several VMs as test hosts, one of them is Vyatta - you''re running all of this on a notebook (which explains the wireless) - the VMs will PROBABLY need access to internet If that is correct, then it''s MUCH easier for you to use Vmware server since it allows you to easily create several private vm-only networks and NAT networks, so you could easily simulate several networks with Vyatta as router. If you still want to go with Xen, then AFAIK bridged setup is the way to go, but you should NOT bridge the wireless interface. Instead, you create several bridges with "brctl addbr" command, and not attach it to any physical interface. You put domUs on those bridges, which should create a private vm-only network. You can also assign IP address to some of the bridges, and setup iptables NAT rules. The Vyatta VM should have at least to NICs, one connected to vm-only bridge and the other to the NATted bridge. Note that this setup involves lots of command line, so it''s probably MUCH easier if you use Vmware server instead. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users