|
|
|
|
|
|
|
|
|
|
xen-users
RE [Xen-users] domU network has sleeping sickness
We had exactly the same problem, but
with only one domU (among about 75 other located on 15 dom0s), two months
ago.
We done a quick and dirty fix : a croned
ping every five minutes on the domU. Since that, we have no more user complains
(this domU is heavily used).
I know it is not a real solution, it
just work for us.
Alain.
xen-users-bounces@xxxxxxxxxxxxxxxxxxx a écrit sur
03/03/2008 16:49:29 :
> Hi all,
>
> I have a strange network problem with some domU's on three XEN-Hosts.
> They are loosing their network connectivity. I do bridged networking.
> * It happens randomly and could happen right after bootup
of the domU
> or anytime later.
> * The domU is not reachable from another host on the
LAN.
> * The domU is always reachable from the dom0 (ssh, ping).
> * I can 'repair' the connection when attaching to the
console and
> ping out from the domU. First nothings happens, then the machine gets
> back their network. (And thats also my momentary workaround, pinging
all
> the time from the console)
> * Pinging from another host at the same time helps too.
> * It could be that I can ping continously from one host
and another
> hosts gets only every 10th packet or so back.
> * The interfaces could come back from their sleep by
itself.
> * When the networks has fallen asleep, ssh on the domU
from another
> host hangs, it does not come back with "no route to host"
or something.
>
> I'm suspicious about the network controllers, they are the same on
all
> hosts: "Intel Corporation 80003ES2LAN Gigabit Ethernet Controller
> (Copper)"(lspci) some kind of "Intel® PRO/1000 EB Network
Connection
> with I/O Acceleration"(Intel website). I've tried the latest
e1000
> driver from Intel but it does'nt helped.
> I've checked all MAC Adresses, they are unique, also the IP Adresses.
>
> Any ideas are welcome :)
>
> -------------------------------------------------------------------------
> "xm info" from host1, openSUSE 10.2 (X86-64):
>
> release : 2.6.18.8-0.9-xen
> version : #1
SMP Sun Feb 10 22:48:05 UTC 2008
> machine : x86_64
> nr_cpus : 4
> nr_nodes : 1
> sockets_per_node : 2
> cores_per_socket : 2
> threads_per_core : 1
> cpu_mhz : 2327
> hw_caps :
> bfebfbff:20100800:00000000:00000140:0004e3bd:00000000:00000001
> total_memory : 32766
> free_memory : 21607
> max_free_memory : 21607
> max_para_memory : 21603
> max_hvm_memory : 21544
> xen_major : 3
> xen_minor : 0
> xen_extra : .3_11774-23
> xen_caps : xen-3.0-x86_64
> xen_pagesize : 4096
> platform_params : virt_start=0xffff800000000000
> xen_changeset : 11774
> cc_compiler : gcc version
4.1.2 20061115 (prerelease) (SUSE
> Linux)
> cc_compile_by : abuild
> cc_compile_domain : suse.de
> cc_compile_date : Thu Jan 10 21:22:54 UTC
2008
> xend_config_format : 2
> -------------------------------------------------------------------------
> "xm info" output on host2, openSUSE 10.3 (X86-64)
>
> release : 2.6.22.13-0.3-xen
> version : #1
SMP 2007/11/19 15:02:58 UTC
> machine : x86_64
> nr_cpus : 8
> nr_nodes : 1
> sockets_per_node : 2
> cores_per_socket : 4
> threads_per_core : 1
> cpu_mhz : 3000
> hw_caps :
> bfebfbff:20100800:00000000:00000140:0004e3bd:00000000:00000001
> total_memory : 16382
> free_memory : 591
> max_free_memory : 591
> max_para_memory : 587
> max_hvm_memory : 577
> xen_major : 3
> xen_minor : 1
> xen_extra : .0_15042-51
> xen_caps : xen-3.0-x86_64
xen-3.0-x86_32p
> xen_scheduler : credit
> xen_pagesize : 4096
> platform_params : virt_start=0xffff800000000000
> xen_changeset : 15042
> cc_compiler : gcc version
4.2.1 (SUSE Linux)
> cc_compile_by : abuild
> cc_compile_domain : suse.de
> cc_compile_date : Tue Sep 25 21:16:06 UTC
2007
> xend_config_format : 4
>
> --
> Marc Teichgraeber
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|