WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] M2N32, suse 10.3 and network problem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] M2N32, suse 10.3 and network problem
From: Chris Epicier <seuchato@xxxxxxxx>
Date: Mon, 14 Jan 2008 06:48:16 +0100 (CET)
Delivery-date: Sun, 13 Jan 2008 21:48:48 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.de; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=OjGNqNyt96VASVV8zYgVHX+bgvKItKUD74RAbCheMJH0CjZv9viqRwHhroXbW05bHVeHDvKya6mrunh+/idJjSq9dFoWZ0YrXGYvbPhPKaGbRUcyorbJAbNdXns7p1lGfn8CHhjnSmV9rIs8dkQiCVgEPiW1+5IIBmfHx0wpB1M=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi 

I have an Asus M2N32 WS Pro, 4G Ram, AthlonX264 4600+.
I Installed SuSE 10.3 (64bit) on Dom0, LVM on Raid 5.
All domU's boot off LVM, using same Suse 10.3. 
I have a firewall (fw) domU running shorewall and a
domU name-dhcp-server (nds). Somewhere in between 10
and 16 hours the network stalls. In dns, I can see
dhcp queries and offers, but these never make it to
the clients in the lan. if I try pinging the domU's I
just get no reply at all. If I shutdown and boot the
domU's again everything runs again.

I considered running "ethtool -K eth0 tx off" on one,
all domU's without success. First I had delegated one
of the on board nics (mcp55, forcedeth) from dom0 and
forwarded to domU fw. That gave some mm.c
errormessages. Thus I now have a pci USB contrioller
with attached NIC delegated from dom0 to domU fw. 

Here are the configs for fw
Linux fw 2.6.22.13-0.3-xen #1 SMP 2007/11/19 15:02:58
UTC x86_64 x86_64 x86_64 GNU/Linux
====================================================
name = "fw"
kernel = "/boot/vmlinuz-xen"
ramdisk = "/boot/initrd-xen"
memory = 128

vif = [ 'mac=aa:cc:00:00:00:C2, bridge=xenbr0' ]
disk = [ 'phy:system/fw,sda1,w' ]
root = "/dev/sda1 rw"
extra = "3 xencons=tty"
pci=[ '04:01.0','04:01.1','04:01.2','04:01.3' ]
====================================================
Here are the configs for nds
Linux nds 2.6.22.13-0.3-xen #1 SMP 2007/11/19 15:02:58
UTC x86_64 x86_64 x86_64 GNU/Linux
====================================================
name = "nds"
kernel = "/boot/vmlinuz-xen"
ramdisk = "/boot/initrd-xen"
memory = 128
vif = [ 'mac=aa:cc:00:00:00:C1, bridge=xenbr0' ]
disk = [ 'phy:system/nds,sda1,w' ]
root = "/dev/sda1 rw"
extra = "3 xencons=tty"
====================================================
uname -a of dom0
Linux caesar 2.6.22.13-0.3-xen #1 SMP 2007/11/19
15:02:58 UTC x86_64 x86_64 x86_64 GNU/Linux
/boot/grub/menu.lst
====================================================
...
title XEN -- openSUSE 10.3 - 2.6.22.13-0.3
    root (hd0,0)
    kernel /xen.gz dom0_mem=256M clocksource=jiffies
    module /vmlinuz-2.6.22.13-0.3-xen
root=/dev/system/Dom0 vga=0x31a splash=silent showopts
    module /initrd-2.6.22.13-0.3-xen
====================================================
/etc/init.d/boot.local
====================================================
modprobe pciback
hide='(09:00.0)(04:01.0)(04:01.1)(04:01.2)(04:01.3)'

# 09:00.0 VGA compatible controller: nVidia
Corporation GeForce 8600 GT (rev a1)

# hide 8600 GT so it can be used in domU (not used at
the moment)
echo -n 0000:09:00.0 >
/sys/bus/pci/drivers/pciback/permissive


# 04:01.0 USB Controller: ALi Corporation USB 1.1
Controller (rev 03)
# 04:01.1 USB Controller: ALi Corporation USB 1.1
Controller (rev 03)
# 04:01.2 USB Controller: ALi Corporation USB 1.1
Controller (rev 03)
# 04:01.3 USB Controller: ALi Corporation USB 2.0
Controller (rev 01)
echo -n 0000:04:01.0 > 
/sys/bus/pci/drivers/ohci_hcd/unbind
echo -n 0000:04:01.1 > 
/sys/bus/pci/drivers/ohci_hcd/unbind
echo -n 0000:04:01.2 > 
/sys/bus/pci/drivers/ohci_hcd/unbind
echo -n 0000:04:01.3 > 
/sys/bus/pci/drivers/ehci_hcd/unbind

echo -n 0000:04:01.0 > 
/sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:04:01.1 > 
/sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:04:01.2 > 
/sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:04:01.3 > 
/sys/bus/pci/drivers/pciback/new_slot

echo -n 0000:04:01.0 > 
/sys/bus/pci/drivers/pciback/bind
echo -n 0000:04:01.1 > 
/sys/bus/pci/drivers/pciback/bind
echo -n 0000:04:01.2 > 
/sys/bus/pci/drivers/pciback/bind
echo -n 0000:04:01.3 > 
/sys/bus/pci/drivers/pciback/bind
====================================================


Can any one help me here? How can I trace/solve that
problem?

greets chris



      Machen Sie Yahoo! zu Ihrer Startseite. Los geht's: 
http://de.yahoo.com/set

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] M2N32, suse 10.3 and network problem, Chris Epicier <=