[Qemu-devel] about qemu

[Qemu-devel] about qemu

[wfreshair]

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

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! 
 

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

Re: [Qemu-devel] about qemu

[André Braga]

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! 
> 
> 
>

[Qemu-devel] about qemu

[chandra shekar]

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

hi iam chandra i am interested in understanding the qemu code  can any one
help me from where i have to start
and also i installed qemu on ubuntu 10.04 after installing when i run qemu
as per instruction given in qemu web page
it says vnc server running on some ip and thats it can please some one help
me,thanks

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

Re: [Qemu-devel] about qemu

[MJ embd]

start from vl.c, main()

-mj

On Wed, Aug 4, 2010 at 10:29 AM, chandra shekar
<chandrashekar512@gmail.com> wrote:
> hi iam chandra i am interested in understanding the qemu code  can any one
> help me from where i have to start
> and also i installed qemu on ubuntu 10.04 after installing when i run qemu
> as per instruction given in qemu web page
> it says vnc server running on some ip and thats it can please some one help
> me,thanks
>



-- 
-mj

[Qemu-devel] about qemu

[chandra shekar]

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

can any one suggest any study materials for start learning  qemu and its
internals
i have already read the documentation in this qemu web page other than that
any
other materials,thanks

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

Re: [Qemu-devel] about qemu

[Mulyadi Santosa]

On Tue, Aug 10, 2010 at 12:17, chandra shekar
<chandrashekar512@gmail.com> wrote:
> can any one suggest any study materials for start learning  qemu and its
> internals
> i have already read the documentation in this qemu web page other than that
> any
> other materials,thanks
>

I am afraid, the other thing left to try is just read the code and
explore them. Running qemu under gdb (i mean qemu itself) might
help...

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com