qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Fam Zheng <famz@redhat.com>,
	"qemu-devel@nongnu.org qemu-devel" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 28/36] tests: Add ubuntu.i386 image
Date: Mon, 25 Sep 2017 09:57:26 +0100	[thread overview]
Message-ID: <20170925085726.GD20236@redhat.com> (raw)
In-Reply-To: <BA02424C-0C79-4FAE-B191-18A9D0CDBAC8@gmail.com>

On Fri, Sep 22, 2017 at 04:26:40PM -0400, Programmingkid wrote:
> 
> > On Sep 22, 2017, at 9:18 AM, Daniel P. Berrange <berrange@redhat.com> wrote:
> > 
> > On Fri, Sep 22, 2017 at 08:44:05PM +0800, Fam Zheng wrote:
> >> On Fri, 09/22 08:10, Programmingkid wrote:
> >>> Could a Darwin test be added? Both x86 and PowerPC versions would be great.
> >> 
> >> It's nice to cover macOS in our test, but to be honest I don't know how to do
> >> it. If there isn't any copyright problem, and if there are instructions
> >> available in wiki.qemu.org descirbing how to create such a guest step by step
> >> like [1], we can add one.
> > 
> > AFAICT we can not just provide or host OS-X images and let individual
> > devs run the without it being a license violation, so best avoided.
> 
> Actually Darwin and Mac OS X are not the same. Darwin is this minimalistic
> environment and Mac OS X is built on top of that environment. There would
> be no license problems when using Darwin only.

I looked for images of Darwin but haven't been able to find any modern
ones. Wikipedia claims that Apple stopped releasing installable images
of Darwin so you have to build it from source :-(

> > IMHO it easier to just rely on Travis' OS-X builders for testing OS-X
> > platform builds, so that licensing compliance is their responsibility.
> 
> That might work for the x86 version of Mac OS X, but there doesn't appear
> to be any support for the PowerPC version of Mac OS X.

Yeah, no PPC support, but then that's essentially a dead platform, so it
is questionable whether we need to care about OS-X PPC support for QEMU.
The last PPC OS-X hardware shipped 2006.

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 :|

  reply	other threads:[~2017-09-25  8:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3351.1506066493.14747.qemu-devel@nongnu.org>
2017-09-22 12:10 ` [Qemu-devel] [PULL 28/36] tests: Add ubuntu.i386 image Programmingkid
2017-09-22 12:44   ` Fam Zheng
2017-09-22 13:18     ` Daniel P. Berrange
2017-09-22 20:26       ` Programmingkid
2017-09-25  8:57         ` Daniel P. Berrange [this message]
2017-09-25 13:50           ` Programmingkid
2017-09-22 20:22     ` Programmingkid
2017-09-25  7:31       ` Gerd Hoffmann
2017-09-25  8:51         ` Daniel P. Berrange
2017-09-22  7:46 [Qemu-devel] [PULL v5 00/36] Build and test automation patches Fam Zheng
2017-09-22  7:46 ` [Qemu-devel] [PULL 28/36] tests: Add ubuntu.i386 image Fam Zheng

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=20170925085726.GD20236@redhat.com \
    --to=berrange@redhat.com \
    --cc=famz@redhat.com \
    --cc=programmingkidx@gmail.com \
    --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).