thr3ads.net - Xen users - [Xen-users] dom0 networking disabled [Mar 2007]

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

kbrown@cm.utexas.edu

2007-Mar-15 23:57 UTC

[Xen-users] dom0 networking disabled

Hi folks, I''ve been trying to work out this situation for a few days
now
without much success and dug all over the archives for similar issues,
none of which seem to relate exactly.

I installed Debian Etch and the Xen (3.03) kernels / binaries on a Dell
server. It works fantastic with all the default configurations with one
strange flaw - as soon as the /etc/xen/scripts/network-bridge script runs,
dom0 loses all network connectivity. It is no longer possible to ping in
or out of the IP for the machine, and it throws no errors, just sits on a
blinking prompt.

I have 4 domU machines running on 4 different IPs and they all work
perfectly, with perfect connectivity. All the default configuration files
seem correct, and there are no firewall problems that I can see. Nothing
gets in or out of dom0, though, from anywhere. Running
''/etc/xen/scripts/network-bridge stop'' will return eth0 to its
former
state and everything starts working again.

So either I''m missing something very obvious, or something is very
wrong -
I''ve attached several readouts below, but let me know if any other info
would be helpful in solving this thing, its had us stumped and seems to be
the only thing keeping us from putting this box into production.

Thanks for any insight,

Kirk



***** XEND-CONFIG *****

(network-script network-bridge)

(vif-script vif-bridge)

(dom0-min-mem 196)

(dom0-cpus 0)



***** IFCONFIG AFTER NETWORK-BRIDGE *****
eth0      Link encap:Ethernet  HWaddr 00:18:8B:30:42:1A
          inet addr:146.6.135.253  Bcast:146.6.135.255  Mask:255.255.255.0
          inet6 addr: fe80::218:8bff:fe30:421a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:428106 errors:0 dropped:0 overruns:0 frame:0
          TX packets:954 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:90445670 (86.2 MiB)  TX bytes:51940 (50.7 KiB)

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:84 errors:0 dropped:0 overruns:0 frame:0
          TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7619 (7.4 KiB)  TX bytes:7619 (7.4 KiB)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1511699 errors:0 dropped:0 overruns:0 frame:0
          TX packets:357092 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:203990694 (194.5 MiB)  TX bytes:52150776 (49.7 MiB)
          Interrupt:16 Memory:f4000000-f4011100

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:954 errors:0 dropped:0 overruns:0 frame:0
          TX packets:428106 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:51940 (50.7 KiB)  TX bytes:90445670 (86.2 MiB)

vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:64258 errors:0 dropped:0 overruns:0 frame:0
          TX packets:562648 errors:0 dropped:115 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4142652 (3.9 MiB)  TX bytes:593022036 (565.5 MiB)

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 NOARP  MTU:1500  Metric:1
          RX packets:898 errors:0 dropped:0 overruns:0 frame:0
          TX packets:429185 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:108700 (106.1 KiB)  TX bytes:90550180 (86.3 MiB)

vif3.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:875 errors:0 dropped:0 overruns:0 frame:0
          TX packets:429167 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:107225 (104.7 KiB)  TX bytes:90548619 (86.3 MiB)

