Re: [libvirt-users] Virsh+QEMU, SSH issue on compiled libvirt
On 03/07/13 20:37, Saravanan Shanmugham (sarvi) wrote:
With these options, it fails to install as below
/bin/mkdir -p '/ws/sarvi-sjc/skunkworks/bspace/usrcisco/libexec'
/bin/mkdir -p
'/ws/sarvi-sjc/skunkworks/bspace/usrcisco/share/augeas/lenses'
/bin/mkdir -p
'/ws/sarvi-sjc/skunkworks/bspace/usrcisco/share/augeas/lenses/tests'
/bin/mkdir -p '/etc/libvirt'
/bin/mkdir: cannot create directory `/etc/libvirt': Permission denied
make-3.79.1-p7[3]: *** [install-confDATA] Error 1
make-3.79.1-p7[3]: Leaving directory
`/ws/sarvi-sjc/skunkworks/bspace/libvirt-1.0.3/src'
make-3.79.1-p7[2]: *** [install-am] Error 2
make-3.79.1-p7[2]: Leaving directory
`/ws/sarvi-sjc/skunkworks/bspace/libvirt-1.0.3/src'
make-3.79.1-p7[1]: *** [install] Error 2
make-3.79.1-p7[1]: Leaving directory
`/ws/sarvi-sjc/skunkworks/bspace/libvirt-1.0.3/src'
make-3.79.1-p7: *** [install-recursive] Error 1
Just changing
# define LIBVIRTD_PRIV_UNIX_SOCKET LOCALSTATEDIR
"/run/libvirt/libvirt-sock"
# define LIBVIRTD_PRIV_UNIX_SOCKET_RO LOCALSTATEDIR
"/run/libvirt/libvirt-sock-ro"
To
# define LIBVIRTD_PRIV_UNIX_SOCKET "/var"
"/run/libvirt/libvirt-sock"
# define LIBVIRTD_PRIV_UNIX_SOCKET_RO "/var"
"/run/libvirt/libvirt-sock-ro"
Fixed the problem and things worked fine.
Okay, this fixes the stuff at first but it isn't a nice fix.
It would be nice for a client only builds to be able to control through a
./configure argument or through some other .conf file where the server
expects to find its socket file.
Hmm, you still can configure the LOCALSTATEDIR variable. The only
drawback is that it puts all daemon state into the configured path.
That said, I am wondering why the client has to know where the server
maintains its libvirt-sock files? Can't client and the server both talk in
relative path terms instead of absolute?
Remote clients don't know the path on the remote host so we can't really
do this. On the other hand, we provide means for configuring the path to
the socket while opening the remote connection. It makes the URI ugly,
but works:
virsh -c qemu+ssh://user@host:port/system?socket=/path/to/socket/on/remote
Peter