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

[Xen-users] exec of init (/sbin/init) failed!!!: No such file or directo

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] exec of init (/sbin/init) failed!!!: No such file or directory
From: "Emre ERALTAN" <eeraltan@xxxxxxxxx>
Date: Thu, 19 Apr 2007 09:59:35 +0200
Delivery-date: Thu, 19 Apr 2007 00:58:27 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=eON0gFD3i8EEkaANUSr/xxUt4j639dgWuX4ZwcIboxX/P+vyFFNMTwI68lumTlbj6cgxYSDhuJUONhKjmJF/AwRKrUyU4bd+ZgIiCs03lwupedp2tZcA5VeY4bAnhrDnVUIzoSGo/FtMD95lBdXMD1DLmK4rC3waKXCfykRtqRg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=l07e4C8UijE6fVfkU4DCYvoQrPv3MPVmmX+WQhSg3MUOJv6ErLstzQqtcQ0tJChRBVNhBkecWVA3q2Gka9GlEKFfCHCoJTV6Wm2AlE0/b/neAqXypBLOexXqhbyriAu1SLaXGW7M0F/UbFSo2EC+9XBHMMG3VN+XFcxvy/2iq5o=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I am a newbie using RHEL 5 with Xen 3.0.3-25.el5 (integrated in this version of RHEL). So, I have included the Xen package when I installed RHEL and then I installed the kernel-xen component which has created in my boot directory 4 files : vmlinuz-2.6.18-8.el5xen, initrd-2.6.18-8.el5xen.img, config-2.6.18-8.el5xen and xen.gz-2.6.18-8.el5. I have also now 2 boot options in my grub.conf :


title Red Hat Enterprise Linux Server (2.6.18-8.el5xen)
        root (hd0,0)
        kernel /xen.gz-2.6.18-8.el5
        module /vmlinuz-2.6.18-8.el5xen ro root=LABEL=/ console=ttyS0,115200n81 reboot=t
        module /initrd-2.6.18-8.el5xen.img
title Red Hat Enterprise Linux Server (2.6.18-8.el5 )
        root (hd0,0)
        kernel /vmlinuz-2.6.18-8.el5 ro root=LABEL=/ console=ttyS0,115200n81 reboot=t
        initrd /initrd-2.6.18-8.el5.img

Then I have decided to run another RHEL 5 as guest OS and I followed tips on the internet:

First of all, I booted with the xen kernel then:

1) dd if=/dev/zero of=/xen/xen2 bs=1M count=1 seek=5120
2) mkfs -t ext3 /xen/xen2
3) mount -o loop /xen/xen2 /mnt
4) cp -vrf /{root,dev,var,etc,usr,bin,sbin,lib} /mnt
5) mkdir /mnt/{proc,sys;home,tmp}
6) umount /mnt (if you forget to do this when you call "xm create -c config_file" it gives an error due to destroyDevice() function)

Then I filled the config_file as following:

kernel = "/boot/vmlinuz-2.6.18-8.el5xen"
ramdisk = "/boot/initrd-2.6.18-8.el5xen.img"
vif = [ '' ]
disk = [ 'file:/xen/xen2,sda2,w' ]
root = "/dev/sda2"
extra = "ro"

But a got the following error when I try to start my domU "xm create -c /etc/xen/xmexample1:

Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!

Then I have tried to create my own initrd image and used the mkinitrd command as following :
mkinirtd /boot/initrd-2.6.18-8.el5xenU 2.6.18-8.el5xen --fstab /mnt/etc/fstab --with xenblk --with xennet --preload xenblk --preload xennet
and changed the ramdisk line in my configuration file ramdisk = "/boot/initrd-2.6.18-8.el5xenU"

But now I got another error : exec of init (/sbin/init) failed!!!: No such file or directory

register_blkdev: cannot get major 8 for sd
Loading scsi_transport_sas.ko module
Loading mptscsih.ko module
Loading mptsas.ko module
Fusion MPT SAS Host driver 3.04.02
Waiting for driver initialization.
Creating root device.
Mounting root filesystem.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Setting up other filesystems.
Setting up new root fs
no fstab.sys, mounting internal defaults
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
exec of init (/sbin/init) failed!!!: No such file or directory
Kernel panic - not syncing: Attempted to kill init!

I have already checked the /sbin/init file which seems to be correct and with necessary rights.

Here is my fstab in the guest FS :

dev/sda2                 /                  ext3            defaults        1 1
LABEL=/boot1       /boot                               defaults        1 2
devpts                  /dev/pts                             devpts  gid=5,mode=620  0 0
tmpfs                   /dev/shm                           tmpfs   defaults        0 0
proc                    /proc                                  proc    defaults        0 0
sysfs                   /sys                                  sysfs   defaults        0 0
LABEL=SWAP-sda3                  swap           swap    defaults        0 0

Does anybody know why I got this error ?

Thanks
--

- - - - - - - - - - - - - -  -  -  -  -  -  -  -  -  -  -  -
Emre ERALTAN
Elève ingénieur 3ème année
Electronique et Informatique Industrielle
ENSSAT
- - - - - - - - - - - - - -  -  -  -  -  -  -  -  -  -  -  -

Attachment: xm create log.txt
Description: Text document

Attachment: xend.log
Description: Binary data

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