kubevirt: virt-handler fails to start on alpine 3.16 k3s cluster

What happened: virt-handler does not start on alpine 3.16 k3s cluster

What you expected to happen: I expect all pods of kubevirt started.

How to reproduce it (as minimally and precisely as possible):

  1. I installed k3s cluster on three nodes, one master and other two agents. curl -sfL https://get.k3s.io | sh -

Pramod-node1:~/.kube# kubectl get nodes -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME pramod-node3 Ready <none> 16m v1.24.6+k3s1 147.75.71.91 <none> Alpine Linux v3.16 5.15.47-0-lts containerd://1.6.8-k3s1 pramod-node2 Ready <none> 16m v1.24.6+k3s1 147.75.49.193 <none> Alpine Linux v3.16 5.15.47-0-lts containerd://1.6.8-k3s1 pramod-node1 Ready control-plane,master 20m v1.24.6+k3s1 139.178.89.1 <none> Alpine Linux v3.16 5.15.47-0-lts containerd://1.6.8-k3s1

  1. Then installed KubeVirt

export RELEASE=$(curl https://storage.googleapis.com/kubevirt-prow/release/kubevirt/kubevirt/stable.txt) kubectl apply -f https://github.com/kubevirt/kubevirt/releases/download/${RELEASE}/kubevirt-operator.yaml kubectl apply -f https://github.com/kubevirt/kubevirt/releases/download/${RELEASE}/kubevirt-cr.yaml

Pramod-node1:~/.kube# kubectl get pods -n kubevirt NAME READY STATUS RESTARTS AGE virt-operator-747d64c764-mb4bw 1/1 Running 0 11m virt-operator-747d64c764-qksbp 1/1 Running 0 11m virt-api-7fb5d599cc-nvk8b 1/1 Running 0 10m virt-api-7fb5d599cc-zr8xd 1/1 Running 0 10m virt-controller-6d594d9b54-wwpqh 1/1 Running 0 10m virt-controller-6d594d9b54-zn9gh 1/1 Running 0 10m virt-handler-w2ldj 0/1 Init:CrashLoopBackOff 6 (4m38s ago) 10m virt-handler-ddwpw 0/1 Init:CrashLoopBackOff 6 (4m30s ago) 10m virt-handler-n2gx4 0/1 Init:CrashLoopBackOff 6 (4m21s ago) 10m

Pramod-node1:~/.kube# kubectl logs -n kubevirt virt-handler-w2ldj -c virt-launcher error: failed to get emulator capabilities error: internal error: Failed to start QEMU binary /usr/libexec/qemu-kvm for probing:

Those ^^^ are the only messages I see in the logs

My CPU is AMD EPYC 7402P 24-Core Processor which supports HW virtualization I did check kvm modules are loaded.

Additional context: Add any other context about the problem here.

Environment:

  • KubeVirt version (use virtctl version): v0.58.0

  • Kubernetes version (use kubectl version): v1.24.6+k3s1

  • VM or VMI specifications: N/A

  • Cloud provider or hardware configuration: Equinix c3.medium.x86 server

  • OS (e.g. from /etc/os-release): NAME=“Alpine Linux” ID=alpine VERSION_ID=3.16.0 PRETTY_NAME=“Alpine Linux v3.16” HOME_URL=“https://alpinelinux.org/” BUG_REPORT_URL=“https://gitlab.alpinelinux.org/alpine/aports/-/issues

  • Kernel (e.g. uname -a): Linux Pramod-node1 5.15.47-0-lts #1-Alpine SMP Thu, 16 Jun 2022 06:04:02 +0000 x86_64 Linux

  • Install tools: N/A

  • Others: N/A

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 60 (4 by maintainers)

Most upvoted comments

It’s not just the hardware. Its hardware + alpine. Any other OS like ubuntu is working.

I will keep this issue open in case someone can find an answer.