kubevirt: virt-launcher is automatically terminated after starting testvm

What happened: After starting testvm ,virt-launcher pod starts initialising and then automatically terminated. kubectl get vmi command saying no resource found.

What you expected to happen: vmi starts running

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

Additional context:

vikash@pop-os:~$ virtctl start testvm
VM testvm was scheduled to start
vikash@pop-os:~$ kubectl get pods -A
NAMESPACE     NAME                               READY   STATUS     RESTARTS   AGE
default       virt-launcher-testvm-c2zhc         0/2     Init:1/2   0          8s
kube-system   coredns-787d4945fb-cggn6           1/1     Running    0          14m
kube-system   etcd-minikube                      1/1     Running    0          15m
kube-system   kube-apiserver-minikube            1/1     Running    0          15m
kube-system   kube-controller-manager-minikube   1/1     Running    0          15m
kube-system   kube-proxy-rb7hl                   1/1     Running    0          14m
kube-system   kube-scheduler-minikube            1/1     Running    0          15m
kube-system   storage-provisioner                1/1     Running    0          15m
kubevirt      virt-api-598b86c466-lwkl8          1/1     Running    0          9m31s
kubevirt      virt-controller-5d7747c4d9-n9d5f   1/1     Running    0          8m56s
kubevirt      virt-controller-5d7747c4d9-xnr46   1/1     Running    0          8m56s
kubevirt      virt-handler-mhs8s                 1/1     Running    0          8m56s
kubevirt      virt-operator-66c966d959-b4q6l     1/1     Running    0          10m
kubevirt      virt-operator-66c966d959-v4gt4     1/1     Running    0          10m

vikash@pop-os:~$ kubectl get pods -A
NAMESPACE     NAME                               READY   STATUS        RESTARTS   AGE
default       virt-launcher-testvm-c2zhc         1/2     Terminating   0          16s
kube-system   coredns-787d4945fb-cggn6           1/1     Running       0          15m
kube-system   etcd-minikube                      1/1     Running       0          15m
kube-system   kube-apiserver-minikube            1/1     Running       0          15m
kube-system   kube-controller-manager-minikube   1/1     Running       0          15m
kube-system   kube-proxy-rb7hl                   1/1     Running       0          15m
kube-system   kube-scheduler-minikube            1/1     Running       0          15m
kube-system   storage-provisioner                1/1     Running       0          15m
kubevirt      virt-api-598b86c466-lwkl8          1/1     Running       0          9m39s
kubevirt      virt-controller-5d7747c4d9-n9d5f   1/1     Running       0          9m4s
kubevirt      virt-controller-5d7747c4d9-xnr46   1/1     Running       0          9m4s
kubevirt      virt-handler-mhs8s                 1/1     Running       0          9m4s
kubevirt      virt-operator-66c966d959-b4q6l     1/1     Running       0          10m
kubevirt      virt-operator-66c966d959-v4gt4     1/1     Running       0          10m

vikash@pop-os:~$ kubectl get pods -A
NAMESPACE     NAME                               READY   STATUS    RESTARTS   AGE
kube-system   coredns-787d4945fb-cggn6           1/1     Running   0          15m
kube-system   etcd-minikube                      1/1     Running   0          15m
kube-system   kube-apiserver-minikube            1/1     Running   0          15m
kube-system   kube-controller-manager-minikube   1/1     Running   0          15m
kube-system   kube-proxy-rb7hl                   1/1     Running   0          15m
kube-system   kube-scheduler-minikube            1/1     Running   0          15m
kube-system   storage-provisioner                1/1     Running   0          15m
kubevirt      virt-api-598b86c466-lwkl8          1/1     Running   0          9m46s
kubevirt      virt-controller-5d7747c4d9-n9d5f   1/1     Running   0          9m11s
kubevirt      virt-controller-5d7747c4d9-xnr46   1/1     Running   0          9m11s
kubevirt      virt-handler-mhs8s                 1/1     Running   0          9m11s
kubevirt      virt-operator-66c966d959-b4q6l     1/1     Running   0          10m
kubevirt      virt-operator-66c966d959-v4gt4     1/1     Running   0          10m

vikash@pop-os:~$ kubectl get vmi
No resources found in default namespace.

vikash@pop-os:~$ kubectl get vms
NAME     AGE   STATUS             READY
testvm   17m   CrashLoopBackOff   False

Environment:

  • KubeVirt version (use virtctl version): 0.59.0
  • Kubernetes version (use kubectl version): 1.26.1
  • VM or VMI specifications: N/A
  • Cloud provider or hardware configuration: N/A
  • OS (e.g. from /etc/os-release): N/A
  • Kernel (e.g. uname -a): N/A
  • Install tools: N/A
  • Others: N/A

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 15 (8 by maintainers)

Most upvoted comments

There was a similar issue some time ago https://github.com/kubevirt/kubevirt/issues/9059 . In short, minikube with kvm2 driver does not seem to support nft.