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] Waiting for root file system...

To: "Fajar A. Nugraha" <list@xxxxxxxxx>
Subject: Re: [Xen-users] Waiting for root file system...
From: chrisbenninger <chrisbenninger@xxxxxxxxx>
Date: Mon, 10 Jan 2011 18:51:08 -0800
Cc: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 10 Jan 2011 18:52:54 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=gmlFjTftW8idyKAkPR2rekpsnGAIvSp7Gi0fpGLioxo=; b=Dd006Lqi3gOCbkP0nNYsxUKWjd4oPMkLAlgCYjXfwnlUFWveswYktKHA1+7gA4C1LF cXsMqZHz8cdgFl5wPD24FKy3vaCE8OAmwQojEqcr1V7kFgdF0c2zjjRrHXbeFnMfVnxl D8JtJLx/0OdDVmczsIrEE7KcvqTEAIdXfzMNs=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=VO66dZuwkAzP1Svi3MdFdpr+nNOnXpvyxlYqaAd65qH1ckuM0vUl/Kqx8xX5DKfOXU 7i6uOK1srdiVZvGHRMqAfUHpFkGnDkjehKf2PRpOEuJ+PG3IvrFyUk7fWyrvoJ2FY39Q fXbLqCAp1/Wo9eZ8S0VzeSmb7rsmtWkqJUceg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTikvW8GYKyHU9S=D=wrgQjtkTLdcCV-7TZ7_QeVJ@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTimUDuLOmog_dcUb5RAa5odvt1vTnZ7pZ+jcx+Jd@xxxxxxxxxxxxxx> <AANLkTi=EWnG2CZMdjXwWuXXDsC4Yg7TZCu9uPFQTUX7i@xxxxxxxxxxxxxx> <AANLkTin2qo4pOeFNmGwR4EOD64joJJjyT5CdbkZyA31b@xxxxxxxxxxxxxx> <AANLkTikvW8GYKyHU9S=D=wrgQjtkTLdcCV-7TZ7_QeVJ@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I generated a new image and this time it worked. I guess the internals of the image didn't match the configuration in the .cfg file?

Chris Benninger
University of Victoria, Computer Science
cbenning@xxxxxxxxxx
http://benninger.ca


On Mon, Jan 10, 2011 at 6:28 PM, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
On Tue, Jan 11, 2011 at 7:32 AM, chrisbenninger
<chrisbenninger@xxxxxxxxx> wrote:
> Whoops,

Please keep list traffic on the list. Someone else might experience
the same problem and can benefit from reading the archives.

> Sorry that xvda was leftover after I tried something, My apologies: The
> config is:
>>
>> kernel = "/boot/vmlinuz-2.6.32.27"
>> ramdisk = "/boot/initrd.img-2.6.32.27-xen"
>> memory = 512
>> vcpus = 1
>> name = "ubuntu910_3"
>> disk =
>> ['file:/media/vm/appliances/ubuntu910_3/ubuntu.9-10.x86-64.img,sda1,w']
>> root = "/dev/sda1 ro"
>> extra = "xencons=tty"
>
> The output is identical to before.

Then the suggestion is identical as before. Have you done it?

> I feel like I am missing a module in the
> initrd but I am not sure which.
>
> Chris Benninger
> University of Victoria, Computer Science
> cbenning@xxxxxxxxxx
> http://benninger.ca
>
>
> On Mon, Jan 10, 2011 at 4:21 PM, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
>>
>> On Tue, Jan 11, 2011 at 6:09 AM, chrisbenninger
>> <chrisbenninger@xxxxxxxxx> wrote:
>> > The domU is booting the 2.6.32.27 kernel with an initrd i generated and
>> > was
>> > using before just fine.
>>
>> Really?
>> Usually things don't "just break"
>>
>> >>     0.161289] xvde1: detected capacity change from 0 to 10486808576
>>
>> >> ['file:/media/vm/appliances/ubuntu910_3/ubuntu.9-10.x86-64.img,sda1,w']
>> >> root = "/dev/xvda1 ro"
>>
>> If you only map one disk, then something weird is happening, cause the
>> boot log say it's detected as xvde1. Try changing "root" parameter on
>> your config file to that (or whatever the boot log shows if it changes
>> again).
>>
>> It might be easier if you use LABEL or UUID. That way you don't have
>> to worry about device name change.
>>
>> --
>> Fajar
>
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>