This issue is libvirt specific. Other drivers may or may not have similar issues but the code paths are very different and can't be generalized under this bug. So adding " running the libvirt driver." or something similar to the first sentence should cover it.
This issue is libvirt specific. Other drivers may or may not have similar issues but the code paths are very different and can't be generalized under this bug. So adding " running the libvirt driver." or something similar to the first sentence should cover it.