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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>


-- 
http://www.linuxpourtous.com


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
WARNING - OLD ARCHIVES

xen-users

Re: [Xen-users] dom0 networking disabled
