Comment 20 for bug 1382046

@serge,

In my case, no: "sudo stop libvirt-bin; sudo start libvirt-bin" does not always completely solve the problem.

'virsh list' worked find after reboot and I was able to bring up virt-manager as well.
% virsh list
 Id Name State
----------------------------------------------------

# Just to make sure it's not ns*cd crashing:
% ps aux | grep 'cd\>'
root 3572 0.0 0.0 771720 2632 ? Ssl 07:53 0:00 /usr/sbin/nscd
nslcd 3611 0.0 0.0 458764 11640 ? Sl 07:53 0:00 /usr/sbin/nslcd
jaffleck 6978 0.0 0.0 6588 708 pts/16 S+ 08:10 0:00 grep --color=auto cd\>

% virt-manager
# (success)
% virsh list
 Id Name State
----------------------------------------------------

% virsh list
error: failed to connect to the hypervisor
error: no valid connection
error: Failed to find group record for gid '1001': No such file or directory

% ps aux | grep 'cd\>'
root 3572 0.0 0.0 771720 2632 ? Ssl 07:53 0:00 /usr/sbin/nscd
nslcd 3611 0.0 0.0 458764 11640 ? Sl 07:53 0:00 /usr/sbin/nslcd
libvirt+ 7088 22.3 25.2 4732808 4144772 ? Sl 08:11 0:54 qemu-system-x86_64 -....
jaffleck 7211 0.0 0.0 6588 724 pts/16 S+ 08:15 0:00 grep --color=auto cd\>

# Exit virt-manager
% sudo service libvirt-bin restart
libvirt-bin stop/waiting
libvirt-bin start/running, process 8002
% virsh list
error: failed to connect to the hypervisor
error: no valid connection
error: Failed to find group record for gid '1001': No such file or directory
% sudo service libvirt-bin restart
libvirt-bin stop/waiting
libvirt-bin start/running, process 8061
% virsh list
 Id Name State
----------------------------------------------------
 2 Windows7 running

% virt-manager
# (success)

..this replicated the behavior I described in #11. So that's one documented instance. I'll see if it happens again.