From: Torbjorn Granlund <tg@gmplib.org>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Which qemu ports actually work?
Date: Tue, 26 Oct 2010 21:12:45 +0200 [thread overview]
Message-ID: <86mxq022fm.fsf@shell.gmplib.org> (raw)
In-Reply-To: <4CC715B7.6090100@mail.berlios.de> (Stefan Weil's message of "Tue\, 26 Oct 2010 19\:53\:59 +0200")
Stefan Weil <weil@mail.berlios.de> writes:
Which kind of host did you use? i386? x86_64? Linux? Windows?
FreeBSD 8.1-p1 x86_64 (the CPU is AMD Phenom X6).
I use the kqemu kernel module. All software (kernel, /usr/ports) are
up-to-date as of yesterday.
My working setups run on a Debian Linux (x86_64) host
(most were also tested sucessfully on a Debian Linux (i386) host).
It would be useful if somebody published the tricks they use to get an
OS to run. "It works for me" might make people do more trial-and-error,
but it might not make them lucky.
Debian Linux i386, x86_64, arm, mips, mips64, ppc guests work.
I haven't tried arm and made just one futile attempt with mips (mips
wants a bios file I have yet to locate).
Are you willing to share your setups with me? Even better, publish them
in such a way that people will easily find them? Now, google seems
better at finding how qemu fails than how it succeeds...
Obviously many developers use similar setups, so they are well tested
and debugged.
I am glad to hear this!
--
Torbjörn
next prev parent reply other threads:[~2010-10-26 19:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 16:38 [Qemu-devel] Which qemu ports actually work? Torbjorn Granlund
2010-10-26 17:13 ` Alexander Graf
2010-10-26 19:02 ` Torbjorn Granlund
2010-10-26 19:25 ` Alexander Graf
2010-10-26 19:52 ` Torbjorn Granlund
2010-10-27 5:06 ` Alexander Graf
2010-10-27 8:39 ` Torbjorn Granlund
2010-10-27 8:51 ` Alexander Graf
2010-10-27 9:21 ` Torbjorn Granlund
2010-10-27 9:24 ` Alexander Graf
2010-10-27 9:33 ` Torbjorn Granlund
2010-10-27 9:31 ` [Qemu-devel] " Paolo Bonzini
2010-10-28 8:32 ` [Qemu-devel] " Torbjorn Granlund
2010-10-28 20:00 ` Alexander Graf
2010-10-27 20:44 ` Blue Swirl
2010-10-27 22:39 ` Torbjorn Granlund
2010-10-28 8:57 ` Artyom Tarasenko
2010-10-28 9:37 ` Torbjorn Granlund
2010-10-28 10:41 ` Artyom Tarasenko
2010-10-26 19:34 ` [Qemu-devel] " Paolo Bonzini
2010-10-26 21:02 ` Stefan Weil
2010-10-26 17:53 ` [Qemu-devel] " Stefan Weil
2010-10-26 19:12 ` Torbjorn Granlund [this message]
2010-10-26 19:35 ` [Qemu-devel] " Paolo Bonzini
2010-10-26 20:07 ` Torbjorn Granlund
2010-10-26 20:54 ` Stefan Weil
2010-10-26 21:11 ` Torbjorn Granlund
2010-10-26 21:09 ` Paolo Bonzini
2010-10-26 18:19 ` [Qemu-devel] Which qemu targets actually work? (was: Which qemu ports actually work?) Andreas Färber
2010-10-26 18:25 ` [Qemu-devel] Which qemu ports actually work? Blue Swirl
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=86mxq022fm.fsf@shell.gmplib.org \
--to=tg@gmplib.org \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).