Announcement of aborting HAXM maintenance

Announcement of aborting HAXM maintenance

[Wang, Wenchao]

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

Hi, Philippe,

Intel decided to abort the development of HAXM and the maintenance of its QEMU part. Should we submit a patch to mark the Guest CPU Cores (HAXM) status as Orphan and remove the maintainers from the corresponding list? Meanwhile, should the code enabling HAX in QEMU once committed by the community be retained?
You may ignore the patch I submitted two months ago. Please do not merge it into QEMU. The HAXM final release can support any QEMU version, and the functionality of the current software are normally available without known security vulnerabilities. Thanks for your support.


Best Regards,
Wenchao


[-- Attachment #2: Type: text/html, Size: 2308 bytes --]

Re: Announcement of aborting HAXM maintenance

[Daniel P. Berrangé]

On Thu, Jan 19, 2023 at 03:56:04AM +0000, Wang, Wenchao wrote:
> Hi, Philippe,
> 
> Intel decided to abort the development of HAXM and the maintenance
> of its QEMU part. Should we submit a patch to mark the Guest CPU
> Cores (HAXM) status as Orphan and remove the maintainers from the
> corresponding list? Meanwhile, should the code enabling HAX in QEMU
> once committed by the community be retained?

If you no longer intend to work on QEMU bits related to HAXM, then
yes, you should send a patch for the MAINTAINERS file to remove you
name and mark it as "Orphan" status.

We would not normally delete code from QEMU, merely because it has
been orphaned. If it is still known to work then we would retain
it indefinitely, unless some compelling reason arises to drop it.
This gives time for any potential users to adjust their plans,
and/or opportunity for other interested people to take over the
maintenance role.

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

Re: Announcement of aborting HAXM maintenance

[Stefan Weil via]

Am 19.01.23 um 11:12 schrieb Daniel P. Berrangé:
> On Thu, Jan 19, 2023 at 03:56:04AM +0000, Wang, Wenchao wrote:
>> Hi, Philippe,
>>
>> Intel decided to abort the development of HAXM and the maintenance
>> of its QEMU part. Should we submit a patch to mark the Guest CPU
>> Cores (HAXM) status as Orphan and remove the maintainers from the
>> corresponding list? Meanwhile, should the code enabling HAX in QEMU
>> once committed by the community be retained?
> 
> If you no longer intend to work on QEMU bits related to HAXM, then
> yes, you should send a patch for the MAINTAINERS file to remove you
> name and mark it as "Orphan" status.
> 
> We would not normally delete code from QEMU, merely because it has
> been orphaned. If it is still known to work then we would retain
> it indefinitely, unless some compelling reason arises to drop it.
> This gives time for any potential users to adjust their plans,
> and/or opportunity for other interested people to take over the
> maintenance role.

HAXM will not only be no longer maintained in QEMU, but also the 
necessary framework for macOS and Windows will be retired. See 
https://github.com/intel/haxm#status on their GitHub page. As stated 
there, macOS provides HVF which can be used instead of HAXM, and Windows 
users can use WHPX. Both HVF and WHPX are supported by QEMU. As far as I 
know HAXM could only provide a limited RAM size (2 GiB?). Maybe it still 
has more deficits. And unmaintained HAXM drivers for macOS and Windows 
might be a security risk, too. It is also not clear whether the last 
downloads of those drivers will be available in the future.

Therefore I'd prefer to remove the whole HAXM code in QEMU soon, even in 
a minor update for this special case.

Stefan

Re: Announcement of aborting HAXM maintenance

[Peter Maydell]

On Thu, 19 Jan 2023 at 10:34, Stefan Weil via <qemu-devel@nongnu.org> wrote:
>
> Am 19.01.23 um 11:12 schrieb Daniel P. Berrangé:
> > On Thu, Jan 19, 2023 at 03:56:04AM +0000, Wang, Wenchao wrote:
> >> Hi, Philippe,
> >>
> >> Intel decided to abort the development of HAXM and the maintenance
> >> of its QEMU part. Should we submit a patch to mark the Guest CPU
> >> Cores (HAXM) status as Orphan and remove the maintainers from the
> >> corresponding list? Meanwhile, should the code enabling HAX in QEMU
> >> once committed by the community be retained?
> >
> > If you no longer intend to work on QEMU bits related to HAXM, then
> > yes, you should send a patch for the MAINTAINERS file to remove you
> > name and mark it as "Orphan" status.
> >
> > We would not normally delete code from QEMU, merely because it has
> > been orphaned. If it is still known to work then we would retain
> > it indefinitely, unless some compelling reason arises to drop it.
> > This gives time for any potential users to adjust their plans,
> > and/or opportunity for other interested people to take over the
> > maintenance role.
>
> HAXM will not only be no longer maintained in QEMU, but also the
> necessary framework for macOS and Windows will be retired. See
> https://github.com/intel/haxm#status on their GitHub page. As stated
> there, macOS provides HVF which can be used instead of HAXM, and Windows
> users can use WHPX. Both HVF and WHPX are supported by QEMU. As far as I
> know HAXM could only provide a limited RAM size (2 GiB?). Maybe it still
> has more deficits. And unmaintained HAXM drivers for macOS and Windows
> might be a security risk, too. It is also not clear whether the last
> downloads of those drivers will be available in the future.
>
> Therefore I'd prefer to remove the whole HAXM code in QEMU soon, even in
> a minor update for this special case.

This sounds like an argument for putting it through our usual
deprecate-and-drop lifecycle.

thanks
-- PMM

RE: Announcement of aborting HAXM maintenance

[Wang, Wenchao]

Hi, Daniel,

Thanks for your reply. Could you please help to merge below attached patch to update the status of HAXM in QEMU? Thanks a lot.


Best Regards,
Wenchao

----------
From d88ba9ab3e32c991566443f3b52c45de67bf10c8 Mon Sep 17 00:00:00 2001
From: Wenchao Wang <wenchao.wang@intel.com>
Date: Thu, 19 Jan 2023 20:08:37 +0800
Subject: [PATCH] MAINTAINERS: Abort HAXM maintenance

Abort the maintenance of Guest CPU Cores (HAXM).

* Clean up the maintainer list of X86 HAXM CPUs
* Remove the web page URL and the mailing list
* Change the status to Orphan

Reviewed-by: Hang Yuan <hang.yuan@intel.com>
Signed-off-by: Wenchao Wang <wenchao.wang@intel.com>
---
 MAINTAINERS | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 0fe50d01e3..0950061dc4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -500,10 +500,7 @@ F: stubs/xen-hw-stub.c
 Guest CPU Cores (HAXM)
 ---------------------
 X86 HAXM CPUs
-M: Wenchao Wang <wenchao.wang@intel.com>
-L: haxm-team@intel.com
-W: https://github.com/intel/haxm/issues
-S: Maintained
+S: Orphan
 F: accel/stubs/hax-stub.c
 F: include/sysemu/hax.h
 F: target/i386/hax/
-- 
2.17.1


-----Original Message-----
From: Daniel P. Berrangé <berrange@redhat.com> 
Sent: Thursday, January 19, 2023 18:12
To: Wang, Wenchao <wenchao.wang@intel.com>
Cc: Philippe Mathieu-Daudé <philmd@linaro.org>; Thomas Huth <thuth@redhat.com>; Paolo Bonzini <pbonzini@redhat.com>; qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Announcement of aborting HAXM maintenance

On Thu, Jan 19, 2023 at 03:56:04AM +0000, Wang, Wenchao wrote:
> Hi, Philippe,
> 
> Intel decided to abort the development of HAXM and the maintenance of 
> its QEMU part. Should we submit a patch to mark the Guest CPU Cores 
> (HAXM) status as Orphan and remove the maintainers from the 
> corresponding list? Meanwhile, should the code enabling HAX in QEMU 
> once committed by the community be retained?

If you no longer intend to work on QEMU bits related to HAXM, then yes, you should send a patch for the MAINTAINERS file to remove you name and mark it as "Orphan" status.

We would not normally delete code from QEMU, merely because it has been orphaned. If it is still known to work then we would retain it indefinitely, unless some compelling reason arises to drop it.
This gives time for any potential users to adjust their plans, and/or opportunity for other interested people to take over the maintenance role.

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

Re: Announcement of aborting HAXM maintenance

[Thomas Huth]

On 19/01/2023 13.40, Wang, Wenchao wrote:
> Hi, Daniel,
> 
> Thanks for your reply. Could you please help to merge below attached patch to update the status of HAXM in QEMU? Thanks a lot.

I can add the patch to my next pull request.
Thanks for your contribution!

  Thomas


> 
> ----------
>  From d88ba9ab3e32c991566443f3b52c45de67bf10c8 Mon Sep 17 00:00:00 2001
> From: Wenchao Wang <wenchao.wang@intel.com>
> Date: Thu, 19 Jan 2023 20:08:37 +0800
> Subject: [PATCH] MAINTAINERS: Abort HAXM maintenance
> 
> Abort the maintenance of Guest CPU Cores (HAXM).
> 
> * Clean up the maintainer list of X86 HAXM CPUs
> * Remove the web page URL and the mailing list
> * Change the status to Orphan
> 
> Reviewed-by: Hang Yuan <hang.yuan@intel.com>
> Signed-off-by: Wenchao Wang <wenchao.wang@intel.com>
> ---
>   MAINTAINERS | 5 +----
>   1 file changed, 1 insertion(+), 4 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 0fe50d01e3..0950061dc4 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -500,10 +500,7 @@ F: stubs/xen-hw-stub.c
>   Guest CPU Cores (HAXM)
>   ---------------------
>   X86 HAXM CPUs
> -M: Wenchao Wang <wenchao.wang@intel.com>
> -L: haxm-team@intel.com
> -W: https://github.com/intel/haxm/issues
> -S: Maintained
> +S: Orphan
>   F: accel/stubs/hax-stub.c
>   F: include/sysemu/hax.h
>   F: target/i386/hax/