All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] OS-X hypervisor.framework support
Date: Mon, 6 Jun 2016 13:44:08 +0100	[thread overview]
Message-ID: <20160606124408.GE5581@redhat.com> (raw)
In-Reply-To: <1F033B05-8C35-4975-8790-C4E09048F4C4@alex.org.uk>

On Mon, Jun 06, 2016 at 01:29:47PM +0100, Alex Bligh wrote:
> Is anyone working on support for hypervisor.framework (OS-X's equivalent to kvm as far as I can see)?
> 
> If not, I might have a go in my copious spare time (cough) and if anyone would be interesting in helping, or giving advice that would be great.
> 
> I note that:
>   https://github.com/mist64/xhyve
> 
> has support for this, and its license is described as "BSD" (that's it). Is that Qemu GPL compatible? Though I suspect a clean implementation may be easier.

The source code file headers show a standard 2-clause BSD, which is
compatible with the GPL. So it is fine to incorporate BSD licensed
code in QEMU, as long as you preserve attribution & copyright notices

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  parent reply	other threads:[~2016-06-06 12:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 12:29 [Qemu-devel] OS-X hypervisor.framework support Alex Bligh
2016-06-06 12:43 ` Peter Maydell
2016-06-06 12:55   ` Alex Bligh
2016-06-06 12:44 ` Daniel P. Berrange [this message]
2016-06-12 16:37 ` Alex Bligh
2016-06-12 22:07   ` Peter Maydell

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=20160606124408.GE5581@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex@alex.org.uk \
    --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.