From: Jack Mitchell <ml@communistcode.co.uk>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: QEMU nfs kernel panic
Date: Wed, 28 Sep 2011 13:42:57 +0100 [thread overview]
Message-ID: <4E831651.5030802@communistcode.co.uk> (raw)
In-Reply-To: <C6510F6D410BB64A8C15398EDC6B847C16E848CE@ORSMSX101.amr.corp.intel.com>
On 27/09/2011 16:07, Zhang, Jessica wrote:
> Hi Jack,
>
> The minimal-dev image doesn't contain tcf-agent which is needed for any remote interaction. So can you build core-image-sato-sdk image and use it to boot up qemu, then your problem will be solved.
>
> Thanks,
> Jessica
>
> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Jack Mitchell
> Sent: Tuesday, September 27, 2011 5:05 AM
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] QEMU nfs kernel panic
>
> On 27/09/2011 10:05, Jack Mitchell wrote:
>> 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.
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> Ok, I managed to fix it. I needed to load the tun module to get it
> working. Maybe this should be added as a check in runqemu?
>
> I am now having issues with connecting to the live image, I recieve a
> connection refused message when I try to upload the file to the virtual
> machine, I have just the stick minimal-dev image so no additional
> passwords set.
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
Thank you Jessica, that solved my problem of being unable to connect to
the virtual machine.
Regards,
Jack.
prev parent reply other threads:[~2011-09-28 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 9:05 QEMU nfs kernel panic Jack Mitchell
2011-09-27 12:05 ` Jack Mitchell
2011-09-27 15:07 ` Zhang, Jessica
2011-09-28 12:42 ` Jack Mitchell [this message]
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=4E831651.5030802@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.