thr3ads.net - Xen users - [Xen-users] DomO network bridge [Jul 2010]

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

Hardeep Uppal

2010-Jul-15 20:40 UTC

[Xen-users] DomO network bridge

Hi,

I have xen3.3 running on debian 2.6.26-2-xen-686 domO kernel and couple of
domU kernel running Ubuntu9.04. I''m using xen-tools to create domU. The
domUs can ping each other but cannot ping anything else including dom0 or
any outside host. Dom0 cannot ping the domUs but is able to talk to other
host. I have been having problem getting the bridge between dom0 and domU.
The network bridge script throws the follow error when executed.

ettm@ettm:~$ sudo /etc/xen/scripts/network-bridge start
ifdown: interface eth0 not configured
ifdown: interface peth0 not configured
Error: either "dev" is duplicate, or "peth0" is a garbage.

I am not sure what the above error means. Is there another way to setup
bridging between domU and dom0 without using network-bridge? I would really
appreciate any help I can get.

Here are all the configure files for xen and domU.

domU.cfg:
kernel      = ''/boot/vmlinuz-2.6.26-2-xen-686''
ramdisk     = ''/boot/initrd.img-2.6.26-2-xen-686''
memory      = ''512''
root        = ''/dev/hda2 ro''
disk        = [
                 
''file:/home/xen/domains/UdomU1/swap.img,hda1,w'',
                 
''file:/home/xen/domains/UdomU1/root.img,hda2,w'',
                 
''file:/home/xen/domains/UdomU1/data.img,hda3,w'',
              ]
name        = ''domU''
dhcp        = ''dhcp''
vif         = [ ''mac=00:16:3E:1C:A6:B1'' ]
on_poweroff = ''destroy''
on_reboot   = ''restart''
on_crash    = ''restart''

xend-config.sxp:
(xend-relocation-server yes)
(xend-relocation-hosts-allow ''^localhost$
^localhost\\.localdomain$'')
(network-script network-bridge)
(vif-script vif-bridge)
(dom0-min-mem 196)
(enable-dom0-ballooning yes)
(dom0-cpus 0)
(vncpasswd '''')


dom0 network:

ettm@ettm:~$ brctl show
bridge name    bridge id        STP enabled    interfaces
eth0        8000.00256449d794    no                  peth0

vif2.0
pan0        8000.000000000000    no
tmpbridge        8000.000000000000    no

ettm@ettm:~$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:25:64:49:d7:94
          inet addr:128.208.3.15  Bcast:128.208.3.255  Mask:255.255.255.0
          inet6 addr: fe80::225:64ff:fe49:d794/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11162 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2837 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2222551 (2.2 MB)  TX bytes:792344 (792.3 KB)

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:40 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3642 (3.6 KB)  TX bytes:3642 (3.6 KB)

pan0      Link encap:Ethernet  HWaddr da:9c:e9:7d:20:fc
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

peth0     Link encap:Ethernet  HWaddr 00:25:64:49:d7:94
          inet addr:128.208.3.15  Bcast:128.208.3.255  Mask:255.255.255.0
          inet6 addr: fe80::225:64ff:fe49:d794/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:13855 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3022 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2665701 (2.6 MB)  TX bytes:820255 (820.2 KB)
          Interrupt:16

tmpbridge Link encap:Ethernet  HWaddr f6:57:32:c2:ac:84
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vif2.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:95 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7596 errors:0 dropped:54 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:4076 (4.0 KB)  TX bytes:731510 (731.5 KB)


domU network:

root@domU:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:3e:1c:a6:b1
          inet addr:10.0.3.26  Bcast:10.0.3.255  Mask:255.255.255.0
          inet6 addr: fe80::216:3eff:fe1c:a6b1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8073 errors:0 dropped:0 overruns:0 frame:0
          TX packets:95 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:772451 (772.4 KB)  TX bytes:5406 (5.4 KB)

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:27 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2592 (2.5 KB)  TX bytes:2592 (2.5 KB)


--Hardeep


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

Marco Nenciarini

2010-Jul-16 06:44 UTC

head link

Re: [Xen-users] DomO network bridge

On 15/07/2010 22:40, Hardeep Uppal wrote:> Hi,
> 
> I have xen3.3 running on debian 2.6.26-2-xen-686 domO kernel and couple of
> domU kernel running Ubuntu9.04. I''m using xen-tools to create
domU. The
> domUs can ping each other but cannot ping anything else including dom0 or
> any outside host. Dom0 cannot ping the domUs but is able to talk to other
> host. I have been having problem getting the bridge between dom0 and domU.
> The network bridge script throws the follow error when executed.
> 
> ettm@ettm:~$ sudo /etc/xen/scripts/network-bridge start
> ifdown: interface eth0 not configured
> ifdown: interface peth0 not configured
> Error: either "dev" is duplicate, or "peth0" is a
garbage.
> 
> I am not sure what the above error means. Is there another way to setup
> bridging between domU and dom0 without using network-bridge? I would really
> appreciate any help I can get.
Try to follow this:

http://lists.xensource.com/archives/html/xen-users/2010-07/msg00275.html

just skip the bond0 stanza.

Here a resume  of resulting /etc/network/interfaces without comments
----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<---

auto lo
iface lo inet loopback

auto br0
iface br0 inet static
        address 192.168.1.10
        netmask 255.255.255.0
        gateway 192.168.1.1
        bridge_ports eth0
        bridge_maxwait 0

---->8---->8---->8---->8---->8---->8---->8---->8---->8---->8---->8---

That''s all.

Kind regards,
Marco

-- 
---------------------------------------------------------------------
|    Marco Nenciarini    | Debian/GNU Linux Developer - Plug Member |
| mnencia@prato.linux.it | http://www.prato.linux.it/~mnencia       |
---------------------------------------------------------------------
Key fingerprint = FED9 69C7 9E67 21F5 7D95  5270 6864 730D F095 E5E4




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

Xen users - Jul 2010 - DomO network bridge

[Xen-users] DomO network bridge

Re: [Xen-users] DomO network bridge