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-devel

Re: [Xen-devel] [PATCH] rombios: pause for a keypress after a failedboot

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] rombios: pause for a keypress after a failedboot
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 7 Jul 2010 07:26:47 +0100
Cc:
Delivery-date: Tue, 06 Jul 2010 23:27:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01A0A4C2@trantor>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcsdE8WgV7isuNqsSTi7Q8hETWVhSQAYZ04QAAn/UrA=
Thread-topic: [Xen-devel] [PATCH] rombios: pause for a keypress after a failedboot
User-agent: Microsoft-Entourage/12.24.0.100205
On 07/07/2010 02:43, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

>> rombios: inform the user and pause for a keypress after a failed boot
>> rather than powering off immediately.
>> 
> 
> That's a great idea for many situations, but not for all. If the DomU
> fails to boot (eg because the drbd backing store is offline or
> something) it would be nice to have the domain exit so that monitoring
> can kick in and alert someone, rather than it just sitting there in a
> running state waiting for user input that might never come.
> 
> I know it's probably a heap more work, but could the behaviour be driven
> by a config file setting? Otherwise this new behaviour is going to be a
> regression.

Simply pausign for a few seconds might be nice. Gives enough time for a user
to see what is going on, but doesn't leave an unattended VM hanging around
forever?

 -- Keir



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