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. Thank you. <div class="gmail_quote">2011/1/20 Justin Clift <<a href="mailto:jclift@redhat.com">jclift@redhat.com</a>> <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On 20/01/2011, at 9:26 PM, Marcela Castro León wrote: Hello > > I've finished the installation. The daemon is not up, so I've tried in that way: > > chubut@chubut:/usr/local/sbin$ sudo ./libvirtd start start > 11:23:17.543: 6168: warning : networkAddGeneralIptablesRules:1097 : Could not add rule to fixup DHCP response checksums on network 'default'. > 11:23:17.543: 6168: warning : networkAddGeneralIptablesRules:1098 : May need to update iptables package & kernel to support CHECKSUM rule. > 11:23:17.577: 6168: warning : qemudStartup:1331 : Unable to create cgroup for driver: No such device or address > 11:23:17.704: 6168: warning : lxcStartup:2128 : Unable to create cgroup for driver: No such device or address > > And stay there, doesn't finish, and not start. > > Can you tell me if i'm doing in the right way? </div>Hi Marcela, When you start the libvirt daemon from the command line, it keeps in the foreground, without going back to a shell prompt. ie: $ sudo./libvirtd (various messages print out here, but libvirtd doesn't exit) Since the libvirt daemon has effectively taken over that terminal session, if I start another terminal session, I can generally use virsh to connect to it. Have you tried that? Starting a new terminal session while libvirtd is running, and then using virsh or virt-manager or something. ? Regards and best wishes, Justin Clift </blockquote></div>