On 10/30/2012 08:30 AM, 何鑫 wrote: Hello, [can you please convince your mailer to wrap long lines - it was very awkward to read this] Sounds like you are mixing self-compiled binaries with system binaries, and that the two have different ideas (based on the options used at ./configure time) of where files should live. To fix this, you need to either make sure your self-compiled binary uses the same ./configure options as what your distro would use (if you self-build from libvirt.git on Fedora, './autogen.sh --system' will help in this regard, although so far no one has submitted patches for that to work on Ubuntu). Or you need to make sure that EVERYTHING you are using is from your self-compiled version, which means using your self-compiled virsh (and not the distro virsh) for connecting to the self-compiled libvirtd. Also, are you sure you started your self-built libvirtd as a daemon? Correct, you can't copy sockets, especially since the socket should only exist while libvirtd is running. -- Eric Blake eblake(a)redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org