[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] how to enable dom0 and domu share same physical network...



Yeah I am letting scripts do it. Since if I define bridge between dom0 and domu's on a physical host then that becomes a different subnet as compared to physical hosts.

The bridge created through scripts should basically act as virtual hub.

~Ashish

From: RabidCicada [rabidcicada@xxxxxxxxx]
Sent: Wednesday, November 28, 2012 3:08 PM
To: Tapdiya, Ashish
Cc: Alexandre Kouznetsov; xen-users@xxxxxxxxxxxxx
Subject: Re: [Xen-users] how to enable dom0 and domu share same physical network...

Or you let the bridge-Utils do that.
 
Also...I've found you typically need to reboot the Dom0 after setting up the bridge stuff with Xend/BridgeUtils.  It seems there is something fishy with it sometimes.


On Wed, Nov 28, 2012 at 4:08 PM, RabidCicada <rabidcicada@xxxxxxxxx> wrote:
Did you mean "not defining any bridge in /etc/network/interfaces of dom0" in your previous email?
If so...then you should be doing that I believe.  You HAVE to create the bridge on Dom0 to be the bridge for the domU's


On Wed, Nov 28, 2012 at 4:02 PM, Tapdiya, Ashish <ashish.tapdiya@xxxxxxxxxxxxxx> wrote:
Specifying bridge=xenbr0 in vif parameter of config file is not working either since i am defining any bridge in /etc/network/interfaces of dom0.

I want the bridge in dom0 to act as a virtual hub and am following instructions from folowing web page for bridge networking scenario where all machines are within the same IP address range
http://wiki.kartbuilding.net/index.php/Xen_Networking

~Ashish
________________________________________
From: xen-users-bounces@xxxxxxxxxxxxx [xen-users-bounces@xxxxxxxxxxxxx] on behalf of Alexandre Kouznetsov [alk@xxxxxxxxxx]
Sent: Wednesday, November 28, 2012 2:41 PM
To: xen-users@xxxxxxxxxxxxx
Subject: Re: [Xen-users] how to enable dom0 and domu share same physical        network...

Hello.

El 28/11/12 14:26, Tapdiya, Ashish escribió:
> i tried specifying mac as well but no luck
> vif = ['mac=00:16:3e:00:00:01,ip=192.168.1.200']
It could work either way, unless your DomU gets confused by the MAC
change no every boot. Generally, it's a good idea to define a static and
specific MAC to each DomU's vif.

>> Please, show this output:
> "xm list" from both of your Dom0.
> Name                                        ID   Mem VCPUs      State   Time(s)
> Domain-0                                     0  6705     4     r-----     45.0
> domu4                                        2  2048     1     -b----      2.5
>
>
>> "brctl show" from both of your Dom0.
> bridge name   bridge id               STP enabled     interfaces
> tmpbridge           8000.feffffffffff       no              vif2.0

This is not the complete output of "brctl show", is it? xenbr0 is the
here. Anyway, your issue is more clear now.

Silly me! Lukas is right, your vif definition needs a bridge definition!
As he said, "vif = ['ip=IP,bridge=xenbr0']" should work.

I would change that to "vif = ['mac=MAC,bridge=xenbr0']".

"vif = ['ip=IP,mac=MAC,bridge=xenbr0']" shall also work, but the IP
address is surely defined within DomU. Whatever you specify in "vif"
directive as IP address, will not be taken into account normally,
although sometimes it's useful to mention it in the config file for
reference.

(such weired way to quote original mail, but whatever)

--
Alexandre Kouznetsov


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users



--
"Ambush!?....I just ambushed you with a cup of coffee"
-CIA agent (RONIN)



--
"Ambush!?....I just ambushed you with a cup of coffee"
-CIA agent (RONIN)
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.