Or Mergi
Or Mergi
@rmohr Currently, the mapping between a VM SR-IOV interface and the underlying VFs is not consistent when more than one VF is from the same resource pool. The VM might...
@RamLavi what you think about using the VMI `spec.device.interfaces` names instead of the current scheme (net1, net2 ..)? (by specifying them in the `k8s.v1.cni.cncf.io/networks` annotation)
> @ormergi AFAIU these names are supposed to be the interface names inside the `virt-launcher` Pod. IIRC they are limited in length. Correct, the CNI will set the interfaces with...
Currently, there is no way to do such mapping out-of-box, you can set each interface with a custom MAC address in the VMI spec and compare it to the guest...
@YitzyD Thanks for sharing and detailed info :slightly_smiling_face: To workaround this, you can create a VFs device pool (sriov-device-plugin config or `SriovNetwotkPolicy` if SR-IOV network operator deployed) for each group...
> looks good in general. But we need to wait for a new release of KubeVirt, and a successful bump of its version here. @nunnatsa Yes, kubevirt/kubevirt#7990 included in Kubevirt...
@andreabolognani Hey is there any chance that the last Libvirt and QEMU update is related?
> What makes you think it might be related to the new virtualization packages? When did the issue start showing up? Did anything change in the test suite recently? @andreabolognani...