Could you please have a look at the permissions of the xend sockets under

/var/run/xend/*? Since virsh is being executed with the the privileges of
the currently logged on user, the driver might not be able to access the
respective socket for reading which causes the driver .