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] fedora core 6 domU on Opensuse 10.2 dom0 - fsck at each

To: "Nico Kadel-Garcia" <nkadel@xxxxxxxxx>
Subject: Re: [Xen-users] fedora core 6 domU on Opensuse 10.2 dom0 - fsck at each boot
From: "Henning Sprang" <henning_sprang@xxxxxx>
Date: Sat, 23 Dec 2006 00:19:35 +0100
Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 22 Dec 2006 15:19:39 -0800
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=HYEL59hbn93huUT5nXx3Fz+T/Kz70U6mntRJnkYsYi69ATlOh4zngp8ZMaE1HvJYPawRq9xTs507Ge41wOhxHX6aaFFM+ZO5UP+UPkczxsfAAV/zWWC4jPYNZpdviEjrEBP6GJ4lO3oYT7bC+bsMlJi0Hi4+KJsQeF+YlBuVfWM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <458C56F6.9070300@xxxxxxxxx>
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: <5bb00b3f0612211720w5dfd543ds979a8f8729e27951@xxxxxxxxxxxxxx> <458C56F6.9070300@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 12/22/06, Nico Kadel-Garcia <nkadel@xxxxxxxxx> wrote:
Henning Sprang wrote:

> I have only one problem: the installed fedora system always wants to
> make a filesystem check for the root file system on /dev/xvda1, on
> every start and reboot.
Make sure that your Xen configuration uses the "ro" kernel option: I
just ran into this while throwing debris out of a Xen configuration.
(selinux=0 and hard-coding the runlevel is foolish, they should be
controlled by the installed guest operating system configuration itself.)

yes, that solved it. thanks a lot! I think i removed the ro when some
other domu was misbehaving, and removing the ro solved that in turn.
Then I copied this template.

Henning

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