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-devel

[Xen-devel] Problem booting Suse Linux VM "INIT: cannot execute "/etc/in

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Problem booting Suse Linux VM "INIT: cannot execute "/etc/init.d/boot""
From: "sanjay kushwaha" <sanjay.kushwaha@xxxxxxxxx>
Date: Tue, 29 May 2007 11:13:15 -0700
Delivery-date: Tue, 29 May 2007 11:11:33 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=fHEJNaDEkWzA3YgfDiPTyWtGIw9NdJWnVHEEE6ppjnCBjLTr7krlIz06f/zc2ukwizOGhW5QcHpfHhqSqEG2XZedIH7Yj3t/DX9MfCDblTIhSKnlQyVky0nRkrTDl9DRz9Ff6G1sgfv4zuuuyo4yEwouY+xSQJfYkvN6gcBTcXQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=hGay06okv1qOnFnU3c7NpOgAbsjtX2fuLGO93BfeapEk9Jk7LnGDcxPXV1/JLQ+H0rBs/HlEQ/+j3rOJLPT7nbljGT54lMAGBMCHsp+MKHTBmk+duwBnyGxlY1OVSNCFszkqBvPbq5NNJZVCL7BZt8IoKBxIz38rf6h/OUH0mEM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Folks,
I create a file backed vbd to boot a guest VM as described in the Xen's user manual in section 'Using File-backed VBDs". The Dom0 and the VBD contain Suse Linux Enterprise Server 10 (X86_64). I am not able to boot the guest VM. During the boot process the INIT process generates an error saying
 
<snip>
Loading jbd
Loading ext3
Waiting for device /dev/sda1 to appear:  ok
rootfs: major=8 minor=1 devn=2049
fsck 1.38 (30-Jun-2005)
[/bin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1
/dev/sda1: clean, 85082/524288 files, 665367/1048576 blocks
fsck succeeded. Mounting root device read-write.
Mounting root /dev/sda1
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
INIT: version 2.86 booting
INIT: cannot execute "/etc/init.d/boot"
INIT: Entering runlevel: 3
INIT: cannot execute "/etc/init.d/rc"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
<snip>
 
 
 
I am using the latest unstable Xen tree. Below is the full log. Thanks a lot for any help.
Sanjay
 

bladespp-04:~ # dd if=/dev/zero of=vmdisk bs=1k seek=4096k count=1
1+0 records in
1+0 records out
1024 bytes (1.0 kB) copied, 8.1e-05 seconds, 12.6 MB/s
bladespp-04:~ #
bladespp-04:~ # mkfs -t ext3 vmdisk
mke2fs 1.38 (30-Jun-2005)
vmdisk is not a block special device.
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
524288 inodes, 1048576 blocks
52428 blocks (5.00%) reserved for the super user
First data block=0
32 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736

Writing inode tables: done                           
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 37 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

bladespp-04:~ # mount -o loop vmdisk /mnt/
bladespp-04:~ # cp -ax /{root,dev,var,etc,usr,bin,sbin,lib} /mnt
bladespp-04:~ # mkdir /mnt/{proc,sys,home,tmp}
bladespp-04:~ # cat /mnt/etc/fstab

/dev/sda1            /                    ext3       defaults              1 1
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0

bladespp-04:~ # umount /mnt/
bladespp-04:~ #
The VM configuration file:
bladespp-04:~ # cat xmexample1

# Kernel image file.
kernel = "/boot/vmlinuz-2.6-xen"

# Optional ramdisk.
ramdisk = "/boot/initrd-2.6-xen.img"

memory = 256

name = "ExampleDomain"

vif = [ '' ]

disk = [ 'tap:aio:/root/vmdisk,sda1,w' ]

# Set root device.
root = "/dev/sda1"

# Sets runlevel 4.
extra = "3"

bladespp-04:~ #
bladespp-04:~ # xm list
Name                                      ID   Mem VCPUs      State   Time(s)
Domain-0                                   0  7646     2     r-----    213.1
bladespp-04:~ # xm create -c xmexample1
Using config file "./xmexample1".
Started domain ExampleDomain
Bootdata ok (command line is root=/dev/sda1 3)
Linux version 2.6.18-xen (sanjaykumar4@bladespp-03 ) (gcc version 4.1.0 (SUSE Linux)) #1 SMP Thu May 24 22:32:35 PDT 2007
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)
No mptable found.
Built 1 zonelists.  Total pages: 67584
Kernel command line: root=/dev/sda1 3
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 16384 bytes)
Xen reported: 2605.904 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB disabled
Memory: 245608k/270336k available (2001k kernel code, 16224k reserved, 870k data, 172k init)
Calibrating delay using timer specific routine.. 5213.10 BogoMIPS (lpj=26065536)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
SMP alternatives: switching to UP code
Freeing SMP alternatives: 24k freed
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 6784k freed
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
PCI: System does not support PCI
PCI: System does not support PCI
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
IA-32 Microcode Update Driver: v1.14a-xen <tigran@xxxxxxxxxxx>
audit: initializing netlink socket (disabled)
audit(1180465319.472:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as tty1
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
NET: Registered protocol family 17
xen-vbd: registered block device major 8
netfront: device eth0 has copying receive path.
XENBUS: Device with no driver: device/console/0
Freeing unused kernel memory: 172k freed
Starting udevd
Creating devices
Loading jbd
Loading ext3
Waiting for device /dev/sda1 to appear:  ok
rootfs: major=8 minor=1 devn=2049
fsck 1.38 (30-Jun-2005)
[/bin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1
/dev/sda1: clean, 85084/524288 files, 673052/1048576 blocks
fsck succeeded. Mounting root device read-write.
Mounting root /dev/sda1
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
INIT: version 2.86 booting
INIT: cannot execute "/etc/init.d/boot"
INIT: Entering runlevel: 3
INIT: cannot execute "/etc/init.d/rc"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: Id "2" respawning too fast: disabled for 5 minutes
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: Id "3" respawning too fast: disabled for 5 minutes
INIT: Id "4" respawning too fast: disabled for 5 minutes
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: cannot execute "/sbin/mingetty"
INIT: Id "5" respawning too fast: disabled for 5 minutes
INIT: Id "6" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel
bladespp-04:~ #

bladespp-04:~ # xm info
host                   : bladespp-04
release                : 2.6.18-xen
version                : #1 SMP Thu May 24 22:32:35 PDT 2007
machine                : x86_64
nr_cpus                : 2
nr_nodes               : 1
sockets_per_node       : 2
cores_per_socket       : 1
threads_per_core       : 1
cpu_mhz                : 2605
hw_caps                : 078bfbff:e3d3fbff:00000000:00000010:00000001
total_memory           : 8023
free_memory            : 0
xen_major              : 3
xen_minor              : 0
xen_extra              : -unstable
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Thu May 17 11:42:46 2007 +0100 15080:089696e0c603
cc_compiler            : gcc version 4.1.0 (SUSE Linux)
cc_compile_by          : sanjaykumar4
cc_compile_domain      : hpl.hp.com
cc_compile_date        : Tue May 29 09:23:36 PDT 2007
xend_config_format     : 4
bladespp-04:~ #


--
----------------------
PhD Student, Georgia Tech
http://www.cc.gatech.edu/~ksanjay/
 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Problem booting Suse Linux VM "INIT: cannot execute "/etc/init.d/boot"", sanjay kushwaha <=