Hi,
Im using Xen testing from 14 Aug 2005.
I have 3 DomU machines.
Everything works most of the time, but occasionally (about once a
week), and not assocaited with any heavy usage, the network dies.
I can still ssh into the Dom0 machine, but that cannot see any of my
DomU machines.
I can connect via console to the DomU machines, and they cannot see
''out'' either. They are however running fine (albeit without
networking)
Any ideas how to start debugging this? has anything like this been
fixed in testing since 14 aug?
When its not wokring, I tried ifconfig and brctl, and to my untrained
eye it all looks fine.
How can I find out whats not working???
thanks
g
(When its working, IFConfig gives
eth0      Link encap:Ethernet  HWaddr 4C:00:10:21:4C:BE
          inet addr:192.168.10.220  Bcast:192.168.10.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:203828 errors:0 dropped:0 overruns:0 frame:0
          TX packets:146316 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:250628668 (239.0 MiB)  TX bytes:71201816 (67.9 MiB)
          Interrupt:21 Base address:0xa000
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3844 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3844 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:257268 (251.2 KiB)  TX bytes:257268 (251.2 KiB)
vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9620 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8712 errors:0 dropped:81 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2014768 (1.9 MiB)  TX bytes:3203884 (3.0 MiB)
vif2.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:59378 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32603 errors:0 dropped:66 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:86719420 (82.7 MiB)  TX bytes:2608655 (2.4 MiB)
vif3.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:266553 errors:0 dropped:0 overruns:0 frame:0
          TX packets:181363 errors:0 dropped:262 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:256948645 (245.0 MiB)  TX bytes:248877128 (237.3 MiB)
xen-br0   Link encap:Ethernet  HWaddr 4C:00:10:21:4C:BE
          inet addr:192.168.10.220  Bcast:192.168.10.255  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:258947 errors:0 dropped:0 overruns:0 frame:0
          TX packets:88567 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:335746440 (320.1 MiB)  TX bytes:70410814 (67.1 MiB)
and
brctl show gives
bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.4c0010214cbe       no              eth0
                                                        vif1.0
                                                        vif2.0
                                                        vif3.0
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I have now discovered that if I leave it for a while (less than half hour, not sure how much less), it recovers... I still have no idea how to start debugging this any clues? cheers g On 9/1/05, George Styles <ripnetuk@gmail.com> wrote:> Hi, > > Im using Xen testing from 14 Aug 2005. > I have 3 DomU machines. > Everything works most of the time, but occasionally (about once a > week), and not assocaited with any heavy usage, the network dies. > > I can still ssh into the Dom0 machine, but that cannot see any of my > DomU machines. > > I can connect via console to the DomU machines, and they cannot see > ''out'' either. They are however running fine (albeit without > networking) > > Any ideas how to start debugging this? has anything like this been > fixed in testing since 14 aug? > > When its not wokring, I tried ifconfig and brctl, and to my untrained > eye it all looks fine. > > How can I find out whats not working??? > > thanks > > g > > (When its working, IFConfig gives > > eth0 Link encap:Ethernet HWaddr 4C:00:10:21:4C:BE > inet addr:192.168.10.220 Bcast:192.168.10.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:203828 errors:0 dropped:0 overruns:0 frame:0 > TX packets:146316 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:250628668 (239.0 MiB) TX bytes:71201816 (67.9 MiB) > Interrupt:21 Base address:0xa000 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:3844 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3844 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:257268 (251.2 KiB) TX bytes:257268 (251.2 KiB) > > vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:9620 errors:0 dropped:0 overruns:0 frame:0 > TX packets:8712 errors:0 dropped:81 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2014768 (1.9 MiB) TX bytes:3203884 (3.0 MiB) > > vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:59378 errors:0 dropped:0 overruns:0 frame:0 > TX packets:32603 errors:0 dropped:66 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:86719420 (82.7 MiB) TX bytes:2608655 (2.4 MiB) > > vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:266553 errors:0 dropped:0 overruns:0 frame:0 > TX packets:181363 errors:0 dropped:262 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:256948645 (245.0 MiB) TX bytes:248877128 (237.3 MiB) > > xen-br0 Link encap:Ethernet HWaddr 4C:00:10:21:4C:BE > inet addr:192.168.10.220 Bcast:192.168.10.255 Mask:255.255.255.255 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:258947 errors:0 dropped:0 overruns:0 frame:0 > TX packets:88567 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:335746440 (320.1 MiB) TX bytes:70410814 (67.1 MiB) > > > > > and > > brctl show gives > > bridge name bridge id STP enabled interfaces > xen-br0 8000.4c0010214cbe no eth0 > vif1.0 > vif2.0 > vif3.0 >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I worked around this in the end by plugging 2 more physical network cards (£10) into my Xen box, and passing them through to the virtual machines... works a treat g On 9/2/05, George Styles <ripnetuk@gmail.com> wrote:> I have now discovered that if I leave it for a while (less than half > hour, not sure how much less), it recovers... > > I still have no idea how to start debugging this > > any clues? > > cheers > > g > > > On 9/1/05, George Styles <ripnetuk@gmail.com> wrote: > > Hi, > > > > Im using Xen testing from 14 Aug 2005. > > I have 3 DomU machines. > > Everything works most of the time, but occasionally (about once a > > week), and not assocaited with any heavy usage, the network dies. > > > > I can still ssh into the Dom0 machine, but that cannot see any of my > > DomU machines. > > > > I can connect via console to the DomU machines, and they cannot see > > ''out'' either. They are however running fine (albeit without > > networking) > > > > Any ideas how to start debugging this? has anything like this been > > fixed in testing since 14 aug? > > > > When its not wokring, I tried ifconfig and brctl, and to my untrained > > eye it all looks fine. > > > > How can I find out whats not working??? > > > > thanks > > > > g > > > > (When its working, IFConfig gives > > > > eth0 Link encap:Ethernet HWaddr 4C:00:10:21:4C:BE > > inet addr:192.168.10.220 Bcast:192.168.10.255 Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:203828 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:146316 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:250628668 (239.0 MiB) TX bytes:71201816 (67.9 MiB) > > Interrupt:21 Base address:0xa000 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:3844 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:3844 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:257268 (251.2 KiB) TX bytes:257268 (251.2 KiB) > > > > vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:9620 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:8712 errors:0 dropped:81 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:2014768 (1.9 MiB) TX bytes:3203884 (3.0 MiB) > > > > vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:59378 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:32603 errors:0 dropped:66 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:86719420 (82.7 MiB) TX bytes:2608655 (2.4 MiB) > > > > vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:266553 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:181363 errors:0 dropped:262 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:256948645 (245.0 MiB) TX bytes:248877128 (237.3 MiB) > > > > xen-br0 Link encap:Ethernet HWaddr 4C:00:10:21:4C:BE > > inet addr:192.168.10.220 Bcast:192.168.10.255 Mask:255.255.255.255 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:258947 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:88567 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:335746440 (320.1 MiB) TX bytes:70410814 (67.1 MiB) > > > > > > > > > > and > > > > brctl show gives > > > > bridge name bridge id STP enabled interfaces > > xen-br0 8000.4c0010214cbe no eth0 > > vif1.0 > > vif2.0 > > vif3.0 > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users