From: "Philippe Mathieu-Daudé" <philmd@redhat.com> To: "Justin Terry (VM)" <juterry@microsoft.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org> Cc: "Fam Zheng" <fam@euphon.net>, "Thomas Huth" <thuth@redhat.com>, "Daniel P . Berrangé" <berrange@redhat.com>, "Eduardo Habkost" <ehabkost@redhat.com>, "Stefan Weil" <sw@weilnetz.de>, "Paolo Bonzini" <pbonzini@redhat.com>, 1879672@bugs.launchpad.net, "Alex Bennée" <alex.bennee@linaro.org>, "Sunil Muthuswamy" <sunilmut@microsoft.com>, "Richard Henderson" <rth@twiddle.net> Subject: Re: [PATCH v2 0/3] testing: Build WHPX enabled binaries Date: Fri, 31 Jul 2020 10:33:22 +0200 [thread overview] Message-ID: <324f5002-be0a-563e-b5a6-e08ee5e1ddad@redhat.com> (raw) In-Reply-To: <2acf854f-c49a-0811-31af-80e1e958f058@redhat.com> Hi Justin, Sunil, On 5/20/20 12:26 PM, Philippe Mathieu-Daudé wrote: > +launchpad ticket > > On 9/20/19 6:53 PM, Justin Terry (VM) wrote: >> Hey Phil, >> >> I have contacted our legal department for guidance on this specific >> use case and will update you when I hear back. Thank you for your >> patience. I recently understood legal changes can be very complex, thus it is implicit it can take years before getting updates. Since the project is still actively developed, maybe you could provide a Azure CI job to build a WHPX binary. We don't need to have access to the binary, just to the exit status (success/fail) and build logs. Do you think it is doable? Thanks, Phil. >> >> Justin Terry >> >>> -----Original Message----- >>> From: Philippe Mathieu-Daudé <philmd@redhat.com> >>> Sent: Friday, September 20, 2019 8:18 AM >>> To: qemu-devel@nongnu.org; Justin Terry (VM) <juterry@microsoft.com> >>> Cc: Daniel P . Berrangé <berrange@redhat.com>; Fam Zheng >>> <fam@euphon.net>; Thomas Huth <thuth@redhat.com>; Paolo Bonzini >>> <pbonzini@redhat.com>; Alex Bennée <alex.bennee@linaro.org>; Richard >>> Henderson <rth@twiddle.net>; Eduardo Habkost <ehabkost@redhat.com>; >>> Stefan Weil <sw@weilnetz.de> >>> Subject: Re: [PATCH v2 0/3] testing: Build WHPX enabled binaries >>> >>> On 9/20/19 1:33 PM, Philippe Mathieu-Daudé wrote: >>>> Add a job to cross-build QEMU with WHPX enabled. >>>> >>>> Since the WHPX is currently broken, include the patch required to have >>>> successful Shippable build. >>>> >>>> I previously included the WHPX headers shared by the Android project, >>>> and Daniel asked me to check the EULA. While trying to manually >>>> install the Windows SDK, I noticed the installer fetches archives >>>> directly, kindly asking where they are stored via the /fwlink API. >>>> Do the same, fetch the required archives and extract them. No need to >>>> accept EULA... >>>> >>>> Docker build the image first, then build QEMU in a instance of this >>>> image. The image is internal to Shippable, the instances are not >>>> reachable and are thrown once the build is finished. What we collect >>>> from Shippable is the console output of QEMU build process, and if the >>>> build process succeed or failed. So far we do not redistribute the >>>> image or built binaries. >>>> >>>> Philippe Mathieu-Daudé (3): >>>> target/i386: Fix broken build with WHPX enabled >>>> tests/docker: Add fedora-win10sdk-cross image >>>> .shippable.yml: Build WHPX enabled binaries >>> >>> FWIW here is the result of this series: >>> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapp. >>> shippable.com%2Fgithub%2Fphilmd%2Fqemu%2Fruns%2F516%2F11%2Fcon >>> sole&data=02%7C01%7Cjuterry%40microsoft.com%7C733a566f3233427 >>> 8ae6f08d73dddb39f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6 >>> 37045894733463150&sdata=55URgDII5r74QMUpLOD%2FWT5%2B5jbzyv >>> nfCSdv%2FNaWDAw%3D&reserved=0 >>> Duration 17 minutes (1076 seconds) >>> >>> 4m49s building the qemu:fedora-win10sdk-cross docker image, 11m10s >>> building WHPX QEMU. >
WARNING: multiple messages have this Message-ID (diff)
From: "Philippe Mathieu-Daudé" <1879672@bugs.launchpad.net> To: qemu-devel@nongnu.org Subject: [Bug 1879672] Re: [PATCH v2 0/3] testing: Build WHPX enabled binaries Date: Fri, 31 Jul 2020 08:33:22 -0000 [thread overview] Message-ID: <324f5002-be0a-563e-b5a6-e08ee5e1ddad@redhat.com> (raw) Message-ID: <20200731083322.ENhRhT75ndr6ZlmpCzUolBeHSkZ1fi7_HbqaUewWaO8@z> (raw) In-Reply-To: 2acf854f-c49a-0811-31af-80e1e958f058@redhat.com Hi Justin, Sunil, On 5/20/20 12:26 PM, Philippe Mathieu-Daudé wrote: > +launchpad ticket > > On 9/20/19 6:53 PM, Justin Terry (VM) wrote: >> Hey Phil, >> >> I have contacted our legal department for guidance on this specific >> use case and will update you when I hear back. Thank you for your >> patience. I recently understood legal changes can be very complex, thus it is implicit it can take years before getting updates. Since the project is still actively developed, maybe you could provide a Azure CI job to build a WHPX binary. We don't need to have access to the binary, just to the exit status (success/fail) and build logs. Do you think it is doable? Thanks, Phil. >> >> Justin Terry >> >>> -----Original Message----- >>> From: Philippe Mathieu-Daudé <philmd@redhat.com> >>> Sent: Friday, September 20, 2019 8:18 AM >>> To: qemu-devel@nongnu.org; Justin Terry (VM) <juterry@microsoft.com> >>> Cc: Daniel P . Berrangé <berrange@redhat.com>; Fam Zheng >>> <fam@euphon.net>; Thomas Huth <thuth@redhat.com>; Paolo Bonzini >>> <pbonzini@redhat.com>; Alex Bennée <alex.bennee@linaro.org>; Richard >>> Henderson <rth@twiddle.net>; Eduardo Habkost <ehabkost@redhat.com>; >>> Stefan Weil <sw@weilnetz.de> >>> Subject: Re: [PATCH v2 0/3] testing: Build WHPX enabled binaries >>> >>> On 9/20/19 1:33 PM, Philippe Mathieu-Daudé wrote: >>>> Add a job to cross-build QEMU with WHPX enabled. >>>> >>>> Since the WHPX is currently broken, include the patch required to have >>>> successful Shippable build. >>>> >>>> I previously included the WHPX headers shared by the Android project, >>>> and Daniel asked me to check the EULA. While trying to manually >>>> install the Windows SDK, I noticed the installer fetches archives >>>> directly, kindly asking where they are stored via the /fwlink API. >>>> Do the same, fetch the required archives and extract them. No need to >>>> accept EULA... >>>> >>>> Docker build the image first, then build QEMU in a instance of this >>>> image. The image is internal to Shippable, the instances are not >>>> reachable and are thrown once the build is finished. What we collect >>>> from Shippable is the console output of QEMU build process, and if the >>>> build process succeed or failed. So far we do not redistribute the >>>> image or built binaries. >>>> >>>> Philippe Mathieu-Daudé (3): >>>> target/i386: Fix broken build with WHPX enabled >>>> tests/docker: Add fedora-win10sdk-cross image >>>> .shippable.yml: Build WHPX enabled binaries >>> >>> FWIW here is the result of this series: >>> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapp. >>> shippable.com%2Fgithub%2Fphilmd%2Fqemu%2Fruns%2F516%2F11%2Fcon >>> sole&data=02%7C01%7Cjuterry%40microsoft.com%7C733a566f3233427 >>> 8ae6f08d73dddb39f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6 >>> 37045894733463150&sdata=55URgDII5r74QMUpLOD%2FWT5%2B5jbzyv >>> nfCSdv%2FNaWDAw%3D&reserved=0 >>> Duration 17 minutes (1076 seconds) >>> >>> 4m49s building the qemu:fedora-win10sdk-cross docker image, 11m10s >>> building WHPX QEMU. > -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1879672 Title: QEMU installer with WHPX support Status in QEMU: Opinion Bug description: People often ask the community to add WHPX support to the QEMU installer for Windows, but it is impossible due to the license limitations of the WHPX SDK. The WinHvEmulation.h and WinHvPlatform.h header files needed are "All rights reserved". However these headers only contain struct definitions and integer constants, no functional code in macros or inline functions. See: https://www.mail-archive.com/qemu-devel@nongnu.org/msg645815.html It is questionable whether the headers alone can be considered copyrightable material. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1879672/+subscriptions
next prev parent reply other threads:[~2020-07-31 8:34 UTC|newest] Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-09-20 11:33 [PATCH v2 0/3] testing: Build WHPX enabled binaries Philippe Mathieu-Daudé 2019-09-20 11:33 ` [PATCH v2 1/3] target/i386: Fix broken build with WHPX enabled Philippe Mathieu-Daudé 2019-09-20 11:37 ` Paolo Bonzini 2019-09-20 11:33 ` [PATCH v2 2/3] tests/docker: Add fedora-win10sdk-cross image Philippe Mathieu-Daudé 2019-09-20 11:33 ` [PATCH v2 3/3] .shippable.yml: Build WHPX enabled binaries Philippe Mathieu-Daudé 2019-09-20 15:17 ` [PATCH v2 0/3] testing: " Philippe Mathieu-Daudé 2019-09-20 16:53 ` Justin Terry (VM) 2020-05-20 10:26 ` Philippe Mathieu-Daudé 2020-05-20 10:26 ` [Bug 1879672] " Philippe Mathieu-Daudé 2020-07-31 8:33 ` Philippe Mathieu-Daudé [this message] 2020-07-31 8:33 ` Philippe Mathieu-Daudé 2020-07-31 23:31 ` [EXTERNAL] " Sunil Muthuswamy 2020-08-03 10:51 ` Philippe Mathieu-Daudé 2020-08-03 10:51 ` [Bug 1879672] " Philippe Mathieu-Daudé 2020-08-03 11:28 ` Stefan Weil 2020-08-03 20:25 ` Stefan Weil 2020-08-04 6:43 ` Thomas Huth 2020-08-04 6:55 ` Stefan Weil 2020-08-04 7:23 ` Philippe Mathieu-Daudé 2020-08-04 7:23 ` [Bug 1879672] " Philippe Mathieu-Daudé 2020-08-04 7:42 ` Stefan Weil 2020-08-04 7:52 ` Philippe Mathieu-Daudé 2020-08-04 7:52 ` [Bug 1879672] " Philippe Mathieu-Daudé 2020-08-04 8:10 ` Thomas Huth 2020-08-04 9:23 ` Daniel P. Berrangé 2020-08-04 9:23 ` [Bug 1879672] " Daniel Berrange 2020-08-18 21:20 ` [EXTERNAL] " Sunil Muthuswamy 2020-08-19 3:36 ` Philippe Mathieu-Daudé 2020-08-19 3:36 ` [Bug 1879672] " Philippe Mathieu-Daudé 2019-09-21 6:34 ` no-reply -- strict thread matches above, loose matches on Subject: below -- 2020-05-20 10:14 [Bug 1879672] [NEW] QEMU installer with WHPX support Philippe Mathieu-Daudé 2020-05-20 10:25 ` [Bug 1879672] " Daniel Berrange 2020-05-20 12:30 ` Stefan Weil 2020-06-08 7:18 ` Philippe Mathieu-Daudé 2020-11-04 20:01 ` John Snow 2020-11-04 23:12 ` Philippe Mathieu-Daudé 2020-11-04 23:12 ` Philippe Mathieu-Daudé 2021-05-09 15:38 ` Philippe Mathieu-Daudé 2021-05-09 18:33 ` Stefan Weil 2021-05-27 7:45 ` Philippe Mathieu-Daudé 2020-02-18 20:38 [PATCH] WHPX: Assigning maintainer for Windows Hypervisor Platform Sunil Muthuswamy 2020-02-18 20:51 ` Justin Terry (SF) 2020-02-19 8:31 ` Philippe Mathieu-Daudé 2020-02-19 15:50 ` [EXTERNAL] " Justin Terry (SF) 2020-02-21 7:54 ` Stefan Weil 2020-02-24 19:43 ` Sunil Muthuswamy 2020-05-20 10:29 ` Philippe Mathieu-Daudé 2020-05-20 10:29 ` [Bug 1879672] " Philippe Mathieu-Daudé 2020-05-19 21:59 ` Sunil Muthuswamy 2020-05-20 10:29 ` Philippe Mathieu-Daudé 2020-05-20 10:29 ` [Bug 1879672] " Philippe Mathieu-Daudé 2020-02-21 17:15 ` Paolo Bonzini 2019-11-07 19:48 [PATCH v2] WHPX: support for xcr0 Sunil Muthuswamy 2019-11-07 20:05 ` Stefan Weil 2019-11-07 22:52 ` Sunil Muthuswamy 2020-05-20 10:27 ` Philippe Mathieu-Daudé 2020-05-20 10:27 ` [Bug 1879672] " Philippe Mathieu-Daudé 2019-11-12 18:52 ` Sunil Muthuswamy 2019-11-13 14:56 ` Paolo Bonzini 2022-04-28 6:31 ` Paolo Bonzini 2019-09-19 10:59 [Qemu-devel] [PATCH 0/2] testing: Build WHPX enabled binaries Philippe Mathieu-Daudé 2019-09-19 10:59 ` [Qemu-devel] [PATCH 1/2] tests/docker: Add fedora-win10sdk-cross image Philippe Mathieu-Daudé 2019-09-19 11:28 ` Alex Bennée 2019-09-19 11:35 ` Philippe Mathieu-Daudé 2019-09-19 10:59 ` [Qemu-devel] [PATCH 2/2] .shippable.yml: Build WHPX enabled binaries Philippe Mathieu-Daudé 2019-09-19 11:02 ` Philippe Mathieu-Daudé 2019-09-19 11:09 ` [Qemu-devel] [PATCH 0/2] testing: " Thomas Huth 2019-09-19 11:21 ` Philippe Mathieu-Daudé 2019-09-19 11:18 ` Stefan Weil 2019-09-19 11:26 ` Philippe Mathieu-Daudé 2020-05-20 10:25 ` Philippe Mathieu-Daudé 2020-05-20 10:25 ` [Bug 1879672] " Philippe Mathieu-Daudé 2019-09-19 11:41 ` [Qemu-devel] " Daniel P. Berrangé 2019-09-19 11:54 ` Philippe Mathieu-Daudé 2019-09-19 13:25 ` Daniel P. Berrangé
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=324f5002-be0a-563e-b5a6-e08ee5e1ddad@redhat.com \ --to=philmd@redhat.com \ --cc=1879672@bugs.launchpad.net \ --cc=alex.bennee@linaro.org \ --cc=berrange@redhat.com \ --cc=ehabkost@redhat.com \ --cc=fam@euphon.net \ --cc=juterry@microsoft.com \ --cc=pbonzini@redhat.com \ --cc=qemu-devel@nongnu.org \ --cc=rth@twiddle.net \ --cc=sunilmut@microsoft.com \ --cc=sw@weilnetz.de \ --cc=thuth@redhat.com \ /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: linkBe 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.