From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Michele Denber <mdenber@gmx.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU on Solaris
Date: Mon, 13 Aug 2018 09:34:08 +0100 [thread overview]
Message-ID: <20180813083408.GG22904@redhat.com> (raw)
In-Reply-To: <5B7054D9.9000209@gmx.com>
On Sun, Aug 12, 2018 at 11:40:09AM -0400, Michele Denber wrote:
> After configuring QEMU on my Sun I got this message:
>
> "Host OS SunOS support is not currently maintained.
> The QEMU project intends to remove support for this host OS in
> a future release if nobody volunteers to maintain it and to
> provide a build host for our continuous integration setup.
> configure has succeeded and you can continue to build, but
> if you care about QEMU on this platform you should contact
> us upstream at qemu-devel@nongnu.org."
>
> Well I do care about QEMU on my platform so I'd like to volunteer to provide
> a host for support. I can provide you with a free account on my Sun Oracle
> Enterprise M3000 quad-core 2.75 GHz. SPARC64 VII running Solaris 10 Update
> 11. I've got plenty of spare CPU cycles and lots of free disk. Please let
> me know.
Copying Peter, as he would need access to a Solaris host to do GIT pre-merge
build testing.
Then there's the question of what ordinary developers would use for their own
testing if they needed to work on some portability issue. We've got support
in tree for running builds against VM images for the various *BSDs, and have
mingw cross build toolchain for Windows. Is it possible to provide free-to-use
VM disk images for Solaris build testing, or are software licensing requirements
going to get in the way of developers using them ?
There is OpenIndiana that forked off OpenSolaris, but I'm unclear how far
OpenIndiana and commercial Solaris have diverged since then ?
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-08-13 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-12 15:40 [Qemu-devel] QEMU on Solaris Michele Denber
2018-08-13 8:34 ` Daniel P. Berrangé [this message]
2018-08-13 10:08 ` Peter Tribble
2018-08-13 10:20 ` Peter Maydell
2018-08-13 19:23 ` Michele Denber
2018-08-13 19:13 ` Michele Denber
-- strict thread matches above, loose matches on Subject: below --
2010-03-04 2:24 [Qemu-devel] qemu " Seth G
2010-03-04 6:22 ` Jonathan Kalbfeld
2010-03-04 6:39 ` Seth Goldberg
2010-03-06 7:11 ` 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=20180813083408.GG22904@redhat.com \
--to=berrange@redhat.com \
--cc=mdenber@gmx.com \
--cc=peter.maydell@linaro.org \
--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).