vif6.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:288128 errors:0 dropped:0 overruns:0 frame:0
          TX packets:724502 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:520109227 (496.0 MiB)  TX bytes:96161833 (91.7 MiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:424744 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:83800426 (79.9 MiB)  TX bytes:0 (0.0 b)




***** BRIDGE STATUS *****
bridge name	bridge id		STP enabled	interfaces
xenbr0		8000.feffffffffff	no
              vif0.0
							peth0
							vif1.0
							vif2.0
							vif3.0
							vif6.0



***** IP TABLES ON DOM0 *****
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           PHYSDEV match
--physdev-in vif1.0
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           PHYSDEV match
--physdev-in vif2.0
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           PHYSDEV match
--physdev-in vif3.0
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           PHYSDEV match
--physdev-in vif6.0

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination



***** WORKING DOMU CONFIG *****

kernel  = ''/boot/vmlinuz-2.6.18-4-xen-vserver-686''
ramdisk = ''/boot/initrd.img-2.6.18-4-xen-vserver-686''
memory  = ''256''
root    = ''/dev/sda1 ro''
disk    = [
''file:/xenservers/domains/xentest1/disk.img,sda1,w'',
''file:/xenservers/domains/xentest1/swap.img,sda2,w'' ]
name    = ''xentest1''
dhcp = ''dhcp''
vif  = [ ''mac=00:16:3E:44:43:99'' ]
on_poweroff = ''destroy''
on_reboot   = ''restart''
on_crash    = ''restart''



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

jez

2007-Mar-16 04:40 UTC

head link

Re: [Xen-users] dom0 networking disabled

On Thu, Mar 15, 2007 at 06:57:52PM -0500, kbrown@cm.utexas.edu
wrote:> 
> I installed Debian Etch and the Xen (3.03) kernels / binaries on a Dell
> server. It works fantastic with all the default configurations with one
> strange flaw - as soon as the /etc/xen/scripts/network-bridge script runs,
> dom0 loses all network connectivity. It is no longer possible to ping in
> or out of the IP for the machine, and it throws no errors, just sits on a
> blinking prompt.
> 
> I have 4 domU machines running on 4 different IPs and they all work
> perfectly, with perfect connectivity. All the default configuration files
> seem correct, and there are no firewall problems that I can see. Nothing
> gets in or out of dom0, though, from anywhere. Running
> ''/etc/xen/scripts/network-bridge stop'' will return eth0
to its former
> state and everything starts working again.
> 
> So either I''m missing something very obvious, or something is very
wrong -
> I''ve attached several readouts below, but let me know if any other
info
> would be helpful in solving this thing, its had us stumped and seems to be
> the only thing keeping us from putting this box into production.
> 
> Thanks for any insight,
> 
> Kirk
> 
Hi Kirk

I''ve looked through the information that you posted but I
can''t see
anything wrong with any of it. 

I reckon that you should bypass the network-bridge script and just use
your own bridge set up in /etc/network/interfaces. It''s insanely easy
to
set up, and if nothing else it might shed some more light on your
predicament. 

Here are the steps to take:

1. Change your /etc/network/interfaces to look like this. Make sure you 
   remove or comment out your previous eth0 entry:

    auto lo
    iface lo inet loopback

    auto xbr0
    iface xbr0 inet static
            address 146.6.135.253 
            netmask 255.255.255.0
            gateway 146.6.135.1    # <- put your gateway here
            bridge_ports eth0    

2. Change your xend-config.sxp to read:

    (network-script network-dummy)
    (vif-script vif-bridge)

3. Double check that the settings for xbr0 in /etc/network/interfaces 
   are exactly the same as eth0 previously had. Then when you are 
   satisfied, reboot.

If your computer resurfaces, and you can contact it over the network, 
then the bridge is up. If not, well eh ... you''re own your own mate!

Now when you start each of the DomU''s xen should put the vif*.0 
interfaces on your bridge. All in all, I think you''ll find that 
this is a much more transparent configuration.

Let us know how you get on.

jez

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

Tim Post

2007-Mar-16 05:36 UTC

head link

Re: [Xen-users] dom0 networking disabled

On Thu, 2007-03-15 at 18:57 -0500, kbrown@cm.utexas.edu
wrote:> I installed Debian Etch and the Xen (3.03) kernels / binaries on a Dell
> server. It works fantastic with all the default configurations with one
> strange flaw - as soon as the /etc/xen/scripts/network-bridge script runs,
> dom0 loses all network connectivity. It is no longer possible to ping in
> or out of the IP for the machine, and it throws no errors, just sits on a
> blinking prompt.
Another poster suggested taking network-bridge out of the equation which
I really also recommend on any Debian based system.

I also recommend adding :

bridge_fd 0
bridge_maxwait 0
bridge_helo 0

.. just prior to :

bridge_ports

To specifically tell the bridge that you don''t want a forward delay or
wait. I''m not sure what brctl''s defaults are so I always
specify it.
Probably also good practice to implicitly turn off stp, too.

However, this also means that your system will always start with a
promiscuous bridge as its primary network device. If this isn''t a full
time Xen machine with a Ft Knox ''ghost town'' dom-0, you may
want
network-bridge to work.

If you post the contents of your /etc/network/interfaces, I think the
list could help you quickly. There seems to be nothing wrong with
anything you posted so far (that I saw), so if there is an obvious issue
its going to be in interfaces.

Otherwise, its probably easier to just let Debian handle the bridging. 
Best,
--Tim

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

Franck

2007-Mar-16 06:21 UTC

head link

Re: [Xen-users] dom0 networking disabled

Hi,
> Hi folks, I''ve been trying to work out this situation for a few
days now
> without much success and dug all over the archives for similar issues,
> none of which seem to relate exactly.
>
> I installed Debian Etch and the Xen (3.03) kernels / binaries on a Dell
> server. It works fantastic with all the default configurations with one
> strange flaw - as soon as the /etc/xen/scripts/network-bridge script runs,
> dom0 loses all network connectivity. It is no longer possible to ping in
> or out of the IP for the machine, and it throws no errors, just sits on a
> blinking prompt.
i''ve exactly the same problem
http://lists.xensource.com/archives/html/xen-users/2007-03/msg00192.html

Franck
> I have 4 domU machines running on 4 different IPs and they all work
> perfectly, with perfect connectivity. All the default configuration files
> seem correct, and there are no firewall problems that I can see. Nothing
> gets in or out of dom0, though, from anywhere. Running
> ''/etc/xen/scripts/network-bridge stop'' will return eth0
to its former
> state and everything starts working again.
>
> So either I''m missing something very obvious, or something is very
wrong -
> I''ve attached several readouts below, but let me know if any other
info
> would be helpful in solving this thing, its had us stumped and seems to be
> the only thing keeping us from putting this box into production.
>
> Thanks for any insight,
>
> Kirk
>
>
>
> ***** XEND-CONFIG *****
>
> (network-script network-bridge)
>
> (vif-script vif-bridge)
>
> (dom0-min-mem 196)
>
> (dom0-cpus 0)
>
>
>
> ***** IFCONFIG AFTER NETWORK-BRIDGE *****
> eth0      Link encap:Ethernet  HWaddr 00:18:8B:30:42:1A
>           inet addr:146.6.135.253  Bcast:146.6.135.255  Mask:255.255.255.0
>           inet6 addr: fe80::218:8bff:fe30:421a/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:428106 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:954 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:90445670 (86.2 MiB)  TX bytes:51940 (50.7 KiB)
>
> 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:84 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:7619 (7.4 KiB)  TX bytes:7619 (7.4 KiB)
>
> peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:1511699 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:357092 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:203990694 (194.5 MiB)  TX bytes:52150776 (49.7 MiB)
>           Interrupt:16 Memory:f4000000-f4011100
>
> vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:954 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:428106 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:51940 (50.7 KiB)  TX bytes:90445670 (86.2 MiB)
>
> vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:64258 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:562648 errors:0 dropped:115 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:4142652 (3.9 MiB)  TX bytes:593022036 (565.5 MiB)
>
> 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 NOARP  MTU:1500  Metric:1
>           RX packets:898 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:429185 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:108700 (106.1 KiB)  TX bytes:90550180 (86.3 MiB)
>
> vif3.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:875 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:429167 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:107225 (104.7 KiB)  TX bytes:90548619 (86.3 MiB)
>
> vif6.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:288128 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:724502 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:520109227 (496.0 MiB)  TX bytes:96161833 (91.7 MiB)
>
> xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
>           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
>           RX packets:424744 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:83800426 (79.9 MiB)  TX bytes:0 (0.0 b)
>
>
>
>
> ***** BRIDGE STATUS *****
> bridge name	bridge id		STP enabled	interfaces
> xenbr0		8000.feffffffffff	no
>               vif0.0
> 							peth0
> 							vif1.0
> 							vif2.0
> 							vif3.0
> 							vif6.0
>
>
>
> ***** IP TABLES ON DOM0 *****
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
>
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
> ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           PHYSDEV match
> --physdev-in vif1.0
> ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           PHYSDEV match
> --physdev-in vif2.0
> ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           PHYSDEV match
> --physdev-in vif3.0
> ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           PHYSDEV match
> --physdev-in vif6.0
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
>
>
>
> ***** WORKING DOMU CONFIG *****
>
> kernel  = ''/boot/vmlinuz-2.6.18-4-xen-vserver-686''
> ramdisk = ''/boot/initrd.img-2.6.18-4-xen-vserver-686''
> memory  = ''256''
> root    = ''/dev/sda1 ro''
> disk    = [
''file:/xenservers/domains/xentest1/disk.img,sda1,w'',
> ''file:/xenservers/domains/xentest1/swap.img,sda2,w'' ]
> name    = ''xentest1''
> dhcp = ''dhcp''
> vif  = [ ''mac=00:16:3E:44:43:99'' ]
> on_poweroff = ''destroy''
> on_reboot   = ''restart''
> on_crash    = ''restart''
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

-- 
http://www.linuxpourtous.com


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

John Shen

2007-Mar-16 11:04 UTC

head link

Re: [Xen-users] dom0 networking disabled

jez,

I have had the exactly the same problem in Fedora Core 6, which uses
/etc/sysconfig/network-scripts/ifcfg-eth0 etc to configure nics.

when i copied your code to ifcfg-xbr0 and tried ifup xbr0, i got errors saying
command bridge_ports not found.

i would appreciate it very much for your help.

Message: 2
Date: Fri, 16 Mar 2007 05:40:13 +0100
From: jez <jez@jinsky.com>
Subject: Re: [Xen-users] dom0 networking disabled
To: xen-users@lists.xensource.com
Message-ID: <20070316044013.GG18608@almeida.jinsky.com>
Content-Type: text/plain; charset=us-ascii

On Thu, Mar 15, 2007 at 06:57:52PM -0500, kbrown@cm.utexas.edu
wrote:>
> I installed Debian Etch and the Xen (3.03) kernels / binaries on a Dell
> server. It works fantastic with all the default configurations with one
> strange flaw - as soon as the /etc/xen/scripts/network-bridge script runs,
> dom0 loses all network connectivity. It is no longer possible to ping in
> or out of the IP for the machine, and it throws no errors, just sits on a
> blinking prompt.
>
> I have 4 domU machines running on 4 different IPs and they all work
> perfectly, with perfect connectivity. All the default configuration files
> seem correct, and there are no firewall problems that I can see. Nothing
> gets in or out of dom0, though, from anywhere. Running
> ''/etc/xen/scripts/network-bridge stop'' will return eth0
to its former
> state and everything starts working again.
>
> So either I''m missing something very obvious, or something is very
wrong -
> I''ve attached several readouts below, but let me know if any other
info
> would be helpful in solving this thing, its had us stumped and seems to be
> the only thing keeping us from putting this box into production.
>
> Thanks for any insight,
>
> Kirk
>
Hi Kirk

I''ve looked through the information that you posted but I
can''t see
anything wrong with any of it.

I reckon that you should bypass the network-bridge script and just use
your own bridge set up in /etc/network/interfaces. It''s insanely easy
to
set up, and if nothing else it might shed some more light on your
predicament.

Here are the steps to take:

1. Change your /etc/network/interfaces to look like this. Make sure you
   remove or comment out your previous eth0 entry:

    auto lo
    iface lo inet loopback

    auto xbr0
    iface xbr0 inet static
            address 146.6.135.253
            netmask 255.255.255.0
            gateway 146.6.135.1    # <- put your gateway here
            bridge_ports eth0   

2. Change your xend-config.sxp to read:

    (network-script network-dummy)
    (vif-script vif-bridge)

3. Double check that the settings for xbr0 in /etc/network/interfaces
   are exactly the same as eth0 previously had. Then when you are
   satisfied, reboot.

If your computer resurfaces, and you can contact it over the network,
then the bridge is up. If not, well eh ... you''re own your own mate!

Now when you start each of the DomU''s xen should put the vif*.0
interfaces on your bridge. All in all, I think you''ll find that
this is a much more transparent configuration.

Let us know how you get on.

jez

John Shen 
System Coordinator, Online Information System
Student Affairs, University of California, Office of the President

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

Petersson, Mats

2007-Mar-16 11:18 UTC

head link

RE: [Xen-users] dom0 networking disabled

> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com 
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of John Shen
> Sent: 16 March 2007 11:05
> To: xen-users@lists.xensource.com
> Subject: Re: [Xen-users] dom0 networking disabled
> 
> jez,
>  
> I have had the exactly the same problem in Fedora Core 6, 
> which uses /etc/sysconfig/network-scripts/ifcfg-eth0 etc to 
> configure nics.
>  
> when i copied your code to ifcfg-xbr0 and tried ifup xbr0, i 
> got errors saying command bridge_ports not found.
You probably need to install "bridge utils" (a package called
"bridge-utils-<ver>.i386.rpm"). 

--
Mats>  
> i would appreciate it very much for your help.
>  
> Message: 2
> Date: Fri, 16 Mar 2007 05:40:13 +0100
> From: jez <jez@jinsky.com>
> Subject: Re: [Xen-users] dom0 networking disabled
> To: xen-users@lists.xensource.com
> Message-ID: <20070316044013.GG18608@almeida.jinsky.com>
> Content-Type: text/plain; charset=us-ascii
> 
> On Thu, Mar 15, 2007 at 06:57:52PM -0500, kbrown@cm.utexas.edu wrote:
> >
> > I installed Debian Etch and the Xen (3.03) kernels / 
> binaries on a Dell
> > server. It works fantastic with all the default 
> configurations with one
> > strange flaw - as soon as the 
> /etc/xen/scripts/network-bridge script runs,
> > dom0 loses all network connectivity. It is no longer 
> possible to ping in
> > or out of the IP for the machine, and it throws no errors, 
> just sits on a
> > blinking prompt.
> >
> > I have 4 domU machines running on 4 different IPs and they all work
> > perfectly, with perfect connectivity. All the default 
> configuration files
> > seem correct, and there are no firewall problems that I can 
> see. Nothing
> > gets in or out of dom0, though, from anywhere. Running
> > ''/etc/xen/scripts/network-bridge stop'' will return
eth0 to
> its former
> > state and everything starts working again.
> >
> > So either I''m missing something very obvious, or something 
> is very wrong -
> > I''ve attached several readouts below, but let me know if 
> any other info
> > would be helpful in solving this thing, its had us stumped 
> and seems to be
> > the only thing keeping us from putting this box into production.
> >
> > Thanks for any insight,
> >
> > Kirk
> >
> 
> Hi Kirk
> 
> I''ve looked through the information that you posted but I
can''t see
> anything wrong with any of it.
> 
> I reckon that you should bypass the network-bridge script and just use
> your own bridge set up in /etc/network/interfaces. It''s 
> insanely easy to
> set up, and if nothing else it might shed some more light on your
> predicament.
> 
> Here are the steps to take:
> 
> 1. Change your /etc/network/interfaces to look like this. 
> Make sure you
>    remove or comment out your previous eth0 entry:
> 
>     auto lo
>     iface lo inet loopback
>    
>     auto xbr0
>     iface xbr0 inet static
>             address 146.6.135.253
>             netmask 255.255.255.0
>             gateway 146.6.135.1    # <- put your gateway here
>             bridge_ports eth0   
> 
> 2. Change your xend-config.sxp to read:
> 
>     (network-script network-dummy)
>     (vif-script vif-bridge)
> 
> 3. Double check that the settings for xbr0 in /etc/network/interfaces
>    are exactly the same as eth0 previously had. Then when you are
>    satisfied, reboot.
> 
> If your computer resurfaces, and you can contact it over the network,
> then the bridge is up. If not, well eh ... you''re own your own
mate!
> 
> Now when you start each of the DomU''s xen should put the vif*.0
> interfaces on your bridge. All in all, I think you''ll find that
> this is a much more transparent configuration.
> 
> Let us know how you get on.
> 
> jez
> 
> John Shen 
> System Coordinator, Online Information System
> Student Affairs, University of California, Office of the President
>  
> 


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

John Shen

2007-Mar-16 11:28 UTC

head link

RE: [Xen-users] dom0 networking disabled

peter, 
 
thank you so much for your response
 
i have bridge-util installed:
 
bridge-utils-1.1-2
 
though i do not see any bridge_ports command. is that supposed to be a command
available if i have this package installed?
 
also, xen network-bridge script works fine and guest network works fine. so i am
still lost.
 
[jshen@eduout3-host ~]$ rpm -ql bridge-utils-1.1-2
/usr/sbin/brctl
/usr/share/doc/bridge-utils-1.1
/usr/share/doc/bridge-utils-1.1/AUTHORS
/usr/share/doc/bridge-utils-1.1/COPYING
/usr/share/doc/bridge-utils-1.1/FAQ
/usr/share/doc/bridge-utils-1.1/HOWTO
/usr/share/man/man8/brctl.8.gz

John Shen 
System Coordinator, Online Information System
Student Affairs, University of California, Office of the President

________________________________

From: Petersson, Mats [mailto:Mats.Petersson@amd.com]
Sent: Fri 3/16/2007 4:18 AM
To: John Shen; xen-users@lists.xensource.com
Subject: RE: [Xen-users] dom0 networking disabled


> -----Original Message----- 
> From: xen-users-bounces@lists.xensource.com 
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of John Shen 
> Sent: 16 March 2007 11:05 
> To: xen-users@lists.xensource.com 
> Subject: Re: [Xen-users] dom0 networking disabled 
> 
> jez, 
>  
> I have had the exactly the same problem in Fedora Core 6, 
> which uses /etc/sysconfig/network-scripts/ifcfg-eth0 etc to 
> configure nics. 
>  
> when i copied your code to ifcfg-xbr0 and tried ifup xbr0, i 
> got errors saying command bridge_ports not found. 
You probably need to install "bridge utils" (a package called
"bridge-utils-<ver>.i386.rpm").

-- 
Mats >  
> i would appreciate it very much for your help. 
>  
> Message: 2 
> Date: Fri, 16 Mar 2007 05:40:13 +0100 
> From: jez <jez@jinsky.com> 
> Subject: Re: [Xen-users] dom0 networking disabled 
> To: xen-users@lists.xensource.com 
> Message-ID: <20070316044013.GG18608@almeida.jinsky.com> 
> Content-Type: text/plain; charset=us-ascii 
> 
> On Thu, Mar 15, 2007 at 06:57:52PM -0500, kbrown@cm.utexas.edu wrote: 
> > 
> > I installed Debian Etch and the Xen (3.03) kernels / 
> binaries on a Dell 
> > server. It works fantastic with all the default 
> configurations with one 
> > strange flaw - as soon as the 
> /etc/xen/scripts/network-bridge script runs, 
> > dom0 loses all network connectivity. It is no longer 
> possible to ping in 
> > or out of the IP for the machine, and it throws no errors, 
> just sits on a 
> > blinking prompt. 
> > 
> > I have 4 domU machines running on 4 different IPs and they all work 
> > perfectly, with perfect connectivity. All the default 
> configuration files 
> > seem correct, and there are no firewall problems that I can 
> see. Nothing 
> > gets in or out of dom0, though, from anywhere. Running 
> > ''/etc/xen/scripts/network-bridge stop'' will return
eth0 to
> its former 
> > state and everything starts working again. 
> > 
> > So either I''m missing something very obvious, or something 
> is very wrong - 
> > I''ve attached several readouts below, but let me know if 
> any other info 
> > would be helpful in solving this thing, its had us stumped 
> and seems to be 
> > the only thing keeping us from putting this box into production. 
> > 
> > Thanks for any insight, 
> > 
> > Kirk 
> > 
> 
> Hi Kirk 
> 
> I''ve looked through the information that you posted but I
can''t see
> anything wrong with any of it. 
> 
> I reckon that you should bypass the network-bridge script and just use 
> your own bridge set up in /etc/network/interfaces. It''s 
> insanely easy to 
> set up, and if nothing else it might shed some more light on your 
> predicament. 
> 
> Here are the steps to take: 
> 
> 1. Change your /etc/network/interfaces to look like this. 
> Make sure you 
>    remove or comment out your previous eth0 entry: 
> 
>     auto lo 
>     iface lo inet loopback 
>    
>     auto xbr0 
>     iface xbr0 inet static 
>             address 146.6.135.253 
>             netmask 255.255.255.0 
>             gateway 146.6.135.1    # <- put your gateway here 
>             bridge_ports eth0   
> 
> 2. Change your xend-config.sxp to read: 
> 
>     (network-script network-dummy) 
>     (vif-script vif-bridge) 
> 
> 3. Double check that the settings for xbr0 in /etc/network/interfaces 
>    are exactly the same as eth0 previously had. Then when you are 
>    satisfied, reboot. 
> 
> If your computer resurfaces, and you can contact it over the network, 
> then the bridge is up. If not, well eh ... you''re own your own
mate!
> 
> Now when you start each of the DomU''s xen should put the vif*.0 
> interfaces on your bridge. All in all, I think you''ll find that 
> this is a much more transparent configuration. 
> 
> Let us know how you get on. 
> 
> jez 
> 
> John Shen 
> System Coordinator, Online Information System 
> Student Affairs, University of California, Office of the President 
>  
> 

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

Kirk Brown

2007-Mar-16 12:02 UTC

head link

Re: [Xen-users] dom0 networking disabled

Hi jez, thanks for the advice - it worked perfectly. To clarify for others
having the same problem - I was using the xen bridge script which would
kill the networking for Dom0, but work with the DomU''s. The fix was to
*not* use xen''s bridging.

My original /etc/network/interfaces looked like this:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address XXX.XXX.XXX.XXX
        netmask 255.255.255.0
        gateway XXX.XXX.XXX.XXX

and in the xend-config, I had:
(network-script network-bridge)


The fix was to set up the bridge directly in /etc/network/interfaces by
changing eth0 to:

auto xenbr0
iface xenbr0 inet static
        address XXX.XXX.XXX.XXX
        netmask 255.255.255.0
        gateway XXX.XXX.XXX.XXX
        bridge_ports eth0

and use the network-dummy in xend-config:
(network-script network-dummy)

Reboot and everything comes up OK.

Thanks again!

K
> Hi Kirk
>
> I''ve looked through the information that you posted but I
can''t see
> anything wrong with any of it.
>
> I reckon that you should bypass the network-bridge script and just use
> your own bridge set up in /etc/network/interfaces. It''s insanely
easy to
> set up, and if nothing else it might shed some more light on your
> predicament.
>
> Here are the steps to take:
>
> 1. Change your /etc/network/interfaces to look like this. Make sure you
>    remove or comment out your previous eth0 entry:
>
>     auto lo
>     iface lo inet loopback
>
>     auto xbr0
>     iface xbr0 inet static
>             address 146.6.135.253
>             netmask 255.255.255.0
>             gateway 146.6.135.1    # <- put your gateway here
>             bridge_ports eth0
>
> 2. Change your xend-config.sxp to read:
>
>     (network-script network-dummy)
>     (vif-script vif-bridge)
>
> 3. Double check that the settings for xbr0 in /etc/network/interfaces
>    are exactly the same as eth0 previously had. Then when you are
>    satisfied, reboot.
>
> If your computer resurfaces, and you can contact it over the network,
> then the bridge is up. If not, well eh ... you''re own your own
mate!
>
> Now when you start each of the DomU''s xen should put the vif*.0
> interfaces on your bridge. All in all, I think you''ll find that
> this is a much more transparent configuration.
>
> Let us know how you get on.
>
> jez
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>


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

jez

2007-Mar-16 17:47 UTC

head link

Re: [Xen-users] dom0 networking disabled

On Fri, Mar 16, 2007 at 04:28:55AM -0700, John Shen
wrote:> peter, 
>  
> thank you so much for your response
>  
> i have bridge-util installed:
>  
> bridge-utils-1.1-2
>  
> though i do not see any bridge_ports command. is that supposed to be a
command available if i have this package installed?
>  
> also, xen network-bridge script works fine and guest network works fine. so
i am still lost.
>  
Sorry John, my fault, I should have made it clear that I was outlining a 
Debian solution. 

I''ve just done some testing with a FC5 box and I think the following
should work for you.

Assuming your original ifcfg-eth0 looks something like:

    # Initial ifcfg-eth0
    DEVICE=eth0
    BOOTPROTO=none
    HWADDR=00:11:43:66:1C:1A
    IPADDR=10.0.0.1
    NETMASK=255.255.255.0
    ONBOOT=yes

You now create a new config file called ifcfg-xbr0 and transfer accross
the ip address and netmask from your original ifcfg-eth0. The end 
result should be the following two files:

/etc/sysconfig/network-scripts/ifcfg-xbr0:

    # ifcfg-xbr0
    DEVICE=xbr0
    TYPE=Bridge
    BOOTPROTO=none
    IPADDR=10.0.0.1
    NETMASK=255.255.255.0
    ONBOOT=yes

/etc/sysconfig/network-scripts/ifcfg-eth0:

    # New ifcfg-eth0
    DEVICE=eth0
    BOOTPROTO=none
    HWADDR=00:11:43:66:1C:1A
    ONBOOT=yes
    BRIDGE=xbr0

Note that I''ve added a new BRIDGE setting to the ifcfg-eth0 file.

The ifcfg-xbr0 file I''ve just shown is as simple as it gets. You can
add
other parameters such as timeouts, etc. Take a look at the ifup-eth
script if you''re curious.

On a different topic, if FC6 doesn''t have a network-dummy script, you
can
create one with:

    $ cat <<EOF > /etc/xen/scripts/network-dummy
    #!/bin/bash

    exit 0
    EOF
    $ chmod +x /etc/xen/scripts/network-dummy

Then change your xend-config.sxp to read:
    (network-script network-dummy)
    (vif-script vif-bridge)

Let us know if this works for you.

jez

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

jez

2007-Mar-16 18:49 UTC

head link

Re: [Xen-users] dom0 networking disabled

On Fri, Mar 16, 2007 at 07:02:27AM -0500, Kirk Brown
wrote:> Hi jez, thanks for the advice - it worked perfectly. To clarify for others
> having the same problem - I was using the xen bridge script which would
> kill the networking for Dom0, but work with the DomU''s. The fix
was to
> *not* use xen''s bridging.
> 
> My original /etc/network/interfaces looked like this:
> 
> auto lo
> iface lo inet loopback
> 
> auto eth0
> iface eth0 inet static
>         address XXX.XXX.XXX.XXX
>         netmask 255.255.255.0
>         gateway XXX.XXX.XXX.XXX
> 
> and in the xend-config, I had:
> (network-script network-bridge)
> 
> 
> The fix was to set up the bridge directly in /etc/network/interfaces by
> changing eth0 to:
> 
> auto xenbr0
> iface xenbr0 inet static
>         address XXX.XXX.XXX.XXX
>         netmask 255.255.255.0
>         gateway XXX.XXX.XXX.XXX
>         bridge_ports eth0
> 
> and use the network-dummy in xend-config:
> (network-script network-dummy)
> 
> Reboot and everything comes up OK.
> 
Excellent!

Just wanted to add that Tim Post makes some good suggestions elsewhere
on this thread about other parameters you might want to add to your 
bridge configuration. There''s a short explaination of each of these,
and a few others, in /usr/share/doc/bridge-utils/README.Debian.gz.

jez

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

Greg Saunders

2007-Mar-17 10:58 UTC

head link

Re: [Xen-users] dom0 networking disabled

I think I have a similar situation to the one Kirk Brown had.

I''ve intalled Etch . . .

Linux 2.6.18-4-amd64 #1 SMP Wed Feb 21 14:29:38 UTC 2007 x86_64 GNU/Linux

.. . . and also the xen-linux-system-2.6.18-4-xen package and the 
bridge-utils package.   But I haven''t tried installing any domUs
because I
can''t even get an internet connection when I boot up using "Xen 
3.0.3-1-amd64 / Debian GNU/Linux, kernel 2.6.18-4-xen-amd64".  Assuming I 
should have internet connection when running the Xen kernel (like I do when 
I run the original Etch kernel), here''s what I''ve done:


I''ve changed my /etc/network/interfaces file from . . .

auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp

auto eth0

.. . . to . . .

auto lo
iface lo inet loopback

iface xenbr0 inet dhcp
bridge_ports eth0

auto xenbr0


Note that there are couple of differences there from what Kirk Brown had: 
I''m using DHCP; I had an "allow-hotplug eth0" line in my
original interfaces
file, which I don''t know if I should leave, remove, or maybe change to 
"allow-hotplug xenbr0".


My /etc/xen/xen-config.sxp file looks like this:


(network-script network-dummy)
(vif-script vif-bridge)
(dom0-min-mem 196)
(dom0-cpus 0)


The Kirk Browm message that started the thread I''m trying to continue
has a
section called "***** IFCONFIG AFTER NETWORK-BRIDGE *****".  I
don''t know
what "AFTER NETWORK-BRIDGE" means, but when I enter the command . . .

ifconfig -a

.. . . I get this:

eth1      Link encap:UNSPEC  HWaddr 
32-4F-C0-00-18-E2-1D-61-00-00-00-00-00-00-00-00
          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)

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:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1060 (1.0 KiB)  TX bytes:1060 (1.0 KiB)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  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)

xenbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:3888 (3.7 KiB)


The . . .

brctl show

.. . . command reveals:

bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.000000000000       no


I take it there''s something I''m missing, either to do with the
brctl command
or extra requirements to use DHCP, or "hotplug" . . . or did I not
dance
naked around the computer in quite the right way?


Hmmmmm.

_________________________________________________________________
Get Out Of The House - Ski, Skate & Sun 
http://local.live.com/?mkt=en-ca/?v=2&cid=A6D6BDB4586E357F!147


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

jez

2007-Mar-17 16:37 UTC

head link

Re: [Xen-users] dom0 networking disabled

Hi Greg

On Sat, Mar 17, 2007 at 06:58:33AM -0400, Greg Saunders
wrote:> I think I have a similar situation to the one Kirk Brown had.
> 
> I''ve intalled Etch . . .
> 
> Linux 2.6.18-4-amd64 #1 SMP Wed Feb 21 14:29:38 UTC 2007 x86_64 GNU/Linux
> 
Nice! I run the debian amd port in a few places - it rocks!
> .. . . and also the xen-linux-system-2.6.18-4-xen package and the 
> bridge-utils package.   But I haven''t tried installing any domUs
because I
> can''t even get an internet connection when I boot up using
"Xen
> 3.0.3-1-amd64 / Debian GNU/Linux, kernel 2.6.18-4-xen-amd64". 
Assuming I
> should have internet connection when running the Xen kernel (like I do when
> I run the original Etch kernel), here''s what I''ve done:
> 
> 
> I''ve changed my /etc/network/interfaces file from . . .
> 
> auto lo
> iface lo inet loopback
> 
> allow-hotplug eth0
> iface eth0 inet dhcp
> 
> auto eth0
> 
> .. . . to . . .
> 
> auto lo
> iface lo inet loopback
> 
> iface xenbr0 inet dhcp
> bridge_ports eth0
> 
> auto xenbr0
> 
> 
One possible problem might be that the dhcp has timed out before the bridge 
has entered full operation mode. I didn''t want to complicate things
when I
was outlining a solution to Kirk, but as Tim Post pointed out elsewhere
in this post, I probably should have added a few timeout settings. Can
you try the following:

    auto lo
    iface lo inet loopback
    
    auto xbr0
    iface xbr0 inet dhcp
        bridge_fd 0
        bridge_maxwait 0
        bridge_helo 0
        bridge_ports eth0

