not able to run any of the conf file as xm create

Submitted by cpallab on Thu, 05/07/2009 - 8:36am
in

not able to run any of the conf file as xm create -c conf file..
gives:

VFS: Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

my kernel vmlinuz-2.6.16.60-0.21-xenpae
os: sles10sp2
xen: Xen 3.0.4

pls help..

‹ Problem with /dev/xvda I am new ›
Submitted by stacklet on Sun, 05/10/2009 - 3:09am.

I have seen this happen when I tried to boot an image that was already mounted as a loop device -- so first make sure the image is not mounted.

I need more info to troubleshoot though -- will send you an email for further details and post here if it can be resolved

Submitted by wondermm on Mon, 05/11/2009 - 12:52pm.

Same problem here..
.
.
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/console/0
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

my config file is

kernel = "/xen/centos/vmlinuz-2.6.18-128.1.6.el5xen"
memory = 256
name = "centos"
vif = [ '' ]
disk = ['file:/xen/centos/centos.5-3.x86-64.img,sda1,w']
root = "/dev/sda1"
extra = "fastboot"

and in the image file /etc/fstab

/dev/sda1 /

Submitted by stacklet on Tue, 05/12/2009 - 2:42pm.

I would be curious to know if you can boot the image with a lightweight domU kernel I just made available:

http://stacklet.com/downloads/kernels/xen/xenU32bit

Submitted by wondermm on Wed, 05/13/2009 - 4:33am.

Now it find the disk, but freezes after request_module: runaway loop modprobe binfmt-464c

NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
xen-vbd: registered block device major 8
blkfront: sda1: barriers enabled
XENBUS: Device with no driver: device/console/0
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Freeing unused kernel memory: 140k freed
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c

Submitted by mitch.sanders on Sun, 05/09/2010 - 8:04am.

Yeah I second that. Im having the same problem here.

Submitted by zagi on Wed, 07/22/2009 - 2:26am.

You need to create a ramdisk which replaces the SCSI modules with XENBLK to mount the filesystem. Use the following command to create it:

mkinitrd --omit-scsi-modules --with=xennet --with=xenblk --preload=xenblk initrd-$(uname -r)-no-scsi.img $(uname -r)

It will be in /boot/ - and add the following to your config file:

ramdisk = "/boot/initrd-VERSION-no-scsi.img"

www.RealityCheckNetwork.com

Submitted by smallpox on Fri, 07/24/2009 - 6:11am.

im getting almost an immediate restart and i'm connected via KVM over IP.. i cant read the error.

i've managed to add ext3 and some raid into the kernel (im doing software raid 1)

http://www.imgbin.org/index.php?page=image&id=656

it doesn't detect md like it should and i'm 100% it's ext3.


© 2010 Stacklet LLC - Privacy