From: Stefan Weil <weil@mail.berlios.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEMU Automated Testing
Date: Sat, 28 Jul 2007 14:43:16 +0200 [thread overview]
Message-ID: <46AB39E4.2040106@mail.berlios.de> (raw)
In-Reply-To: <46AB2B87.2030305@gmail.com>
QEMU can build and run on a MIPS32 host - it just needs a few patches
(which were already sent to the list but got lost in CVS head).
The patched sources I use to run QEMU MIPS Malta with Debian stable
inside of a QEMU Malta emulation on x86 hardware are available from URL
http://svn.berlios.de/viewcvs/ar7-firmware/qemu/branches/head/
Use this command to get them:
svn checkout
http://svn.berlios.de/svnroot/repos/ar7-firmware/qemu/branches/head/
Any combination of big and little endian works with pcnet32:
qemu-system-mipsel in qemu-system-mips,
qemu-system-mipsel in qemu-system-mipsel,
qemu-system-mips in qemu-system-mips,
qemu-system-mips in qemu-system-mipsel.
Other network emulations only work with some of these combinations.
User mode emulation won't work, but it does not work on any
platform - not even x86.
I did not check MIPS64 emulation.
Stefan
> Do you have any idea of what else is needed to get QEMU to a usable
> state on
> MIPS hosts? Are there any other ideas for virtualisation such as Xen
> or VMware/
> SimOS? I have asked on the Xen-devel list but nobody gave any feedback
> there.
next prev parent reply other threads:[~2007-07-28 12:43 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-07 18:14 [Qemu-devel] qemu Makefile.target vl.h hw/acpi.c hw/adlib.c Paul Brook
2007-04-07 18:32 ` J. Mayer
2007-04-07 19:10 ` Paul Brook
2007-04-07 19:32 ` Blue Swirl
2007-04-07 19:46 ` Paul Brook
2007-04-07 20:28 ` J. Mayer
2007-04-07 20:45 ` Paul Brook
2007-04-07 22:18 ` J. Mayer
2007-04-07 22:49 ` Thiemo Seufer
2007-04-07 23:13 ` Paul Brook
2007-04-07 23:54 ` J. Mayer
2007-04-08 0:04 ` Thiemo Seufer
2007-04-08 7:49 ` IRQ handling (was [Qemu-devel] qemu Makefile.target vl.h hw/acpi.c hw/adlib.c ...) J. Mayer
2007-04-08 8:38 ` J. Mayer
2007-04-08 14:41 ` Thiemo Seufer
2007-04-08 16:31 ` J. Mayer
2007-04-08 20:43 ` QEMU Automated Testing " Natalia Portillo
2007-04-08 22:07 ` Eduardo Felipe
2007-04-08 23:53 ` Natalia Portillo
2007-04-09 9:36 ` Eduardo Felipe
2007-04-09 21:19 ` Rob Landley
2007-04-10 11:24 ` Jamie Lokier
2007-04-10 12:00 ` Pierre d'Herbemont
2007-07-27 14:21 ` Dan Shearer
2007-07-27 14:29 ` Anthony Liguori
2007-07-27 14:34 ` Dan Shearer
2007-07-27 14:58 ` Sunil Amitkumar Janki
2007-07-27 15:12 ` Dan Shearer
2007-07-27 15:50 ` Sunil Amitkumar Janki
2007-07-27 16:04 ` Dan Shearer
2007-07-27 16:50 ` Jan Marten Simons
2007-07-27 18:51 ` Thiemo Seufer
2007-07-27 19:55 ` Sunil Amitkumar Janki
2007-07-28 10:17 ` Thiemo Seufer
2007-07-28 11:41 ` Sunil Amitkumar Janki
2007-07-28 12:43 ` Stefan Weil [this message]
2007-07-27 18:54 ` Andreas Färber
2007-07-28 10:36 ` Thiemo Seufer
2007-07-29 15:31 ` Andreas Färber
2007-04-10 11:17 ` IRQ handling " Jamie Lokier
2007-04-09 0:41 ` [Qemu-devel] Re: IRQ handling Paul Brook
2007-04-09 11:11 ` J. Mayer
2007-04-09 13:58 ` Paul Brook
2007-04-09 14:56 ` J. Mayer
2007-04-09 16:57 ` Paul Brook
2007-04-07 23:26 ` [Qemu-devel] qemu Makefile.target vl.h hw/acpi.c hw/adlib.c Fabrice Bellard
2007-04-08 13:06 ` Wang Cheng Yeh
2007-04-08 13:56 ` Thiemo Seufer
2007-04-08 22:45 ` Paul Brook
2007-04-07 21:20 ` Thiemo Seufer
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=46AB39E4.2040106@mail.berlios.de \
--to=weil@mail.berlios.de \
--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 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.