thr3ads.net - Xen users - Getting the bridged network running on Debian Squeeze with Xen 4.0.1 [Feb 2012]

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

Taschik, Daniel

2012-Feb-29 11:32 UTC

Getting the bridged network running on Debian Squeeze with Xen 4.0.1

Hi,

For a few days, I have been trying  to get a Xen 4.0.1 running on a fresh
installed Debian Squeeze 6.0.4. The host installation was fine at all. My
problem is, that I can''t get the network in the guest domU up and
running.

root@guest:~# ifconfig
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: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)

root@guest:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 39:fa:a9:88:a1:5c  
          inet addr:192.168.67.14  Bcast:192.168.67.255  Mask:255.255.255.0
          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:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:23 

root@guest:~# ifconfig eth0 up
SIOCSIFFLAGS: Cannot assign requested address


On the Host, my xend-configuration.sxp looks like this:

(vif-script vif-bridge)
(network-script ''network-bridge bridge=eth0'')
(dom0-min-mem 2048)
(enable-dom0-ballooning yes)
(total_available_memory 0)
(dom0-cpus 0)
(vncpasswd '''').
(xend-unix-server yes)

brctl show looks like this:

bridge name     bridge id               STP enabled     interfaces
eth0            8000.002590499320       no              peth0
                     				                                    vif1.0
My host dmesg log looks like this:

[ 1110.116485] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 1122.775781] device vif2.0 entered promiscuous mode
[ 1122.781559] eth0: port 2(vif2.0) entering forwarding state
[ 1122.851644] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 1122.853593] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please
use
[ 1122.853597] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module
option or
[ 1122.853600] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[ 1122.880067] physdev match: using --physdev-out in the OUTPUT, FORWARD and
POSTROUTING chains for non-bridged traffic is not supported anymore.
[ 1122.895044] physdev match: using --physdev-out in the OUTPUT, FORWARD and
POSTROUTING chains for non-bridged traffic is not supported anymore.
[ 1122.899251] physdev match: using --physdev-out in the OUTPUT, FORWARD and
POSTROUTING chains for non-bridged traffic is not supported anymore.
[ 1122.899258] physdev match: using --physdev-out in the OUTPUT, FORWARD and
POSTROUTING chains for non-bridged traffic is not supported anymore.
[ 1124.867103] blkback: ring-ref 770, event-channel 24, protocol 1 (x86_64-abi)
[ 1124.905556] blkback: ring-ref 771, event-channel 25, protocol 1 (x86_64-abi)


I created the guest with:

xen-create-image --force       --fs=ext4 --genpass=0 --install=1      
--memory=10G --password=test      --pygrub --size=20G --swap=4G     
--swap-dev=/dev/vg0/hostname.com-swap --vcpus=4       --dist=squeeze
--install-method=debootstrap       --broadcast=192.168.67.127
--netmask=255.255.255.128      --gateway=192.168.67.1 --ip=192.168.67.14
--mac=39:fa:a9:88:a1:5c      --nameserver=192.168.67.1 --hostname=hostname.com  
--lvm=vg0


I found out that when I disable handle_iptables() (line 94 in
/etc/xen/scripts/vif-bridge), the errors about the physdev-out disappear, but
even when this error is gone the problem is still the same. I tried using routed
networking, but the same problem here. I have been reinstalling two times but no
success at all. I hope you can help me to find out how to get the network in the
guest running.

Thanks in Advance!

Daniel

Simon Hobson

2012-Feb-29 12:04 UTC

head link

Re: Getting the bridged network running on Debian Squeeze with Xen 4.0.1

Taschik, Daniel wrote:
>On the Host, my xend-configuration.sxp looks like this:
>
>(vif-script vif-bridge)
>(network-script ''network-bridge bridge=eth0'')
OK, stop right there, comment out network-script. The Xen supplied 
scripts are not needed now and are to all intents deprecated in 
favour of Host OS facilities. Debian in particular make sit an 
absolute doddle to set up the bridge. All you need in 
/etc/network/interfaces is something like this :

auto eth0
iface eth0 inet static
   bridge_ports peth0
   address 192.168.x.y
   netmask 255.255.255.0
   gateway 192.168.x.z

And I''ve used /etc/udev/rules.d/70-persistent-net.rules to set the 
name of the physical interface to peth0. You don''t have to do this, 
you can use any name for the bridge, and any name for the physical 
NIC.

That *really* is all you need to create a bridge in Debian these days !

I''d try that first and see if it changes anything. If not then 
there''s something else going on. I''m running 4.0.1 &
Debian Squeeze
both at home and work, i686 and AMD64.

One other thing I''d try is not specifying any IP addressing when 
creating the guest. That ought to bypass any iptables stuff being set 
up in vif-script.

-- 
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.

Joseph Glanville

2012-Feb-29 12:10 UTC

head link

Re: Getting the bridged network running on Debian Squeeze with Xen 4.0.1

Take a look at the xen beginners guide on the wiki. It covers networking
and this problem in particular.
On Feb 29, 2012 11:05 PM, "Simon Hobson"
<linux@thehobsons.co.uk> wrote:
> Taschik, Daniel wrote:
>
>  On the Host, my xend-configuration.sxp looks like this:
>>
>> (vif-script vif-bridge)
>> (network-script ''network-bridge bridge=eth0'')
>>
>
> OK, stop right there, comment out network-script. The Xen supplied scripts
> are not needed now and are to all intents deprecated in favour of Host OS
> facilities. Debian in particular make sit an absolute doddle to set up the
> bridge. All you need in /etc/network/interfaces is something like this :
>
> auto eth0
> iface eth0 inet static
>  bridge_ports peth0
>  address 192.168.x.y
>  netmask 255.255.255.0
>  gateway 192.168.x.z
>
> And I''ve used /etc/udev/rules.d/70-**persistent-net.rules to set
the name
> of the physical interface to peth0. You don''t have to do this, you
can use
> any name for the bridge, and any name for the physical NIC.
>
> That *really* is all you need to create a bridge in Debian these days !
>
> I''d try that first and see if it changes anything. If not then
there''s
> something else going on. I''m running 4.0.1 & Debian Squeeze
both at home
> and work, i686 and AMD64.
>
>
> One other thing I''d try is not specifying any IP addressing when
creating
> the guest. That ought to bypass any iptables stuff being set up in
> vif-script.
>
> --
> Simon Hobson
>
> Visit
http://www.**magpiesnestpublishing.co.uk/<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.
>
> ______________________________**_________________
> 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

Taschik, Daniel

2012-Feb-29 12:32 UTC

head link

Re: Getting the bridged network running on Debian Squeeze with Xen 4.0.1

Thanks for your fast response.
On 29.02.2012, at 13:04, Simon Hobson wrote:
> Taschik, Daniel wrote:
> 
>> On the Host, my xend-configuration.sxp looks like this:
>> 
>> (vif-script vif-bridge)
>> (network-script ''network-bridge bridge=eth0'')
> 
> OK, stop right there, comment out network-script. The Xen supplied 
> scripts are not needed now and are to all intents deprecated in 
> favour of Host OS facilities. Debian in particular make sit an 
> absolute doddle to set up the bridge. All you need in 
> /etc/network/interfaces is something like this :
> 
> auto eth0
> iface eth0 inet static
>   bridge_ports peth0
>   address 192.168.x.y
>   netmask 255.255.255.0
>   gateway 192.168.x.z
> I commented (network-script ''network-bridge bridge=eth0'') and
m y interfaces now look like the following:

auto eth0
iface eth0 inet static
    	bridge_ports peth0
        address 192.168.67.12
        netmask 255.255.255.128
        network 192.168.67.0
        broadcast 192.168.67.127
        gateway 192.168.67.1
        # dns-* options are implemented by the resolvconf package, if installed
        dns-nameservers 192.168.67.1
        dns-search signavio.com

I also changed /etc/udev/rules.d/70-persistent-net.rules to:

# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:25:90:49:93:20", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="peth0"
# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:25:90:49:93:21", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:25:90:49:93:1f", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:25:90:49:93:1e", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

I also changed my guest vif config to:

vif         = [ ''bridge=xenbr0,mac=39:fa:a9:88:a1:5c'' ]

When I create the guest I still get the following error:

Configuring network interfaces...SIOCSIFFLAGS: Cannot assign requested address
SIOCSIFFLAGS: Cannot assign requested address
Failed to bring up eth0.

any other ideas?
> And I''ve used /etc/udev/rules.d/70-persistent-net.rules to set the
> name of the physical interface to peth0. You don''t have to do
this,
> you can use any name for the bridge, and any name for the physical 
> NIC.
> 
> That *really* is all you need to create a bridge in Debian these days !
> 
> I''d try that first and see if it changes anything. If not then 
> there''s something else going on. I''m running 4.0.1 &
Debian Squeeze
> both at home and work, i686 and AMD64.
> 
> 
> One other thing I''d try is not specifying any IP addressing when 
> creating the guest. That ought to bypass any iptables stuff being set 
> up in vif-script.
> 
> -- 
> 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.
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users

Simon Hobson

2012-Feb-29 13:51 UTC

head link

Re: Getting the bridged network running on Debian Squeeze with Xen 4.0.1

Taschik, Daniel wrote:
>I commented (network-script ''network-bridge bridge=eth0'')
and m y
>interfaces now look like the following:
>
>auto eth0
>iface eth0 inet static
...>I also changed my guest vif config to:
>
>vif         = [ ''bridge=xenbr0,mac=39:fa:a9:88:a1:5c'' ]
>
>When I create the guest I still get the following error:
xenbr0 is not the same as eth0, it''s trying to create a virtual 
interface attached to a non-existant bridge.

-- 
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.

Walter Robert Ditzler

2012-Feb-29 16:33 UTC

head link

Re: Getting the bridged network running on Debian Squeeze with Xen 4.0.1

hi all,

i had several problems getting that to work, my solutions look like:

aptitude install bridge-utils, net-tools, uuid, uuid-dev, tcpd

/etc/network/interfaces
***
auto lo
iface lo inet loopback

auto br0
iface br0 inet static
        address         x.x.x.x
        netmask         255.255.255.0
        network         x.x.x.x
        broadcast       x.x.x.x
        gateway         x.x.x.x
        bridge_ports    eth0
        bridge_stp      on
        bridge_maxwait  0
***

/etc/xen/*.cfg
***
vif             = [ ''bridge=br0,mac=00:16:3e:xx:xx:xx'' ] (vif
mac setup
works only with the beginning of 00:16:3e)
***

/etc/xen/xend-config.sxp
***
# -*- sh -*-
#(logfile /var/log/xen/xend.log)
#(loglevel DEBUG)
#(xsm_module_name dummy)
#(xen-api-server ((unix)))
#(xend-http-server no)
#(xend-unix-server no)
#(xend-tcp-xmlrpc-server no)
#(xend-unix-xmlrpc-server yes)
(xend-relocation-server yes)
#(xend-relocation-ssl-server no)
#(xend-udev-event-server no)
#(xend-unix-path /var/lib/xend/xend-socket)
#(xend-tcp-xmlrpc-server-address ''localhost'')
#(xend-tcp-xmlrpc-server-port 8006)
#(xend-tcp-xmlrpc-server-ssl-key-file  xmlrpc.key)
#(xend-tcp-xmlrpc-server-ssl-cert-file xmlrpc.crt)
#(xend-port 8000)
(xend-relocation-port 8002)
#(xend-relocation-ssl-port 8003)
# xend-relocation-ssl-server is set.
#(xend-relocation-server-ssl-key-file   xmlrpc.key)
#(xend-relocation-server-ssl-cert-file  xmlrpc.crt)
#(xend-relocation-ssl no)
#(xend-address '''')
#(xend-address localhost)
(xend-relocation-address '''')
(xend-relocation-hosts-allow '''')
#(xend-relocation-hosts-allow ''^localhost$
^localhost\\.localdomain$'')
#(console-limit 1024)
(network-script ''network-bridge antispoof=yes'')
(vif-script vif-bridge)
#(vif-script vif-route)
#(vif-script vif-nat)
(dom0-min-mem 256)
(enable-dom0-ballooning yes)
(total_available_memory 0)
(dom0-cpus 0)
#(enable-dump no)
#(external-migration-tool '''')
(vnc-listen ''0.0.0.0'')
(vncpasswd '''')
#(vnc-tls 1)
#(vnc-x509-cert-dir vnc)
#(vnc-x509-verify 1)
(keymap ''de-ch'')
#(resource-label-change-script '''')
#(qemu-dm-logrotate-count 10)
#(xend-domains-path /var/lib/xend/domains)
#(device-create-timeout 100)
#(pscsi-device-mask (''*''))
***

enjoy, walter

-----Original Message-----
From: xen-users-bounces@lists.xen.org
[mailto:xen-users-bounces@lists.xen.org] On Behalf Of Simon Hobson
Sent: Mittwoch, 29. Februar 2012 14:51
To: xen-users@lists.xen.org
Subject: Re: [Xen-users] Getting the bridged network running on Debian
Squeeze with Xen 4.0.1

Taschik, Daniel wrote:
>I commented (network-script ''network-bridge bridge=eth0'')
and m y
>interfaces now look like the following:
>
>auto eth0
>iface eth0 inet static
...>I also changed my guest vif config to:
>
>vif         = [ ''bridge=xenbr0,mac=39:fa:a9:88:a1:5c'' ]
>
>When I create the guest I still get the following error:
xenbr0 is not the same as eth0, it''s trying to create a virtual
interface
attached to a non-existant bridge.

--
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.

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

Xen users - Feb 2012 - Getting the bridged network running on Debian Squeeze with Xen 4.0.1

Getting the bridged network running on Debian Squeeze with Xen 4.0.1

Re: Getting the bridged network running on Debian Squeeze with Xen 4.0.1

Re: Getting the bridged network running on Debian Squeeze with Xen 4.0.1

Re: Getting the bridged network running on Debian Squeeze with Xen 4.0.1

Re: Getting the bridged network running on Debian Squeeze with Xen 4.0.1

Re: Getting the bridged network running on Debian Squeeze with Xen 4.0.1