-
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
[macOS] podman machine start
fails with the error message "qemu-system-x86_64: CPU model 'host' requires KVM"
#10555
Comments
I was able to start the VM by adding the QEMU option.
Hypervisor.framework is supported on macOS
|
For some reason it is only added on arm64, but not on amd64: Note: this was in |
@baude PTAL |
@ashley-cui PTAL also. |
distribution information and qemu version ? |
I've added the information to the top comments.
|
Ok, thank you. We were testing with version 5.0. I will try v6.0 and report back. |
On intel macs, we need to accel=hvf to work correctly. Fixes: containers#10555 [NO TESTS NEEDED] Signed-off-by: Brent Baude <[email protected]>
closed via #10605 |
I've got v3.2.1 working fine. Also, #10578 seems to have been fixed. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
On macOS, when I run
podman machine init
and thenpodman machine start
, I get an error message "qemu-system-x86_64: CPU model 'host' requires KVM" and the VM fails to start.Steps to reproduce the issue:
On the Mac client:
Describe the results you received:
Describe the results you expected:
The VM will be successfully started.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Package info (e.g. output of
rpm -q podman
orapt list podman
):podman
qemu
VM image
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
11.3.1 (20E241)Updated to 11.4The text was updated successfully, but these errors were encountered: