thr3ads.net - Xen users - how to enable dom0 and domu share same physical network... [Nov 2012]

If this information is useful, please help other people find it:
Share via:

Tapdiya, Ashish

2012-Nov-28 18:39 UTC

how to enable dom0 and domu share same physical network...

Hi,

I have two physical machines connected through a switch in a 192.168.1.* subnet.
Dom0''s are assigned static ip addresses 192.168.1.100, 192.168.1.101
respectively. Dom0''s can ping each other. Each physical machine has a
domu guest and static address assigned to domu''s are 192.168.1.200,
192.168.1.201 respectively.

However domu''s can neither ping each other nor dom0''s.
Similarly dom0''s cannot ping domu''s. Following are my
configuration specifics:

In /etc/xen/xend-config.sxp following entries are enabled
network-script network-bridge
vif-script vif-bridge

Domu''s /etc/network/interfaces static ip is assigned like this
auto eth0
iface eth0 inet static
address 192.168.1.200
netmask 255.255.255.0
gateway 192.168.1.2

if dom-u creation config file vif entry is as follows,
vif = [''ip=192.168.1.200'']

How to enable domu''s to share same physical network and become part of
192.168.1.* subnet.

Any help or pointer will be highly appreciated.

Thanks.




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

Alexandre Kouznetsov

2012-Nov-28 19:00 UTC

head link

Re: how to enable dom0 and domu share same physical network...

Hello.

If I understand right, DomUs can''t ping any Dom0 or any DomU that is
not
on the same physical machine.

I can see you do not specify a MAC address for your DomU''s vif. As far 
as I remember, it makes Xen to generate the MAC on the fly. If  DomU 
uses udev, it might think there is a new network interface on each boot, 
not eth0, so it fails to configure the network properly.

Please, show this output:
"xm list" from both of your Dom0.
"brctl show" from both of your Dom0.
"ifconfig" (and "ifconfig -a", if different) from your DomU.

Other test would be to try to ping DomUs from each other, as far as they 
are on the same physical machine, if your setup allows it.


Greetings.


-- 
Alexandre Kouznetsov

Lukas Laukamp

2012-Nov-28 19:09 UTC

head link

Re: how to enable dom0 and domu share same physical network...

Am 28.11.2012 19:39, schrieb Tapdiya, Ashish:> Hi,
>
> I have two physical machines connected through a switch in a 
> 192.168.1.* subnet. Dom0''s are assigned static ip addresses 
> 192.168.1.100, 192.168.1.101 respectively. Dom0''s can ping each
other.
> Each physical machine has a domu guest and static address assigned to 
> domu''s are 192.168.1.200, 192.168.1.201 respectively.
>
> However domu''s can neither ping each other nor dom0''s.
Similarly
> dom0''s cannot ping domu''s. Following are my configuration
specifics:
>
> In /etc/xen/xend-config.sxp following entries are enabled
> network-script network-bridge
> vif-script vif-bridge
>
> Domu''s /etc/network/interfaces static ip is assigned like this
> auto eth0
> iface eth0 inet static
> address 192.168.1.200
> netmask 255.255.255.0
> gateway 192.168.1.2
>
> if dom-u creation config file vif entry is as follows,
> vif = [''ip=192.168.1.200'']
>
> How to enable domu''s to share same physical network and become
part of
> 192.168.1.* subnet.
>
> Any help or pointer will be highly appreciated.
>
> Thanks.
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
Hello,

so the right scripts are set in xend-config.sxp. Does the system create 
a correct bridge and connects the DomU devices to the bridge when the 
DomU starts?

So in the case of a Debian/Ubuntu system you can do this very easy 
manually on this way:

Open /etc/network/interfaces with an editor and put in something like this:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto xenbr0
iface xenbr0 inet static
     address IP
     netmask NETMASK
     gateway GATEWAY
     bridge_ports eth0
     bridge_stp off
     bridge_fd 0

Then restart the network:

/etc/init.d/networking restart

Before you do this comment out the network-script network-bridge line in 
xend-config.sxp.

The vif line would look like this:

vif = [''ip=IP,bridge=xenbr0'']

Then should the DomU be able to communicate with the physical network.

The bridge-utils must be installed for this. For Red Hat based 
distributions you have to create a network script for eth0 and for the 
bridge. For any other distribution you can look in the documentation how 
to create bridges.

Best Regards


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

Tapdiya, Ashish

2012-Nov-28 20:24 UTC

head link

Re: how to enable dom0 and domu share same physical network...

________________________________
From: Lukas Laukamp [lukas@laukamp.me]
Sent: Wednesday, November 28, 2012 1:09 PM
To: Tapdiya, Ashish
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] how to enable dom0 and domu share same physical
network...

Am 28.11.2012 19:39, schrieb Tapdiya, Ashish:
Hi,

I have two physical machines connected through a switch in a 192.168.1.* subnet.
Dom0''s are assigned static ip addresses 192.168.1.100, 192.168.1.101
respectively. Dom0''s can ping each other. Each physical machine has a
domu guest and static address assigned to domu''s are 192.168.1.200,
192.168.1.201 respectively.

However domu''s can neither ping each other nor dom0''s.
Similarly dom0''s cannot ping domu''s. Following are my
configuration specifics:

In /etc/xen/xend-config.sxp following entries are enabled
network-script network-bridge
vif-script vif-bridge

Domu''s /etc/network/interfaces static ip is assigned like this
auto eth0
iface eth0 inet static
address 192.168.1.200
netmask 255.255.255.0
gateway 192.168.1.2

if dom-u creation config file vif entry is as follows,
vif = [''ip=192.168.1.200'']

How to enable domu''s to share same physical network and become part of
192.168.1.* subnet.

Any help or pointer will be highly appreciated.

Thanks.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org<mailto:Xen-users@lists.xen.org>
http://lists.xen.org/xen-users

Hello,

so the right scripts are set in xend-config.sxp. Does the system create a
correct bridge and connects the DomU devices to the bridge when the DomU starts?
>> Here is the output from brctl show
>>bridge name    bridge id        STP enabled    interfaces    tmpbridge        8000.feffffffffff    no        vif2.0

So in the case of a Debian/Ubuntu system you can do this very easy manually on
this way:

Open /etc/network/interfaces with an editor and put in something like this:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto xenbr0
iface xenbr0 inet static
    address IP
    netmask NETMASK
    gateway GATEWAY
    bridge_ports eth0
    bridge_stp off
    bridge_fd 0
>>I want the bridge to act as a virtual hub and domu''s to have an
ip from same subnet as dom0''s (physical hosts). In the above mentioned
bridge creation domu''s will be on a different subnets and then one domu
on a physical host cannot communicate with another domu on a different physical
host
Then restart the network:

/etc/init.d/networking restart

Before you do this comment out the network-script network-bridge line in
xend-config.sxp.

The vif line would look like this:

vif = [''ip=IP,bridge=xenbr0'']

Then should the DomU be able to communicate with the physical network.

The bridge-utils must be installed for this. For Red Hat based distributions you
have to create a network script for eth0 and for the bridge. For any other
distribution you can look in the documentation how to create bridges.
>> xen is 4.1.2
>> os is ubuntu oneiric
>> kernel is 3.0.51
Best Regards

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

Tapdiya, Ashish

2012-Nov-28 20:26 UTC

head link

Re: how to enable dom0 and domu share same physical network...

Hello.

If I understand right, DomUs can''t ping any Dom0 or any DomU that is
not
on the same physical machine.
>>yes
I can see you do not specify a MAC address for your DomU''s vif. As far
as I remember, it makes Xen to generate the MAC on the fly. If  DomU
uses udev, it might think there is a new network interface on each boot,
not eth0, so it fails to configure the network properly.
>>i tried specifying mac as well but no luck
>>vif = [''mac=00:16:3e:00:00:01,ip=192.168.1.200'']
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

"ifconfig" (and "ifconfig -a", if different) from your DomU.
>>
>>eth0      Link encap:Ethernet  HWaddr 00:16:3e:00:00:01           inet addr:192.168.1.107  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::216:3eff:fe00:1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:23 errors:0 dropped:0 overruns:0 frame:0
          TX packets:68 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4021 (4.0 KB)  TX bytes:3072 (3.0 KB)
          Interrupt:26
