All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Torbjorn Granlund <tg@gmplib.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Which qemu ports actually work?
Date: Tue, 26 Oct 2010 19:53:59 +0200	[thread overview]
Message-ID: <4CC715B7.6090100@mail.berlios.de> (raw)
In-Reply-To: <86sjzssydf.fsf@shell.gmplib.org>

Am 26.10.2010 18:38, schrieb Torbjorn Granlund:
> I am not sure this inquiry is appropriate for this mailing list. But at
> the qemu web site, this is the only mailing list mentioned.
>
> I would like to run as many OS's as possible under as many processors as
> possible, using qemu. Results thus far has not been very encouraging,
> though.
>
> Here is my test matrix:
>
> fbsd-8_1 nbsd-5_0_2 debian-5 gentoo hurd
>
> sparc n/a OK n/a n/a n/a
>
> sparc64 fw crash fw crash kern crash black fb n/a
>
> ppc early hang fw crash OK kern hang n/a
>
> ppc64 early panic fw crash kern hang kern hang n/a
>
> i386 OK OK OK installs,
> non-booting
> x86_64 OK OK OK
>
> These are results from multiple attempts and google searches for what
> other people have done. Unfortunately, there aren't many matches,
> except that the various error messages I get have been experienced by
> several other people.
>
> Is this what I can expect from qemu today? Are the goals of the qemu
> project to make the various ports operational for running these OS's?
> If yes, what is the time frame?
>
> It would be nice with a status page (there is a blank such page already,
> I mean a non-blank page...) informing about the status of the various
> ports. A naive user--such as myself--tends to assume that a released
> port actually works. It takes many hours of poorly used effort before
> one can conclude that e.g., sparc64 does not work at all.
>
> (We should probably not blame qemu for hurd's shortcomings here. Hurd
> is highly experimental. I have not tried it on actual hardware.)


Which kind of host did you use? i386? x86_64? Linux? Windows?

My working setups run on a Debian Linux (x86_64) host
(most were also tested sucessfully on a Debian Linux (i386) host).

Debian Linux i386, x86_64, arm, mips, mips64, ppc guests work.
Obviously many developers use similar setups, so
they are well tested and debugged.

Regards,
Stefan Weil

  parent reply	other threads:[~2010-10-26 17:55 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 ` Stefan Weil [this message]
2010-10-26 19:12   ` [Qemu-devel] " Torbjorn Granlund
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=4CC715B7.6090100@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=qemu-devel@nongnu.org \
    --cc=tg@gmplib.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.