Currently the driver mocks GPUs devices. However, with kubevirt, once the device allocation is done for the pod, the pod then configures libvirt domain xml and passes the device to the domain (Kubevirt VM guest).
For this reason, currently with the driver, a kubevirt VM never goes to running state. There is a need to create a mock vfio device, which will help run example workflows as well as e2e tests for KubeVirt VM.
Currently the driver mocks GPUs devices. However, with kubevirt, once the device allocation is done for the pod, the pod then configures libvirt domain xml and passes the device to the domain (Kubevirt VM guest).
For this reason, currently with the driver, a kubevirt VM never goes to running state. There is a need to create a mock vfio device, which will help run example workflows as well as e2e tests for KubeVirt VM.