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/
Home Products Support Community News


[Xen-tools] [RFC] Daemon startup order

To: xen-tools@xxxxxxxxxxxxxxxxxxx, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-tools] [RFC] Daemon startup order
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Thu, 04 Aug 2005 10:46:24 -0500
Delivery-date: Thu, 04 Aug 2005 19:52:55 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-tools-request@lists.xensource.com?subject=help>
List-id: Xen control tools developers <xen-tools.lists.xensource.com>
List-post: <mailto:xen-tools@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-tools>, <mailto:xen-tools-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-tools>, <mailto:xen-tools-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-tools-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (X11/20050317)

A few people are having problems with the new console daemon and I've tracked the problem down to the order in which daemons are started. Here's what currently happens:

1) xend (the script in tools/misc) start will launch xcs and consoled
2) xend (the python server) will launch xenstored whenever it needs it

This creates a bit of a chicken and the egg problem since consoled needs xenstored to function. There's a few options:

1) Have consoled (and all future daemons) implement the logic to wait for xenstored to start
2) Move xenstored launching to xend (the script in tools/misc)
3) Give all the daemons proper init.d scripts with dependencies

I'm partial to #3 although #2 would be a fine quick hack.

For now, if anyone gets messages about not being able to read the tty with xm console, simply run consoled.


Anthony Liguori

Xen-tools mailing list

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