qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Programmingkid <magiccatsoftware@gmail.com>,
	Max Reitz <mreitz@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Mount image file feature
Date: Sat, 29 Aug 2015 17:04:58 -0600	[thread overview]
Message-ID: <55E23A9A.5060607@redhat.com> (raw)
In-Reply-To: <1DBD1CD3-3C0E-4AC6-97EB-FC51F09EF5F8@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 781 bytes --]

On 08/29/2015 11:36 AM, Programmingkid wrote:

>>
>>> Mac OS X is a second-class citizen in the QEMU world...
>>
>> Might have to do something with most (?) of it being non-free and Apple
>> not caring enough about KVM.
> 
> Fact, Apple has made an hypervisor API available as of Mac OS 10.10, so who
> knows. Maybe in the future someone will implement KVM support on Mac OS X.
> 
> Fact, Apple now gives away Mac OS X for free. Yes I know, it is only for Apple-only
> hardware still. 

No monetary cost is not the same as free.  Where can I get the source
code without being forced to agree to a non-free license, or forced to
buy particular hardware?

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  parent reply	other threads:[~2015-08-29 23:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27  1:05 [Qemu-devel] Mount image file feature G 3
2015-08-29 15:40 ` Max Reitz
2015-08-29 15:57   ` Programmingkid
2015-08-29 16:39     ` Max Reitz
2015-08-29 17:36       ` Programmingkid
2015-08-29 18:01         ` Max Reitz
2015-08-29 18:34           ` MagicCat Software
2015-08-29 19:34             ` Max Reitz
2015-08-29 20:06               ` Programmingkid
2015-08-29 23:10               ` Eric Blake
2015-08-30  0:02                 ` Programmingkid
2015-08-30  7:15                   ` Paolo Bonzini
2015-08-29 19:52             ` Max Reitz
2015-08-29 20:18               ` Programmingkid
2015-08-29 23:12                 ` Eric Blake
2015-08-29 23:31                   ` Programmingkid
2015-08-29 23:04         ` Eric Blake [this message]
2015-08-30  0:03           ` MagicCat Software
2015-08-31  8:02             ` Markus Armbruster
2015-08-30  6:47         ` Paolo Bonzini
2015-08-31  3:47           ` Programmingkid
2015-08-31  7:52         ` Markus Armbruster
2015-08-31 13:12           ` Programmingkid
2015-08-31 16:26             ` Markus Armbruster
2015-08-31 18:29               ` Programmingkid
2015-08-30  6:42       ` Paolo Bonzini
2015-08-31 20:13       ` Programmingkid
2015-08-31 20:26         ` Max Reitz
2015-08-31 20:33           ` Programmingkid
2015-09-02 14:31             ` Max Reitz
2015-09-02 14:38               ` Programmingkid
2015-09-03  9:46                 ` Markus Armbruster
2015-09-03 14:24                   ` Programmingkid
2015-09-03 16:26                     ` Markus Armbruster
2015-09-03 16:51                       ` Programmingkid
2015-09-03  9:34               ` Markus Armbruster

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=55E23A9A.5060607@redhat.com \
    --to=eblake@redhat.com \
    --cc=magiccatsoftware@gmail.com \
    --cc=mreitz@redhat.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).