I''m not overly confident that this is the problem since the bridge is
unlikely to send out a dhcp request if it''s not yet operating. But
it''s
still worth a try.

Also, I''d use xbr0 or br0 for the name of your bridge. It''s
easier to
see problems where they occur because the xen scripts use the name xenbr0 
when they create a bridge. Actually, it just tripped me up when trying 
to troubleshoot your situation, and got me to thinking that you hadn''t 
rebooted, hadn''t edited xend-config.sxp properly, hadn''t ...
> Note that there are couple of differences there from what Kirk Brown had: 
> I''m using DHCP; I had an "allow-hotplug eth0" line in my
original
> interfaces file, which I don''t know if I should leave, remove, or
maybe
> change to "allow-hotplug xenbr0".
> 
Okay, well I believe that ''allow-hotplug'' is needed by laptops
that
use certain wireless cards, pcmcia cards, and such. However, if this 
is a laptop and eth0 is a wireless card, then you''ve probably got
bigger
problems to worry about. I''ve read in a few different places that
bridging
generally doesn''t work with wireless cards. See:
http://linux-net.osdl.org/index.php/Bridge#It_doesn.27t_work_with_my_Wireless_card.21

If eth0 is a PCI card, then just remove the allow-hotplug stuff. If
you''ve got a hotplug PCI system, you can always work out if/how to put
the allow-hotplug back in later.
> 
> My /etc/xen/xen-config.sxp file looks like this:
> 
> 
> (network-script network-dummy)
> (vif-script vif-bridge)
> (dom0-min-mem 196)
> (dom0-cpus 0)
> 
That looks fine. 
> 
> The Kirk Browm message that started the thread I''m trying to
continue has a
> section called "***** IFCONFIG AFTER NETWORK-BRIDGE *****".  I
don''t know
> what "AFTER NETWORK-BRIDGE" means, but when I enter the command .
. .
> 
Generally "after network bridge" would mean after the xend daemon has
been started. This starts when you boot up - it''s startup script is
/etc/init.d/xend. The configuration file xen-config.sxp is xend''s
config
file.
> ifconfig -a
> 
> .. . . I get this:
> 
> eth1      Link encap:UNSPEC  HWaddr 
> 32-4F-C0-00-18-E2-1D-61-00-00-00-00-00-00-00-00
>          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)
> 
> 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:18 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:1060 (1.0 KiB)  TX bytes:1060 (1.0 KiB)
> 
> sit0      Link encap:IPv6-in-IPv4
>          NOARP  MTU:1480  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)
> 
> xenbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
>          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:0 (0.0 b)  TX bytes:3888 (3.7 KiB)
>
This doesn''t look right for a couple of reasons. First, we are trying
to
add an interface called eth0 to our bridge, but there is no sign here 
that eth0 even exists on your system.

