On Mon, Mar 19, 2007 at 06:45:01PM +0900, Atsushi SAKAI wrote:
Hi,
I think virConnectOpen driver counting check is wrong.
If we does not run libvirt_qemud, virsh does not run on root privilege.
This restriction forces Xen user to run verbose libvirt_qemud.
Haha ! Thanks a lot, I noticed this just before the release but
didn't took the time to chase it down:
ot@xen64 ~]# /etc/init.d/libvirtd stop
Stopping libvirtd daemon: [ OK ]
[root@xen64 ~]# /usr/bin/virsh list
libvir: error : no support for hypervisor
virsh: error: failed to connect to the hypervisor
[root@xen64 ~]# /u/veillard/libvirt/src/virsh list
Id Name State
----------------------------------
0 Domain-0 running
[root@xen64 ~]#
thanks a lot, applied and commited !
Daniel
--
Red Hat Virtualization group
http://redhat.com/virtualization/
Daniel Veillard | virtualization library
http://libvirt.org/
veillard(a)redhat.com | libxml GNOME XML XSLT toolkit
http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine
http://rpmfind.net/