From: "André Braga" <meianoite@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] about qemu
Date: Mon, 5 Sep 2005 13:00:11 -0300 [thread overview]
Message-ID: <2ad73a05090509004ab97887@mail.gmail.com> (raw)
In-Reply-To: <431C0C4B.000005.12601@m191.126.com>
Well, as far as I can see, you're passing the RAW DEVICE NODE as the
root partition instead of the numbered partition convention.
Instead of passing root=/dev/hda, try something like root=/dev/hda1
I hope that helps.
p.s.: Next time, please, take your time to read what you're doing
before complaining to a discussion list that had nothing to do with
the problem you faced in the first place.. And, as you may or may not
have noticed, your last sentence sounded somewhat harsh...
Cheers,
A.
--
"The weakest way to solve a problem is just to solve it"-Alan Kay
2005/9/5, wfreshair <wfreshair@126.com>:
> hi
> i have read the pdf file:Embedded Linux kernel and driver developm Training
> lab book.pdf.
> at the page 7,when i boot kernel.
> " qemu -m 32 -kernel
> /lab/linux-2.6.11.11/arch/i386/boot/bzImage -append
> "clock=pit root=/dev/hda" -hda
> /lab/linux/lab1/data/linux_i386.img -boot c"
> i meet the information:
> kernel panic -not syncing:no init found.
> try passing init=option to kernel."
> then i add a console device to root filesystem:
> mkdir /lab/rootfs
> cd ....../lab1
> mount -o loop data/linux_i386.img /lab/rootfs
> then
> i just copy /dev/console file to
> /lab/rootfs/dev.-----------though i can't find it in
> /lab/rootfs after i do that.
> and then i umount /lab/rootfs
> i meet the error:umount: /lab/rootfs: device is busy.
> Also ,i can't qeum kernel.
> who know the reason? explain it clearly!
>
>
>
next prev parent reply other threads:[~2005-09-05 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 9:13 [Qemu-devel] about qemu wfreshair
2005-09-05 16:00 ` André Braga [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-04 4:59 chandra shekar
2010-08-04 5:21 ` MJ embd
2010-08-10 5:17 chandra shekar
2010-08-10 14:16 ` Mulyadi Santosa
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=2ad73a05090509004ab97887@mail.gmail.com \
--to=meianoite@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 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).