This message was deleted.

That can be safely ignored. I suspect it's just a side effect of how KubeVirt manages the libvirt process and communicates with the guest

I raised a new issue on libvirt gitlab https://gitlab.com/libvirt/libvirt/-/issues/605 and they mentioned it has been fixed in libivrt v9.2 and has not been back ported but since harvester v1.2.1 is using kubevirt v0.54.0 which is underneath using libvirt 8.0.0-2, that's why we are seeing these warnings. If the next release of harvester contains kubevirt which supports libvirt v9.2+ , hopefully we shouldn't be getting these warnings after once

Nice. Harvester 1.3.0 will ship with KubeVirt 1.1.0.