zhhray
Is it a bug in 0.44.1 version of kubevirt? Is it the same issue with this issue? https://github.com/kubevirt/kubevirt/issues/6620
This problem persists when kubevirt is upgraded to the latest version. Can anyone answer this question? @rmohr
> @zhhray can you verify that other pods can reach the internet, and in addition, can you try connecting to the vm via `virtctl console` (serial console) or `virtctl vnc`...
Is there any key information or log that I can provide?
> I'm interested in the VMI status (just making sure you're sshing to the correct address). Can you show us the interface status of the VM ? `kubectl get vmi...
> Hello @zhhray, this does seem to be the same issue as described here: #6620 > > Could you please provides us with the virt-handler logs (collected from the virt-handler...
By the way, my configuration in Kubevirt's CR is already like this. However, the startup argument `-v` of all virt-xxx components still has a value of `2`. I killed all...
> may be node's kernel version too low(
> may be node's kernel version too low(
> Interesting, thanks @qyzhaoxun @SimpCosm for pointing this out! It appears our CI is kept up-to-date, so this issue has completely flew under the radar. > > @zhhray This change...