From: Jack Mitchell <ml@communistcode.co.uk>
To: yocto@yoctoproject.org
Subject: QEMU nfs kernel panic
Date: Tue, 27 Sep 2011 10:05:00 +0100 [thread overview]
Message-ID: <4E8191BC.9030207@communistcode.co.uk> (raw)
I am using the stock sysroot and arm kernel zImage downloaded from the
yocto site. When I try to boot QEMU all is well until it tries to mount
the nfs root filesystem. It can't find it and the kernel panics, I have
set --debug all on in the runqemu-export-rootfs script but it throws no
further errors. Does anyone have any idea why it would do this, is it
possible that there is something wrong with the nfs implementation in
the kernel and the module is not loaded correctly, or is it more likely
that the nfs share isn't mounted on my machine and the kernel cannot
find it.
Screenshot of kernel panic: http://imgur.com/UbPTT
The only thing that jumps out at me is in the kernel boot up the rootfs
doesn't have a value as can be seen in the screenshot, but I don't know
if this is normal or not?
Cheers,
Jack.
next reply other threads:[~2011-09-27 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 9:05 Jack Mitchell [this message]
2011-09-27 12:05 ` QEMU nfs kernel panic Jack Mitchell
2011-09-27 15:07 ` Zhang, Jessica
2011-09-28 12:42 ` Jack Mitchell
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=4E8191BC.9030207@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=yocto@yoctoproject.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.