From: Richard Pennington <rich@pennware.com>
To: musl@lists.openwall.com
Subject: Re: Test environment for non-native archs
Date: Sun, 27 May 2012 06:54 -0500 [thread overview]
Message-ID: <1445612.NTLIVY7KuE@main.pennware.com> (raw)
In-Reply-To: <20120527031840.GC163@brightrain.aerifal.cx>
On Saturday, May 26, 2012 11:18:40 PM Rich Felker wrote:
> Hi,
>
> I've been thinking a bit about further testing of ARM (for which I
> don't have a native environment) and ports to other systems, and
> realized that to be able to efficiently mix working on the native host
> and virtual target system (e.g. doing most of the compiling on the
> host), it's going to be desirable to have the Linux running under qemu
> using part of the host's filesystem as its root fs, instead of having
> a filesystem image.
>
> This seems to be possible with qemu's support for exporting a virtual
> 9p share to the guest OS, but I haven't yet determined if it's
> possible to boot directly with the 9p share as the root fs, or whether
> it's going to require a separate initial fs image and switch/pivot
> root afterwards (as you can tell, I'm not very familiar with this sort
> of setup).
>
> Anyone know the answer, or have some recipes I could use?
>
> Rich
Hi Rich,
For my testing (which musl for ARM just passed, by the way ;-), I mostly use
QEMU in Linux user space emulation mode. I just compile an executable on my
x86 system and run it:
qemu-arm a.out arg1 arg2 ...
In fact, my system is configured to recognize an arm executable and run qemu-
arm automatically, which is kind of slick.
When I do run a full blown system VM, I just nfs mount directories on my main
system that I'm interested in.
-Rich
next prev parent reply other threads:[~2012-05-27 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 3:18 Rich Felker
2012-05-27 11:54 ` Richard Pennington [this message]
2012-05-27 13:11 ` Rich Felker
2012-05-29 2:03 ` Roy Tam
2012-05-29 2:45 ` Rich Felker
2012-06-03 11:15 ` aep
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=1445612.NTLIVY7KuE@main.pennware.com \
--to=rich@pennware.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).