During hotplug, virt-launcher refers to a non existent device, which causes IO errors when the guest attempts to access the storage. This has been observed within hypershift/kubevirt with kubevirt-csi.

So the device major and minor in the virt-launcher do not match the device major/minor in the attachment pod. The device major/minor on the host match the attachment pod (since that comes from kubernetes). I think that at somepoint the major/minor did match, but something caused the underlying major/minor to change (maybe attached to different node, attachment pod killed, not sure) but the virt-launcher never got updated.

Should probably modify virt-handler to check major/minor on the file besides it existence, and re-create if different.