Second, what the hell is going on with the HWaddr for eth1. That''s not
an ethernet MAC at all. It should be of the form 00:11:43:66:16:1A not
32-4F-C0-00-18-E2-1D-61-00-00-00-00-00-00-00-00.
''encap:UNSPEC'', wtf?

I''m guessing eth1 this is a wireless card. But I''m more
worried that
there is no indication that eth0 exists. Even if eth0 is enslaved to a 
bridge, you should still see an entry for eth0, and it should be UP, 
but should not have an address. Eg:

eth0      Link encap:Ethernet  HWaddr 00:04:75:98:E5:49  
          inet6 addr: ...
	  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          ...
> The . . .
> 
> brctl show
> 
> .. . . command reveals:
> 
> bridge name     bridge id               STP enabled     interfaces
> xenbr0          8000.000000000000       no
> 
> 
> I take it there''s something I''m missing, either to do
with the brctl
> command or extra requirements to use DHCP, or "hotplug" . . . or
did I not
> dance naked around the computer in quite the right way?
> 
To summarize:
 . Explain what eth0 is and what eth1 is (wireless, PCI, etc)
 . Try again using the timeout settings in interfaces.
 . Also, do you have physical access to this machine or is it in a
   remote hosting center? If you''ve got physical access then we can
step
   through creating a bridge manually - not something you really want to 
   try when logged in remotely :-)


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

