[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] HAXM is now open source

From: Thomas Huth
Subject: Re: [Qemu-devel] HAXM is now open source
Date: Tue, 14 Nov 2017 12:09:00 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0

On 14.11.2017 09:54, Yu Ning wrote:
> Hello,
> As some of you may have noticed, since QEMU 2.9.0, an accelerator known
> as “hax” has been available for Windows and macOS builds of QEMU, thanks
> to the hard work of Vincent Palatin and help from this community (Paolo
> Bonzini, Stefan Weil, et al.).
> The accelerator requires a host kernel module (driver) known as Intel
> Hardware Accelerated Execution Manager (HAXM), i.e. intelhaxm.sys on
> Windows or intelhaxm.kext on macOS, similar to how the KVM accelerator
> depends on kvm.ko on Linux.
> Today, we released the source code of the HAXM kernel module under the
> BSD 3-clause license:
> https://github.com/intel/haxm
> We look forward to working with the community to improve HAXM (both the
> kernel module and the accelerator). The code is accompanied by some
> basic documentation (README.md and API.md), which is incomplete, but
> hopefully helps people get started. If you have any questions or
> suggestions, please create an issue or post a comment on GitHub.

That's great news! I hope this all will help to promote QEMU on Windows
and macOS quite a bit!

However, during the past months, I noticed a couple of times that users
ask on IRC or the qemu-discuss mailing list how they could accelerate
their QEMU on Windows - and they are running only in TCG mode when you
ask how they start QEMU. So it seems like there is not much knowledge
about "--accel hax" in the public yet. Maybe you could write a nice blog
post for the QEMU blog or something similar that explains how to use
HAXM with QEMU on Windows for the normal users? Or maybe make it more
prominent in the QEMU wiki? (e.g. the main page only mentions KVM and
Xen, but not HAXM)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]