Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] qemu-native: depend on unfs-server-native
Date: Wed, 2 May 2012 16:37:44 -0500	[thread overview]
Message-ID: <4FA1A928.20309@windriver.com> (raw)
In-Reply-To: <965C6250-6D1E-438E-8207-1E1D9DAF398A@dominion.thruhere.net>

On 05/02/2012 09:44 AM, Koen Kooi wrote:
> Op 2 mei 2012, om 16:33 heeft Jason Wessel het volgende geschreven:
>
>> On 05/02/2012 09:29 AM, Koen Kooi wrote:
>>> Op 2 mei 2012, om 16:23 heeft Jason Wessel het volgende geschreven:
>>>
>>>> The user mode NFS server does not get built by default when you are
>>>> using a purely command line driven development environment without SDK
>>>> tools.  In order to accommodate simple test configurations and have
>>>> all the tools built for the minimal validation with qemu-native,
>>>> simply add the dependency to unfs-server-native.
>>> So all images I build for e.g. qemux86 now have an nfs-server? Can we please move settings like that to the specific images?
>>>
>> This is part of the simulation environment.  Not all of the run qemu functionality works correctly without this.
> I repeat:  Can we please move settings like that to the specific images?
>
> I don't need nor want nfs servers in the images I build for qemu. And they work just fine without it.

Are you advocating that you really want to make the system harder to use where somethings just do not work out of the box for no obvious reason?   I realize that for your particular use case everything works fine, or you would be submitting patches to fix it.

The qemux86 appears to be a very generic BSP aimed at having an easy to use simulation environment.  If you build a minimal image it would seem that it should work for all the the runqemu boot methods out of the box with no additional steps.

If your BSP has no simulator, you will not be building QEMU and in theory, this is not an issue.

Example of what happens today:

1) . ../oe-init-build-env
2) bitbake core-image-minimal
3) runqemu-extract-sdk tmp/deploy/images/core-image-minimal-qemux86.tar.bz2 nfs
4) runqemu qemux86 nographic `pwd`/nfs
--- And now the error ---
Error: Unable to find rpc.mountd binary in /opt/poky/scratch/build/tmp/sysroots/x86_64-linux/usr/sbin/
--------------------------------


If you are in absolute disagreement with this patch, please suggest a way to accomplish the same thing with the same number of steps or fewer.  Arguably, I'd like to even go a step further and reduce this to 3 steps where the runqemu can auto extract the NFS root on demand if it is not already there.

It seems that the runqemu could also be modified to allow you to choose slirp networking such that no root access is needed at all for invoking the simulation.  All such changes are aimed at simplistic generic use of the generated images.

Cheers,
Jason.



  reply	other threads:[~2012-05-02 21:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02 14:23 [PATCH] qemu-native: depend on unfs-server-native Jason Wessel
2012-05-02 14:29 ` Koen Kooi
2012-05-02 14:32   ` Martin Jansa
2012-05-02 14:33   ` Jason Wessel
2012-05-02 14:44     ` Koen Kooi
2012-05-02 21:37       ` Jason Wessel [this message]
2012-05-03  7:22         ` Koen Kooi
2012-05-02 21:49       ` Phil Blundell
2012-05-02 22:06         ` Mark Hatle
2012-05-02 22:12         ` Jason Wessel
2012-05-03  7:32 ` Khem Raj
2012-05-03  7:43   ` Koen Kooi
2012-05-03  8:47     ` Richard Purdie
2012-05-03 10:39       ` Koen Kooi
2012-05-03 10:57         ` Jason Wessel
2012-05-03 11:24         ` Richard Purdie
2012-05-03 11:39           ` Koen Kooi
2012-05-03 11:51             ` Richard Purdie
2012-05-04  6:13               ` Koen Kooi
2012-05-04  6:32                 ` Martin Jansa
2012-05-04  6:50                   ` Koen Kooi
2012-05-04  9:32                     ` Richard Purdie

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=4FA1A928.20309@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.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