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


Re: [Xen-users] Installation Problem: exec of init (/sbin/init) failed!!

To: deshantm@xxxxxxxxx
Subject: Re: [Xen-users] Installation Problem: exec of init (/sbin/init) failed!!!: No such file or directory
From: "Manu Anand" <manu.anand@xxxxxxxxx>
Date: Fri, 19 Dec 2008 00:30:03 -0800
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 19 Dec 2008 00:32:14 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=wmCHWtBUTa46AYPJE7pJdiU9iWfU0sFqJRDQcglsyuM=; b=UqW7Uj62zPD/Kvly31QEKj6LPBnevDBsUJzQc8ccXkRSS/txF3seYStbzHbbLbjnXr BRE+DgJZKcRDJI/878Fx7KOf47VIeEaWWuZfJmMn+R1soAeOvCwuHkFfo9M9xxHT3emI sLshtzM8yWzOyL1l2qWRnmwqlG+CzfFsrd8ac=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=M5LLZpXsKX6ykYcG+LWXTkUv1zltQgET9GvLrl7V0ru5x/vtWojeQmTUoHgpLTTY3d RzCLUiHQrsMOTY54kHwySnEM8grq6O93AyHcY2xj2aP5FhNSwMjARAN14730eHZQfuJs me+yIMH7sjT86AqGsi65NOsnYO/qYmrJQ28vE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1e16a9ed0812182156g47ea802fvb1dfe1e777cb6768@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: <13f5ba680812182024s7627abg1a3daea98d6d0e7@xxxxxxxxxxxxxx> <1e16a9ed0812182156g47ea802fvb1dfe1e777cb6768@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

On Thu, Dec 18, 2008 at 9:56 PM, Todd Deshane <deshantm@xxxxxxxxx> wrote:
On Thu, Dec 18, 2008 at 11:24 PM, Manu Anand <manu.anand@xxxxxxxxx> wrote:
> Hi folks:
> I'm having the exact problem with /sbin/init described at
> http://lists.xensource.com/archives/html/xen-users/2007-04/msg00570.html
> The environment is CentOS but the problem and the steps I've taken are
> exactly the same.

That thread is somewhat hard to follow, but the suggestions seem good.

The basic idea is that you have a guest on a different partition and you
are trying to boot it?

Hey Todd:

That missing / was a typo.
I re-generated the initrd file anyways and it still fails with the same error.

The only thing that I'm doing differently is that I created a new device file /dev/sda10 for the guest
However the linux kernel is the same as the one that DomU is using.

I cannot reboot the system to check out whether the boot loader will be able to load the new image.
I'll try that tomorrow.
I'm playing with some centos specific install programs (virt-install, virt-image etc) in the meantime..

Thanks for your help

The guest was/is a normal linux install?

Are you just missing a forward slash in the fstab below?
(/dev/sda10)? or is that just a typo?

Do make sure that everything is in the right spot...

chroot in the the partition for example.

Is it bootable as a normal linux system with grub
(not as a xen guest, just to test)?

> The guest's fstab is
> dev/sda10       /               ext3    defaults        1 1
> tmpfs                   /dev/shm                tmpfs   defaults        0 0
> devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
> sysfs                   /sys                    sysfs   defaults        0 0
> proc                    /proc                   proc    defaults        0 0
> LABEL=SWAP-sda2         swap                    swap    defaults        0 0
> My config script is
> kernel = "/boot/vmlinuz-2.6.18-92.1.18.el5xen"
> ramdisk = "/boot/2.6.18-92.1.18.el5xen-custom-3"
> memory = 256
> name = "ExampleDomain"
> vif = [ '' ]
> disk = [ 'tap:aio:/home/admin/vm1disk,sda10,w', ]
> root = "/dev/sda10 rw"

don't put the rw in the root line.


Try it instead in the extra
extra="ro 4"

Hope that helps.


Todd Deshane

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>