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] SLES10 guest OSes drop off network.

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] SLES10 guest OSes drop off network.
From: Scott Forten <scott.forten@xxxxxxxxxx>
Date: Wed, 23 Aug 2006 09:44:45 -0700
Delivery-date: Wed, 23 Aug 2006 09:45:40 -0700
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>
Organization: Oracle Corporation
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.5 (Windows/20060719)
I am having issues with guest OSes running on SLES10 (Sun 4200) hosts.

Periodically, the guest OS system drops off the network. From the general network it is not pingable, consequently, ssh fails. If however, I log into the SLES10 server that is hosting the guest OS and ssh to the guest OS, then it becomes immediately pingable and accessible to the rest of the network. Almost like the network on the guest os is sleeping.

The guest OSes are configured to have two networks, one public and one private. They are bound to different NIC cards on the physical host. dmesg reports the following from the xen host (SLES10 on a Sun 4200)

device vif24.1 entered promiscuous mode
xenbr1: port 4(vif24.1) entering learning state
xenbr1: topology change detected, propagating
xenbr1: port 4(vif24.1) entering forwarding state
device vif24.0 entered promiscuous mode
xenbr0: port 4(vif24.0) entering learning state
xenbr0: topology change detected, propagating
xenbr0: port 4(vif24.0) entering forwarding state
device vif24.2 entered promiscuous mode

Here is the configuration file for the xen guest OS;

disk = [ 'file:/xen1/rhel4u3.img,hda,w', 'file:/xen/swap/xen1swap,sdb6,w' ]
memory = 2048
vcpus = 2
builder = 'linux'
name = 'xen1'
vif = [ 'mac=00:16:3e:4b:bb:4e,bridge=xenbr0', 'mac=00:16:3e:f1:56:2d,bridge=xenbr1', 'mac=00:16:3e:3e:e8:75', 'mac=00:16:3e:85:b5:60' ]
root = '/dev/hda1'
localtime = 0
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
extra = ' TERM=xterm'
bootloader = '/usr/lib/xen/boot/domUloader.py'
bootentry = 'hda1:/boot/vmlinuz-2.6.16-xen,/boot/initrd-2.6.16-xen.img'

And the configuration of my-network-script, which is used to bind xenbr0 and xenbr1 to specific nic cards
#!/bin/sh
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth1

Is there some configuration file or sleep mode that is causing the guest OS to shutdown it's network or otherwise go to sleep?

Scott

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] SLES10 guest OSes drop off network., Scott Forten <=