From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] initrd & kernel panic
Date: Sat, 24 Jun 2006 13:20:36 +0100 [thread overview]
Message-ID: <200606241320.37722.paul@codesourcery.com> (raw)
In-Reply-To: <d5a13c80606240420p66862d2x@mail.gmail.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.
Paul
next prev parent reply other threads:[~2006-06-24 12:20 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 [this message]
2006-06-26 1:23 ` VMiklos
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=200606241320.37722.paul@codesourcery.com \
--to=paul@codesourcery.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).