[Qemu-devel] initrd & kernel panic

[Qemu-devel] initrd & kernel panic

[VMiklos]

hi

currently i'm using qemu in the following way to test our installer on x86:
1) build the kernel
2) build the initrd
3) build a mini iso with a grub that boots the kernel

it would be nice if i could avoid the 3rd step

what i've tried:

http://frugalware.org/~vmiklos/logs/qemu-initrd.log

if i generate the iso and boot this kernel & initrd with the same
parameters from grub, it works fine

have i missed something?

thanks,
VMiklos

--
Developer of Frugalware Linux, to make things frugal - http://frugalware.org

Re: [Qemu-devel] initrd & kernel panic

[Paul Brook]

> what i've tried:
>
> http://frugalware.org/~vmiklos/logs/qemu-initrd.log
>
> if i generate the iso and boot this kernel & initrd with the same
> parameters from grub, it works fine
>
> have i missed something?

You're telling it to load the initrd from floppy, which is obviously wrong. 
qemu already loaded the initrd. Remove all the broken initrd/ramdisk kernel 
commandline bits.

Paul

Re: [Qemu-devel] initrd & kernel panic

[VMiklos]

hi,

2006/6/24, Paul Brook <paul@codesourcery.com>:
> > what i've tried:
> >
> > http://frugalware.org/~vmiklos/logs/qemu-initrd.log
> >
> > if i generate the iso and boot this kernel & initrd with the same
> > parameters from grub, it works fine
> >
> > have i missed something?
>
> You're telling it to load the initrd from floppy, which is obviously wrong.
> qemu already loaded the initrd. Remove all the broken initrd/ramdisk kernel
> commandline bits.

initrd=initrd-i686.img.gz -> dropped
load_ramdisk=1 -> dropped
prompt_ramdisk=0 -> dropped
ramdisk_size=33888 -> dropped
rw -> kept
root=/dev/ram -> dropped
console=ttyS0 -> kept as you requested

now it panics with:
"RAMDISK: Couldn't find valid RAM disk image starting at 0.
VFS: Cannot open root device "<NULL>" or unknown-block(33,2)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(33,2)"

ok, let's append root=/dev/ram again, still panics:
"RAMDISK: Couldn't find valid RAM disk image starting at 0.
XFS: bad magic number
XFS: SB validate failed
No filesystem could mount root, tried:  reiserfs ext3 ext2 xfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)"

have i missed something?

thanks,
VMiklos

--
Developer of Frugalware Linux, to make things frugal - http://frugalware.org

Re: [Qemu-devel] initrd & kernel panic

[Ed Swierk]

On 6/25/06, VMiklos <vmiklos@gmail.com> wrote:
> initrd=initrd-i686.img.gz -> dropped
> load_ramdisk=1 -> dropped
> prompt_ramdisk=0 -> dropped
> ramdisk_size=33888 -> dropped
> rw -> kept
> root=/dev/ram -> dropped
> console=ttyS0 -> kept as you requested
>
> now it panics with:
> "RAMDISK: Couldn't find valid RAM disk image starting at 0.
> VFS: Cannot open root device "<NULL>" or unknown-block(33,2)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(33,2)"
>
> ok, let's append root=/dev/ram again, still panics:
> "RAMDISK: Couldn't find valid RAM disk image starting at 0.
> XFS: bad magic number
> XFS: SB validate failed
> No filesystem could mount root, tried:  reiserfs ext3 ext2 xfs
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)"
>
> have i missed something?

What format is your initrd? It should be either a gzipped cpio archive
(initramfs) or an uncompressed filesystem image file.

See http://lxr.linux.no/source/Documentation/initrd.txt and
http://lxr.linux.no/source/Documentation/early-userspace/README.

--Ed

[Qemu-devel] Asking about developing Qemu with Eclipse

[Tieu Ma Dau]

[-- Attachment #1: Type: text/plain, Size: 887 bytes --]

Hi all,
  I want to develop Qemu to simulate only ARM processor, so I've configured Qemu source code on MinGW/Msys with the command below:
  ./configure --target-list=arm-softmmu
  And after that I've created a new Eclipse project on the directory  which contains the source code configured. I've tried to build the  project (with Eclipse menu: Project -> Build All) and I've got the  error below: 
  
  make[1]: *** No rule to make target `vl.c', needed by `vl.o'.
  make[1]: *** No rule to make target `osdep.c', needed by `osdep.o'.
  ...
  make[1]: Entering directory `/cygdrive/d/travail/develop/qemu-0.8.1_after_config_for_arm/arm-softmmu'
  make[1]: *** No rule to make target `pci.c', needed by `pci.o'.
  ....
  
  Where the problems arrive?
  Best regard
  Tieu
  
 		
---------------------------------
Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.

[-- Attachment #2: Type: text/html, Size: 1043 bytes --]

Re: [Qemu-devel] initrd & kernel panic

[VMiklos]

2006/6/26, Ed Swierk <eswierk@arastra.com>:
> What format is your initrd? It should be either a gzipped cpio archive
> (initramfs) or an uncompressed filesystem image file.
>
> See http://lxr.linux.no/source/Documentation/initrd.txt and
> http://lxr.linux.no/source/Documentation/early-userspace/README.

as i said the kernel&initrd is ok if i boot them (using grub) from an
iso image. anyway i've tried to uncompress the gzipped initrd, and it
didn't help (same "RAMDISK: Couldn't find valid RAM disk image
starting at 0." error message)

if grub is able to boot the kernel & initrd and qemu isn't then the
kernel & initrd should be ok, just the parameters may be wrong or
there should be some problem with qemu itself. or am i wrong?

thanks,
VMiklos

--
Developer of Frugalware Linux, to make things frugal - http://frugalware.org