>>lo        Link encap:Local Loopback           inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1920 (1.9 KB)  TX bytes:1920 (1.9 KB)


Other test would be to try to ping DomUs from each other, as far as they
are on the same physical machine, if your setup allows it.
>> domu''s are on different physical machines 
>>Also,
>>xen is 4.1.2
>>os is ubuntu oneiric
>>kernel 3.0.51
>>Thanks for reply. I appreciate it.
Greetings.

________________________________________
From: xen-users-bounces@lists.xen.org [xen-users-bounces@lists.xen.org] on
behalf of Alexandre Kouznetsov [alk@ondore.com]
Sent: Wednesday, November 28, 2012 1:00 PM
To: xen-users@lists.xen.org
Subject: Re: [Xen-users] how to enable dom0 and domu share same physical       
network...

Hello.

If I understand right, DomUs can''t ping any Dom0 or any DomU that is
not
on the same physical machine.

I can see you do not specify a MAC address for your DomU''s vif. As far
as I remember, it makes Xen to generate the MAC on the fly. If  DomU
uses udev, it might think there is a new network interface on each boot,
not eth0, so it fails to configure the network properly.

Please, show this output:
"xm list" from both of your Dom0.
"brctl show" from both of your Dom0.
"ifconfig" (and "ifconfig -a", if different) from your DomU.

Other test would be to try to ping DomUs from each other, as far as they
are on the same physical machine, if your setup allows it.


Greetings.


--
Alexandre Kouznetsov


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

Alexandre Kouznetsov

2012-Nov-28 20:41 UTC

head link

Re: 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

Tapdiya, Ashish

2012-Nov-28 21:02 UTC

head link

Re: how to enable dom0 and domu share same physical network...

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@lists.xen.org [xen-users-bounces@lists.xen.org] on
behalf of Alexandre Kouznetsov [alk@ondore.com]
Sent: Wednesday, November 28, 2012 2:41 PM
To: xen-users@lists.xen.org
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@lists.xen.org
http://lists.xen.org/xen-users

RabidCicada

2012-Nov-28 21:08 UTC

head link

Re: how to enable dom0 and domu share same physical network...

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@vanderbilt.edu> 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@lists.xen.org [xen-users-bounces@lists.xen.org]
> on behalf of Alexandre Kouznetsov [alk@ondore.com]
> Sent: Wednesday, November 28, 2012 2:41 PM
> To: xen-users@lists.xen.org
> 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@lists.xen.org
> http://lists.xen.org/xen-users
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>


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


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

RabidCicada

2012-Nov-28 21:08 UTC

head link

Re: 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@gmail.com>
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@vanderbilt.edu> 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@lists.xen.org [xen-users-bounces@lists.xen.org]
>> on behalf of Alexandre Kouznetsov [alk@ondore.com]
>> Sent: Wednesday, November 28, 2012 2:41 PM
>> To: xen-users@lists.xen.org
>> 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@lists.xen.org
>> http://lists.xen.org/xen-users
>>
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> 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@lists.xen.org
http://lists.xen.org/xen-users

Tapdiya, Ashish

2012-Nov-28 21:24 UTC

head link

Re: 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@gmail.com]
Sent: Wednesday, November 28, 2012 3:08 PM
To: Tapdiya, Ashish
Cc: Alexandre Kouznetsov; xen-users@lists.xen.org
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@gmail.com<mailto:rabidcicada@gmail.com>> 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@vanderbilt.edu<mailto:ashish.tapdiya@vanderbilt.edu>>
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@lists.xen.org<mailto:xen-users-bounces@lists.xen.org>
[xen-users-bounces@lists.xen.org<mailto:xen-users-bounces@lists.xen.org>]
on behalf of Alexandre Kouznetsov [alk@ondore.com<mailto:alk@ondore.com>]
Sent: Wednesday, November 28, 2012 2:41 PM
To: xen-users@lists.xen.org<mailto:xen-users@lists.xen.org>
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@lists.xen.org<mailto:Xen-users@lists.xen.org>
http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org<mailto:Xen-users@lists.xen.org>
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@lists.xen.org
http://lists.xen.org/xen-users

