kubevirt.github.io
kubevirt.github.io copied to clipboard
kubevirt
QEmu fatal error on M1 Mac with Docker Desktop and minikube
Is this a BUG REPORT or FEATURE REQUEST?:
Uncomment only one, leave it on its own line:
/kind bug
/kind enhancement
What happened:
Trying to start https://kubevirt.io/labs/manifests/vm.yaml and open a console to it. The VirtualMachineInstance shows the following error:
'server error. command SyncVMI failed: "LibvirtError(Code=67, Domain=10,
Message=''unsupported configuration: CPU mode ''host-passthrough'' for aarch64
qemu domain on aarch64 host is not supported by hypervisor'')"'
What you expected to happen:
Console should open, showing that VMs output.
Anything else we need to know?:
Running on an M1 Max, on top op Docker Desktop with Docker Engine v24.0.6, using minikube v1.32.0 on Darwin 14.2 (arm64).
I enabled emulation:
spec:
certificateRotateStrategy: {}
configuration:
developerConfiguration:
useEmulation: true
What am I missing? I understand I need emulation on a ARM Mac because of platform limitations.
This issue might get better traction in the kubevirt/kubevirt repo, but I understand it makes sense here as this is related to the minikube quickstart on this site.
@cwilkers I see what you mean. I was able to get everything I need up & running on AMD64 without any hassle and thus I decided to post it here, indeed because of the quickstart guide you mentioned.
Hi @tommy2d @cwilkers Regrettably, KubeVirt does not yet offer support for macOS. There are existing issues related to this, such as the one highlighted here: Issue #10939 on GitHub. As I do not have a Mac computer, it's challenging for me to facilitate KubeVirt compatibility with macOS.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubevirt-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.