Re: [Xen-users] xen and boot problems (with CentOS 4.2)

To:	"mbjohn@xxxxxxxx" <mbjohn@xxxxxxxx>
Subject:	Re: [Xen-users] xen and boot problems (with CentOS 4.2)
From:	"Eric Peterson" <srcfoo@xxxxxxxxx>
Date:	Wed, 29 Mar 2006 09:57:38 -0600
Cc:	Haavard Bjerke <havard.bjerke@xxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Wed, 29 Mar 2006 15:59:24 +0000
Domainkey-signature:	a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FE8A2843UCVvzdqoLPZJHIlvU0ivH25LdbXmZ+HGstGTLbcKgSO5EK/dcPNNRUGSCk26TovFZo4eCQTPhAh6b4SzWpmK34LgmMaIUj27aLfCPhkgi6brxSu27h9XbXuFtxDQhzC1NFx0Afw4UZQBZeKs2jOoipnMJJ3lkKKLCPc=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<Pine.GSO.4.58.0603291026070.1011@xxxxxxxxxxxxxxxxxxxxxxx>
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:	<Pine.GSO.4.58.0603291014540.1011@xxxxxxxxxxxxxxxxxxxxxxx> <442AA694.20809@xxxxxxx> <Pine.GSO.4.58.0603291026070.1011@xxxxxxxxxxxxxxxxxxxxxxx>
Sender:	xen-users-bounces@xxxxxxxxxxxxxxxxxxx

On 3/29/06, mbjohn@xxxxxxxx <mbjohn@xxxxxxxx> wrote:
> Thank you so much for the quick reply!  The fastboot option did the
> trick and I'm now in my virtual machine!
>
> Should I be concerned about having to use the fastboot option?  Will it
> cause problems later on?
>
> Thanks again!
>
> Brian

fastboot won't cause problems by itself.  It disables fsck checking on
boot.  fsck is complaining in this case because it thinks the
partition is mounted.  The way that you would find problems later on
is when the system was shutdown uncleanly and no disk check was forced
on the filesystem.

This shouldn't be a problem with you domU systems since you should
know when things have been shutdown uncleanly and you should be able
to run fsck manually on the partition from dom0 before it's next boot.

I wonder why fsck is confused?  How are you passing the block device
on to the domU? It isn't mounted in dom0 is it?  Is it a file or
partition?  Sorry for all the questions but I'm curious.

Cheers!
Eric

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