VirtualDomain status waits forever if libvirtd is not running

If the libvirtd is down or virsh cannot connect to it for whatever reason, VirtualDomain considers that as "no state" for the domain. That turns it into an infinite loop and operations eventually time out (stop too). Noticed while shutting down a node where libvirt got erroneously stopped before pacemaker: the node got fenced because a VirtualDomain resource timed out first in migrate then in stop.

Start by locating the VirtualDomain resource agent and its handling of virsh connection failures when libvirtd is unavailable. Reproduce the status and stop paths with libvirtd stopped or virsh unable to connect. Done means those operations fail or recover instead of looping until they time out.

Written by the indexing model from the issue text.