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

Re: [Xen-users] Killall very slow

To: Xen User List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Killall very slow
From: "John A. Sullivan III" <jsullivan@xxxxxxxxxxxxxxxxxxx>
Date: Fri, 27 Jan 2006 01:43:10 -0500
Delivery-date: Fri, 27 Jan 2006 06:52:25 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1138340908.31378.57.camel@localhost>
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>
References: <1138340908.31378.57.camel@localhost>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 2006-01-27 at 00:48 -0500, John A. Sullivan III wrote:
> Hello, all.  When we halt or reboot dom0, we find that the shutdown
> process waits for an extraordinarily long time at killall.  There
> doesn't seem to be much going on in the script so I'm not sure what's
> causing such a delay.  It smells like it's waiting for a timeout.  Has
> anyone else experienced this? Does anyone know how to fix it? Thanks -
> John

Ah, I think I found it.  I noticed that xend and xendomains seemed to be
terminating after killall.  I looked in rc0.d and rc6.d (I'm using a
SYSV system - FC3) and there were no kill links for xend or xendomains.
I added them to run before killall and now the system reboots in a snap.
Is this safe? Have I inadvertently done something evil?

On a related note, I am temporarily in a bit of a chicken and egg
scenario.  The default gateway for the dom0 is temporarily a domU
running on the dom0.  Thus, the dom0 does not have access to DNS, NTP
(all on the Internet for now), etc. during boot.  Thus the boot time is
very long while it waits for all the timeouts.  I changed the start
order in rc3.d and rc5.d to start xend and xendomains after network but
before anything that requires Internet access.  Is this safe or have I
again accidentally done evil? Thanks - John
-- 
John A. Sullivan III
Open Source Development Corporation
+1 207-985-7880
jsullivan@xxxxxxxxxxxxxxxxxxx

Financially sustainable open source development
http://www.opensourcedevel.com


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

<Prev in Thread] Current Thread [Next in Thread>