Xen users - Feb 2007 - "INIT: cannot execute ''/etc/init.d/boot''"

I have a disk image file that was created using dd, makereiserfs dance,

operating system files copied in directly with cp -ax (vi a temporary
mount,

and then dismounted).

 

My domU configuration is as follows:

 

--------------------------------

 

kernel = "/RAID/data/xen/bootsles10/vmlinuz-xen"

ramdisk = "/RAID/data/xen/bootsles10/initrd-xen"

memory = 2048

name = "vm2"

vcpus = 1

vif = [ ''mac=00:16:3e:01:00:11, bridge=xenbr0'' ]

 

disk = [ ''file:/RAID/data/xen/images/suse.img,hda1,w'' ]

 

dhcp="dhcp"

 

#root = "/dev/hda1 ro"

root = "/dev/hda1"

 

extra = "4"

on_poweroff = ''preserve''

on_reboot = ''restart''

on_crash = ''restart''

 

--------------------------------

 

Please note the "disk" and "root" lines. The path to the
suse.img file
is correct.

The paths to the kernels and the ramdisks are correct.

 

I''m calling your attention to the disk and root lines, because I cannot
find a guide

that explains all the options here, and am not entirely sure they are
correct.

 

On to my errors:

 

 

...

Trans replayed: mountid 19, transid 188, desc 6288, len 10, commit 6299,
next trans offset 6282

Reiserfs journal ''/dev/hda1'' in blocks [18..8211]: 5
transactions
replayed

Checking internal tree..finished

fsck succeeded. Mounting root device read-write.

Mounting root /dev/hda1

ReiserFS: hda1: found reiserfs format "3.6" with standard journal

ReiserFS: hda1: using ordered data mode

reiserfs: using flush barriers

ReiserFS: hda1: journal params: device hda1, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30

ReiserFS: hda1: checking transaction log (hda1)

reiserfs: disabling flush barriers on hda1

ReiserFS: hda1: Using r5 hash to sort names

INIT: version 2.86 booting

INIT: cannot execute "/etc/init.d/boot"

INIT: Entering runlevel: 4

INIT: cannot execute "/sbin/mingetty"

...repeats...

....

 

--------------------------------

 

I''ve navigated this file system and checked that the "cannot
execute"
files are executable.

They are. I''m wondering if there is some pathing problem?

 

The other thing that I''ve tried is commenting out the "root"
line. I
get:

 

"Waiting for device /dev/sda2 to appear: ..................not found
-exiting to /bin/sh"

 

Is there something wrong with my domU config?

 

Joe Kraska

San Diego CA

USA

 

 



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