> I think now is running.
> I've started doing
>
> *chubut@chubut:/usr/local/sbin$ sudo ./libvirtd &
> *
> and checked doing
>
> *chubut@chubut:~$ ps -ef | grep libvirtd
> chubut 1877 1700 0 12:16 pts/0 00:00:00 grep --color=auto libvirtd
> chubut@chubut:~$ ps -ef | grep libvirtd
> root 1945 1721 0 12:17 pts/1 00:00:00 ./libvirtd
> chubut 1993 1700 0 12:17 pts/0 00:00:00 grep --color=auto libvirtd
> chubut@chubut:~$ sudo virsh -c qemu:///system list
> Id Name State
> ----------------------------------
>
> chubut@chubut:~$ *
>
> Do you think it's right? Thank you very much.
>
> Marcela
>
Please try as a root or via sudo:
> 2011/1/20 Justin Clift <
jclift@redhat.com>
>
>> On 20/01/2011, at 9:52 PM, Marcela Castro León wrote:
>> Hello
>>> I've got this error.
>>> chubut@chubut:/usr/local$ virsh -c qemu:///system list
>>> error: unable to connect to '/usr/local/var/run/libvirt/libvirt-sock',
>> libvirtd may need to be started: No such file or directory
>>> error: failed to connect to the hypervisor
>>>
>>> The daemon is not running, but i don't know how to start it.
>>
>> Ok, this might be a dumb question, but have you tried "sudo virsh -c
>> qemu:///system list" (with the "sudo") when the libvirtd program is running?
>
>
>