Vihari Vinnakota

Hi, Thanks for the reply. The status of the kubevirt pods shows ready as below: NAME READY STATUS RESTARTS AGE virt-api-7589df599d-5fjn7 1/1 Running 0 3m8s virt-api-7589df599d-5s9kg 1/1 Running 0 3m8s...

Hi, Please find the status and logs of the kubevirt pods fetched from a fresh setup in the same order. ubuntu@root-k8s-dpdk-master:~$ kubectl get pods -n kubevirt -owide NAME READY STATUS...

@usrbinkat, can I know if there is anything I can do to fix this issue. I am not sure what exactly is wrong. I am not able to create a...

@usrbinkat, I am still stuck with the issue. Can you please help me fixing this. I would like to know if there is any observation that I missed form the...

> Same as in #8478 > > Hi @feitnomore, this is a known issue that currently KubeVirt does not work with Kubernetes `1.25` because of the device plugin registration failure....

> @nvinnakota10, well, the fix for the device plugin issue is included in 0.58.0. AFAIK, KubeVirt is not yet tested against k8s 1.25 therefore its probably not 'officially' supported yet....

The issue is seen because TCP traffic was dropping at the compute NIC, where the kubevirt is installed. It is due to our settings in the custom CNI.

@xpivarc , @vasiliy-ul , can you please provide any documentation which gives the information on which kubevirt version supports which K8s version. We are confused if 0.58 supports k8s 1.25....

> @nvinnakota10 I'm still missing the scheduling part or is it part of CNI? My question is will be a VMI requesting this network interface automatically scheduled on nodes where...