On Tue, Apr 14, 2009 at 02:06:52PM -0700, Daniel Labrosse wrote: > Hi All, > > I've been using libvirt 0..4.4 for a few weeks now. I have > unix_sock_group = "mygroup" set so that i can perform non-root > management capabilities on the host. > > I have recently installed a new host running Scientific Linux 5.3 and > libvirt 0.3.3 comes as default. First off, there is no libvirtd.conf > file included with 0.3.3, so I copied the file from libvirt 0.4.4 (which > is running on my Fedora 8 box). The 'unix_sock_group' config param *is* supported in 0.3.3, but the libvirtd daemon will not change the group ownership in the directory /var/run/libvirt where the socket is created. So you almost certainly won't be able to access the socket itself. You could try chgrp'ing the directory. A good test is to make sure you can access the socket as non-root, eg ls -l /var/run/libvirt/libvirt-sock Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list