Skip to content
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

Minikube cluster using kvm2 driver is broken on linux/aarch64 #18238

Closed
nirs opened this issue Feb 23, 2024 · 2 comments · Fixed by #18239
Closed

Minikube cluster using kvm2 driver is broken on linux/aarch64 #18238

nirs opened this issue Feb 23, 2024 · 2 comments · Fixed by #18239
Labels
arch/arm64 co/kvm2-driver KVM2 driver related issues kind/bug Categorizes issue or PR as related to a bug. os/linux priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@nirs
Copy link
Contributor

nirs commented Feb 23, 2024

What Happened?

Starting minikube using kvm2 driver times out getting an ip address. The VM
starts but drop into the UEFI shell.

Example command:

minikube start --driver kvm2

The issue is using SATA cdrom - this is not supported in QEMU for linux/aarch64.

To reproduce install Asahi Linux Fedora remix on a MacBook.

Attach the log file

Logs are not relevant.

Operating System

Redhat/Fedora

Driver

KVM2

nirs added a commit to nirs/minikube that referenced this issue Feb 23, 2024
On linux/aarch64 (e.g. Asahi Linux on MacBook M*) booting from SATA
cdrom is broken and the VM drops into the UEFI shell.

It seems that linux/aarch64 supports only virtio and scsi devices[1].
Replace with scsi cdrom (like the x86 version) and addd a virtio-scsi
controller since the default scsi controller does not boot as well.

[1] https://kubevirt.io/user-guide/virtual_machines/virtual_machines_on_Arm64/#disks-and-volumes

Fixes kubernetes#18238
nirs added a commit to nirs/minikube that referenced this issue Feb 23, 2024
On linux/aarch64 (e.g. Asahi Linux on MacBook M*) booting from SATA
cdrom is broken and the VM drops into the UEFI shell.

It seems that linux/aarch64 supports only virtio and scsi devices[1].
Replace with scsi cdrom (like the x86 version) and addd a virtio-scsi
controller since the default scsi controller does not boot as well.

[1] https://kubevirt.io/user-guide/virtual_machines/virtual_machines_on_Arm64/#disks-and-volumes

Fixes kubernetes#18238
@afbjorklund
Copy link
Collaborator

afbjorklund commented Mar 7, 2024

I think there is a lack of test machines for linux/arm64, previously I was mostly using Raspberry Pi

It is possible that the "qemu" driver works better

The "kvm" driver probably wasn't tested much

1be7018

@afbjorklund
Copy link
Collaborator

afbjorklund commented Mar 7, 2024

Also there is a lack of Fedora OS testing in general, including other architectures such as x86_64

@afbjorklund afbjorklund added arch/arm64 os/linux co/kvm2-driver KVM2 driver related issues kind/bug Categorizes issue or PR as related to a bug. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. labels Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch/arm64 co/kvm2-driver KVM2 driver related issues kind/bug Categorizes issue or PR as related to a bug. os/linux priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants