From: Dekar <Dekar@wc3edit.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] How to get a shell to work with in user mode?
Date: Wed, 04 Feb 2009 08:22:53 +0100 [thread overview]
Message-ID: <4989424D.4070905@wc3edit.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi, took me a while to get qemu compiled... My host is x86 my guest ARM.
I was playing with qemu in a chroot environment and it seemed to work
quite well after I put the static
linked qemu in the chroot and switched to to running a bash using it.
Then I found out that it switched
back to executing x86er binaries while in the chroot. So I have to run
qemu-arm every time I want to run
an ARM binary inside my ARM chroot. This behavior makes it impossible
to execute shell scripts.
Is there anyway to make qemu hook in the bash and automatically run
binaries? It would be awesome
to have qemu working in a chroot environment without the need to load
another kernel.
greets Elias Önal
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkmJQkkACgkQvmkQVSIBO6xgQQCeNQmdIY+ZR/ND8Vn9b6RCY30l
yEYAoJ2EeA3fCRs1RMxQjb/AygpHh0Zi
=xACA
-----END PGP SIGNATURE-----
reply other threads:[~2009-02-04 7:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4989424D.4070905@wc3edit.net \
--to=dekar@wc3edit.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).