Greg Saunders

2007-Mar-17 18:09 UTC

head link

Re: [Xen-users] dom0 networking disabled

Jez, thanks for input.
>
>Okay, well I believe that ''allow-hotplug'' is needed by
laptops that
>use certain wireless cards, pcmcia cards, and such. However, if this
>is a laptop and eth0 is a wireless card, then you''ve probably got
bigger
>problems to worry about. I''ve read in a few different places that
bridging
>generally doesn''t work with wireless cards. See:
>http://linux-net.osdl.org/index.php/Bridge#It_doesn.27t_work_with_my_Wireless_card.21
>
>If eth0 is a PCI card, then just remove the allow-hotplug stuff. If
>you''ve got a hotplug PCI system, you can always work out if/how to
put
>the allow-hotplug back in later.
To be honest, I don''t know that eth0 is a PCI card, but I suspect it
is.  I
do know that the computer is a laptop (Dell Inspiron 6400 with Core 2 Duo, 
much like the one reviewed at 
http://www.reghardware.co.uk/2006/12/06/review_dell_inspiron_6400/), and I 
do know that eth0 is not a PCMCIA card - the computer doesn''t even have
a
PCMCIA slot.

>
>To summarize:
>  . Explain what eth0 is and what eth1 is (wireless, PCI, etc)
I am under impression that eth0 is my "not-wireless" network interface
card;
not to be confused with wlan0, my wireless network interface card, mention 
of which I had completely removed from /etc/network/interfaces.

As for what eth1 is - I hadn''t noticed it before and I had assumed it
was
something to do with the Xen installation.  Given that you''re asking, 
though, I wonder now if it''s something to do with another foray
I''ve
recently made into virtualisation: I have installed the Qemu and have had a 
virtual machine running on that.  (That experiment is over now, though, and 
I was going to remove Qemu.)
>  . Try again using the timeout settings in interfaces.
Done.  No difference.  After making /etc/network/interfaces look like this 
(note change from "xenbr0" to "xbr0" and lack of
"allow-hotplug") :

auto lo
iface lo inet loopback

iface xbr0 inet dhcp
    bridge_fd 0
    bridge_maxwait 0
    bridge_helo 0
    bridge_ports eth0

auto xbr0


I ran


/etc/init.d/networking restart


which returned:


Reconfiguring network interfaces...There is already a pid file 
/var/run/dhclient.xbr0.pid with pid 2404
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/xbr0/00:00:00:00:00:00
Sending on   LPF/xbr0/00:00:00:00:00:00
Sending on   Socket/fallback
eth0: ERROR while getting interface flags: No such device
interface eth0 does not exist!
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/xbr0/00:00:00:00:00:00
Sending on   LPF/xbr0/00:00:00:00:00:00
Sending on   Socket/fallback
DHCPDISCOVER on xbr0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on xbr0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on xbr0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on xbr0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on xbr0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.


And ifconfig -a returns


eth1      Link encap:UNSPEC  HWaddr 
32-4F-C0-00-18-E2-1D-61-00-00-00-00-00-00-00-00
          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)

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:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:760 (760.0 b)  TX bytes:760 (760.0 b)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  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)

