Change default QEMU CPU level to qemu64 on Windows amd64

[arixmkii]

Originally max level with exceptions was used, because netavark could not work with qemu64, because there were needed SIMD instructions blocked. Now it works w/o any issues. What could have changed in between:

• qemu64 could have been adjusted to expose more features for this basic CPU;
• Rust compiler could have been improved to generate multiple versions of binary paths to choose the suitable most performant one available at runtime;
• Optimization flags might have changed for netavark;
• Some or all of the above.

This has been verified to work on:

• Windows 10, Intel Core i7 6700K
• Windows 11, Intel Core i7 11375H
• Windows 11 Insiders Preview, Hyper-V machine with nested virtualization on Windows 11 Intel Core i7 11375 host Support Qemu accelerated podman machine on Windows hosts #13006 (comment)

SW versions:

• QEMU 8.1.0-rc2 (this is a safe choice, because the QEMU support on Windows is yet to be released)
• Podman 4.7.0-dev

All test were run with SMP 1 and SMP 4. max level in Hyper-V was always getting stuck during boot sequence (in different stages for SMP 1 and SMP 4 (SMP 1 was completing slightly more actions, but never fully booted the VM)).

I don't have any AMD machines for testing, but I expect qemu64 to be more stable for AMD as well as it should hide almost all of the specifics of the CPU in question.

No release note, as there were no releases for Windows QEMU yet.

No tests as this is only the default settings changed and no logic changes.

Does this PR introduce a user-facing change?

None

[NO NEW TESTS NEEDED]

[rhatdan]

@baude @n1hility @gbraad @ashley-cui PTAL

[gbraad]

I'll try to test this before my PTO

[arixmkii]

@gbraad if you want to test it end to end you will need as well adding:

• Implement Unix domain socket support for VLAN #17473
• Enable QEMU Podman machine on Windows #18488

Both PRs are rebased and applies nicely to the latest code. I also have the notes on how to init machine for Windows and QEMU (which additional parameters in cmd line are needed comparing to WSL or QEMU on other platforms) available here.

[arixmkii]

Do we have any updates on this?

[flouthoc]

I'll try to test this before my PTO

@gbraad Friendly ping.

[arixmkii]

I have it in a branch with 2 other commits https://github.com/arixmkii/podman/tree/qcw-2023-09-30-3 This branch then can be tested with machine e2e tests (documentation update included in the topmost commit)

In isolation the change could be tests without rebuilds just following instructions on how to run Podman with QEMU on Windows from here https://github.com/containers/podman/blob/36f8e78d718e1a47727dce798e9bbe4881c53099/docs/tutorials/qemu-remote-tutorial.md#qemu-1 One will need to adjust -cpu part.

[rhatdan]

@gbraad @baude @ashley-cui PTAL

[n1hility]

LGTM

[packit-as-a-service]

Ephemeral COPR build failed. @containers/packit-build please check.

[lsm5]

Ephemeral COPR build failed. @containers/packit-build please check.

ignore eln for now

[rhatdan]

@baude waiting on you.

[TomSweeneyRedHat]

Re-Ping @baude

[baude]

/lgtm

[baude]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arixmkii, baude

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:

• OWNERS [baude]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment