From: VMiklos <vmiklos@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] initrd & kernel panic
Date: Mon, 26 Jun 2006 03:23:49 +0200 [thread overview]
Message-ID: <d5a13c80606251823q313dbaf1j@mail.gmail.com> (raw)
In-Reply-To: <200606241320.37722.paul@codesourcery.com>
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
next prev parent reply other threads:[~2006-06-26 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 11:20 [Qemu-devel] initrd & kernel panic VMiklos
2006-06-24 12:20 ` Paul Brook
2006-06-26 1:23 ` VMiklos [this message]
2006-06-26 2:02 ` Ed Swierk
2006-06-26 7:38 ` [Qemu-devel] Asking about developing Qemu with Eclipse Tieu Ma Dau
2006-06-26 21:14 ` [Qemu-devel] initrd & kernel panic VMiklos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5a13c80606251823q313dbaf1j@mail.gmail.com \
--to=vmiklos@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.