-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated options for QEMU on Windows hosts #17029
Updated options for QEMU on Windows hosts #17029
Conversation
@arixmkii the bots want you to add a test or add a no test needed message. See the failures. |
@n1hility PTAL |
LGTM once CI is green (need [NO NEW TESTS NEEDED] in description + a force push to pick it up as @baude mentions) |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: arixmkii, n1hility The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Using "w" suffixed versions of QEMU binaries for correct background process handling and not bind it to lifecycle of command prompt window. Stub for arm64 version added to fix compilation issues of this target, when QEMU machine will be finally enabled. Signed-off-by: Arthur Sengileyev <[email protected]>
35f28ed
to
35d2f61
Compare
LGTM |
/lgtm |
These changes are extracted from #16872 draft. arm64 will not be supported as QEMU machine host, because there is no QEMU for that arch on Windows, but it will be needed to compile remote client on that arch (alternative is to introduce a bigger refactoring around machine related code).
Using "w" suffixed versions of QEMU binaries for correct background process handling and not bind it to lifecycle of command prompt window. Stub for arm64 version added to fix compilation issues of this target, when QEMU machine will be finally enabled.
Signed-off-by: Arthur Sengileyev [email protected]
[NO NEW TESTS NEEDED]
Does this PR introduce a user-facing change?