On 12 June 2016 at 17:37, Alex Bligh wrote:
> My thesis is that's easier to emulate the KVM API and translate it
> to Hypervisor.Framework calls, than modify qemu everywhere so it
> calls Hypervisor.Framework everywhere directly, because there are
> so many calls to the KVM API.
I'm not entirely
On 6 Jun 2016, at 13:29, 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 g
Peter,
On 6 Jun 2016, at 13:43, Peter Maydell wrote:
> Not that I am aware of.
>
> Previous discussion:
> https://lists.gnu.org/archive/html/qemu-devel/2015-11/msg03086.html
Thanks. Missed that due to "Framwork" spelling!
--
Alex Bligh
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 t
On 6 June 2016 at 13:29, Alex Bligh wrote:
> Is anyone working on support for hypervisor.framework (OS-X's
> equivalent to kvm as far as I can see)?
Not that I am aware of.
Previous discussion:
https://lists.gnu.org/archive/html/qemu-devel/2015-11/msg03086.html
> If not, I might have a go in my
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
h