xbr0      Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:3546 (3.4 KiB)


For comparison, it might tell you something to see that when I run my 
original Etch kernel and make my /etc/network/interfaces looks this:


auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

iface wlan0 inet dhcp
wireless-essid ThinAir

auto eth0

auto wlan0


The result of /etc/init.d/networking restart is


Reconfiguring network interfaces...There is already a pid file 
/var/run/dhclient.eth0.pid with pid 3188
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:15:c5:c9:f6:e3
Sending on   LPF/eth0/00:15:c5:c9:f6:e3
Sending on   Socket/fallback
DHCPRELEASE on eth0 to 192.168.0.1 port 67
There is already a pid file /var/run/dhclient.wlan0.pid with pid 2560
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:19:7d:12:f3:31
Sending on   LPF/wlan0/00:19:7d:12:f3:31
Sending on   Socket/fallback
DHCPRELEASE on wlan0 to 192.168.0.1 port 67
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:15:c5:c9:f6:e3
Sending on   LPF/eth0/00:15:c5:c9:f6:e3
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPOFFER from 192.168.0.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.102 -- renewal in 233563 seconds.
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/wlan0/00:19:7d:12:f3:31
Sending on   LPF/wlan0/00:19:7d:12:f3:31
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.0.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.201 -- renewal in 273397 seconds.
done.


So that ifconfig -a returns


eth0      Link encap:Ethernet  HWaddr 00:15:C5:C9:F6:E3
          inet addr:192.168.0.102  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::215:c5ff:fec9:f6e3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:72 errors:0 dropped:0 overruns:0 frame:0
          TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:18210 (17.7 KiB)  TX bytes:5002 (4.8 KiB)
          Interrupt:58

eth1      Link encap:UNSPEC  HWaddr 
32-4F-C0-00-18-E2-1D-61-00-00-00-00-00-00-00-00
          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)

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:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:760 (760.0 b)  TX bytes:760 (760.0 b)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  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)

wlan0     Link encap:Ethernet  HWaddr 00:19:7D:12:F3:31
          inet addr:192.168.0.201  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::219:7dff:fe12:f331/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:57 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:16492 (16.1 KiB)  TX bytes:3421 (3.3 KiB)
          Interrupt:169 Memory:efcfc000-efd00000

>  . Also, do you have physical access to this machine or is it in a
>    remote hosting center? If you''ve got physical access then we
can step
>    through creating a bridge manually - not something you really want to
>    try when logged in remotely :-)
I do have physical access to the machine.

_________________________________________________________________
RealLiveMoms: Share your experience with Real Live Moms just like you 
http://www.reallivemoms.ca/


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

jez

2007-Mar-17 20:25 UTC

head link

Re: [Xen-users] dom0 networking disabled