Alexandre Kouznetsov

2012-Nov-28 22:39 UTC

head link

Re: how to enable dom0 and domu share same physical network...

Hello.

El 28/11/12 15:08, RabidCicada escribió:> Or you let the bridge-Utils do that.Do you mean Xen''s network scripts? They are supposed to manage that,
but
have proven to do a not so great job. Mainly because of 
cross-distribution issues, as far as I know.

The general recommendation is to create the needed bridges by your 
distribution''s means, and then tell Xen which bridge to use in what 
case. Very stable, very predictable, very flexible.

This threads might help to figure out how to set up the bridging networks:
http://lists.xen.org/archives/html/xen-users/2012-10/msg00071.html
http://lists.xen.org/archives/html/xen-users/2012-09/msg00164.html

For reference about Xen''s networking model, I would recommend
Xen''s wiki:
http://wiki.xensource.com/xenwiki/XenNetworking (nicer pictures)
http://wiki.xen.org/wiki/Xen_Networking (more recent)
> 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.I can believe that. That is one fo the reasons for a recommendation to 
manage bridges somehow else, no via Xen''s scripts.

In any case, definitely it''s good idea to reboot your system as part of
your normal pre-production tests, in order to make sure whatever 
configuration you have made is persistent.

While doing tests, the bridging setup is perfectly manageable on the 
fly. Sometimes, it VLANs and some buggy switch (hello, Trendnet) are 
involved, it''s good idea to reset the network port.

Greetings.

-- 
Alexandre Kouznetsov

Simon Hobson

2012-Nov-28 22:45 UTC

head link

Re: how to enable dom0 and domu share same physical network...

Please learn how to bottom post and trim unnecessary quoted material.


Tapdiya, Ashish wrote:
>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.
You should leave netword-script unset and use the OS tools to setup 
the bridge. The old network-scripts are deprecated and date from a 
time when the various distros didn''t the tools. Now most ditros have 
much easier to use tools for setting up this sort of things - as 
posted earlier, it''s trivial to setup in Debian via 
/etc/network/interfaces.

Create a bridge, attached your eth0 NIC to it, and specify that 
bridge in your VIF definitions - and all the machines will be on the 
same network.
-- 
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.

Ian Campbell

2012-Nov-29 07:58 UTC

head link

Re: how to enable dom0 and domu share same physical network...

On Wed, 2012-11-28 at 18:39 +0000, Tapdiya, Ashish wrote:
> if dom-u creation config file vif entry is as follows,
> vif = [''ip=192.168.1.200''] 
This is used to create the appropriate rules in dom0 to allow traffic to
flow (e.g. if you have a firewall in dom0, or are doing NAT or routed
networking) but doesn''t actually, AFAIK, cause anything to be
configured
within the guest.

So as well as sorting out your dom0 bridging setup etc then you also
need to configure the .200 IP address within your guest (i.e. in the
guest''s /etc/network/interfaces or equivalent).

For the host side you might find
http://wiki.xen.org/wiki/Network_Configuration_Examples_%28Xen_4.1%2B%29
useful.

Ian.

Reasonably Related Threads

Search for more reasonably related threads

Xen users - Nov 2012 - how to enable dom0 and domu share same physical network...

how to enable dom0 and domu share same physical network...

Re: how to enable dom0 and domu share same physical network...

Re: how to enable dom0 and domu share same physical network...

Re: how to enable dom0 and domu share same physical network...

Re: how to enable dom0 and domu share same physical network...

Re: how to enable dom0 and domu share same physical network...

Re: how to enable dom0 and domu share same physical network...

Re: how to enable dom0 and domu share same physical network...

Re: how to enable dom0 and domu share same physical network...

Re: how to enable dom0 and domu share same physical network...

Re: how to enable dom0 and domu share same physical network...

Re: how to enable dom0 and domu share same physical network...

Re: how to enable dom0 and domu share same physical network...

Reasonably Related Threads