Cordialement,
There's a very high chance this is the same issue as described in
#596635. I'm just about to add a patch for this to SVN (which will
become 2.6.32-24).
On Thu, 2010-09-23 at 20:00 +0200, Guillaume Seigneuret wrote:
> Package: linux-image-2.6.32-5-xen-amd64
> Version: 2.6.32-23
>
> domU's randomly loose network, not at the same time. The only solution for the network to comes back is to reboot the virtual machine.
> Distrib version : Debian squeeze
> # dpkg -l | grep xen
> ii libxenstore3.0 3.4.3~rc3-1 Xenstore communications library for Xen
> ii linux-image-2.6.32-5-xen-amd64 2.6.32-23 Linux 2.6.32 for 64-bit PCs, Xen dom0 suppor
> ii xen-hypervisor-4.0-amd64 4.0.1~rc5-1 The Xen Hypervisor on AMD64
> ii xen-linux-system-2.6.32-5-xen-amd64 2.6.32-23 Xen system with Linux 2.6.32 on 64-bit PCs (
> ii xen-qemu-dm-4.0 4.0.0-5 Xen Qemu Device Model virtual machine hardwa
> ii xen-utils-4.0 4.0.1~rc5-1 XEN administrative tools
> ii xen-utils-common 4.0.0-1 XEN administrative tools - common files
> ii xenstore-utils 4.0.1-1 Xenstore utilities for Xen
> # dpkg -l | grep udev
> ii libudev0 160-1 libudev shared library
> ii udev 160-1 /dev/ and hotplug management daemon
> A fixed memory amount has been applied to the dom0 (dom0_mem=768M lowmem_emergency_pool=16M)
> The offload checksum has been disabled on each domU and dom0. (post-up ethtool -K eth0 tx off)
> DomU's are using the same kernel/modules as dom0.
> The bug has been reproduced on two servers.
> Cordialement,
> Guillaume Seigneuret
>
>
>
>
>
> Network and System Security Architect
> Web : http://www.omegacube.fr
> Address :
> Hôtel Technologique - BP 100
> Technopôle de Château Gombert
> 13382 Marseille Cedex 13
>
--
Ian Campbell
BOFH excuse #22:
monitor resolution too high