On Sat, Mar 17, 2007 at 02:09:24PM -0400, Greg Saunders
wrote:>
> >If eth0 is a PCI card, then just remove the allow-hotplug stuff. If
> >you''ve got a hotplug PCI system, you can always work out
if/how to put
> >the allow-hotplug back in later.
> 
> To be honest, I don''t know that eth0 is a PCI card, but I suspect
it is.  I
> do know that the computer is a laptop (Dell Inspiron 6400 with Core 2 Duo, 
> much like the one reviewed at 
> http://www.reghardware.co.uk/2006/12/06/review_dell_inspiron_6400/), and I 
> do know that eth0 is not a PCMCIA card - the computer doesn''t even
have a
> PCMCIA slot.
> 
That sounds about right. I''ve got an  inspiron here, there will always
be
an onboard nic on those things. I did a quick search on the oui part of
the MAC addreess below 00:15:C5 and I it appears to be registered to
Dell. 
> >
> >To summarize:
> > . Explain what eth0 is and what eth1 is (wireless, PCI, etc)
> 
> I am under impression that eth0 is my "not-wireless" network
interface
> card; not to be confused with wlan0, my wireless network interface card, 
> mention of which I had completely removed from /etc/network/interfaces.
> 
> As for what eth1 is - I hadn''t noticed it before and I had assumed
it was
> something to do with the Xen installation.  Given that you''re
asking,
> though, I wonder now if it''s something to do with another foray
I''ve
> recently made into virtualisation: I have installed the Qemu and have had a
> virtual machine running on that.  (That experiment is over now, though, and
> I was going to remove Qemu.)
> 
I''d be very surprised if it was related to qemu. I''m messing
around with
qemu and kvm at the moment and I don''t see anything like that.
Qemu''s
user mode networking stack would not be allowed to create interfaces
like that on the host, and if your using tuntap interfaces, these 
will look like normal ethernet interfaces. Anyway, the good news is that 
eth1 is there - and still strange looking - when you run etch with a 
non-xen kernel. It''s probably not something we need to worry about
here.
> > . Try again using the timeout settings in interfaces.
> 
> Done.  No difference.  After making /etc/network/interfaces look like this 
> (note change from "xenbr0" to "xbr0" and lack of
"allow-hotplug") :
> 
> auto lo
> iface lo inet loopback
> 
> iface xbr0 inet dhcp
>    bridge_fd 0
>    bridge_maxwait 0
>    bridge_helo 0
>    bridge_ports eth0
> 
> auto xbr0
>
That''s a pity!

<snip/>> And ifconfig -a returns
> 
> eth1      Link encap:UNSPEC  HWaddr 
> 32-4F-C0-00-18-E2-1D-61-00-00-00-00-00-00-00-00
>          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)
> 
<snip/>> 
> For comparison, it might tell you something to see that when I run my 
> original Etch kernel and make my /etc/network/interfaces looks this:
> 
<snip/>> So that ifconfig -a returns
> 
> eth0      Link encap:Ethernet  HWaddr 00:15:C5:C9:F6:E3
>          inet addr:192.168.0.102  Bcast:192.168.0.255  Mask:255.255.255.0
>          inet6 addr: fe80::215:c5ff:fec9:f6e3/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:72 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:18210 (17.7 KiB)  TX bytes:5002 (4.8 KiB)
>          Interrupt:58
> 
> eth1      Link encap:UNSPEC  HWaddr 
> 32-4F-C0-00-18-E2-1D-61-00-00-00-00-00-00-00-00
>          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)
> 
Thanks Greg, this comparison was very helpful. The problem here is
clearly that eth0 does not exist when you boot into xen. It''s not a
problem with bridging, or anything like that. If you were to use an
empty /etc/network/interfaces file and you were to prevent xend from
running at startup:

    # find /etc/rc*.d -name ''*xend''
    /etc/rc0.d/K21xend
    /etc/rc1.d/K21xend
    /etc/rc2.d/S20xend
    /etc/rc3.d/S20xend
    /etc/rc4.d/S20xend
    /etc/rc5.d/S20xend
    /etc/rc6.d/K21xend
    # find /etc/rc*.d -name ''*xend'' | rename s/S20/K80/
    # find /etc/rc*.d -name ''*xend''
    /etc/rc0.d/K21xend
    /etc/rc1.d/K21xend
    /etc/rc2.d/K80xend
    /etc/rc3.d/K80xend
    /etc/rc4.d/K80xend
    /etc/rc5.d/K80xend
    /etc/rc6.d/K21xend

And you rebooted. You would still not see eth0. You can try this if you
want (but remember to do a ''rename s/K80/S20/'' afterwards).

If you can get eth0 to exist under xen then all that bridging stuff will
fall into place. So how do you do that? Well, I recommend you try the
following. 

Boot into etch with the none-xen kernel running. Now collect all the
information you can about you network card:

   $ udevinfo -ap /sys/class/net/eth0/ > eth0.notes

You are particularly interested in what driver is running for eth0:

   $ udevinfo -ap /sys/class/net/eth0/ | grep -i driver
   DRIVER=="b44"
   DRIVER==""
   DRIVER==""


Also run ''lspci'' and collect the information you receive in
case you
need to search google.

Then boot back into xen and try to load the driver manually.

   $ modprobe b44

Check the output of udevinfo here as well, and check log files and just
generally try to work out what has happened to eth0.
> 
> > . Also, do you have physical access to this machine or is it in a
> >   remote hosting center? If you''ve got physical access then
we can step
> >   through creating a bridge manually - not something you really want
to
> >   try when logged in remotely :-)
> 
> I do have physical access to the machine.
>
Good, but unfortunatly I can''t step you through the manual creation 
of the bridge if eth0 does not exist. And if it did exist the bridge 
stuff would probably be working just fine anyway. Damn!

jez

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

Greg Saunders

2007-Mar-17 21:20 UTC

head link

Re: [Xen-users] dom0 networking disabled

Thanks again Jez,

I''ll have another go when next I get a chance, which should be next
week
some time.  This turning into an interesting project with mystery NIC 
appearances (eth1) and disappearances (eth0 under Xen).   Very intriguing.

_________________________________________________________________
Your Space. Your Friends. Your Stories. Share your world with Windows Live 
Spaces. http://spaces.live.com/?mkt=en-ca


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

jez

2007-Mar-17 22:52 UTC

head link

Re: [Xen-users] dom0 networking disabled

On Sat, Mar 17, 2007 at 05:20:48PM -0400, Greg Saunders
wrote:> Thanks again Jez,
> 
> I''ll have another go when next I get a chance, which should be
next week
> some time.  This turning into an interesting project with mystery NIC 
> appearances (eth1) and disappearances (eth0 under Xen).   Very intriguing.
> 
The Suspense is rife! Tag a note on the end if you manage to get it solved.


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

Possibly Parallel Threads

Search for more reasonably related threads

Xen users - Mar 2007 - dom0 networking disabled

[Xen-users] dom0 networking disabled

Re: [Xen-users] dom0 networking disabled

Re: [Xen-users] dom0 networking disabled

Re: [Xen-users] dom0 networking disabled

Re: [Xen-users] dom0 networking disabled

RE: [Xen-users] dom0 networking disabled

RE: [Xen-users] dom0 networking disabled

Re: [Xen-users] dom0 networking disabled

Re: [Xen-users] dom0 networking disabled

Re: [Xen-users] dom0 networking disabled

Re: [Xen-users] dom0 networking disabled

Re: [Xen-users] dom0 networking disabled

Re: [Xen-users] dom0 networking disabled

Re: [Xen-users] dom0 networking disabled

Re: [Xen-users] dom0 networking disabled

Re: [Xen-users] dom0 networking disabled

Possibly Parallel Threads