Am 07.10.2013 19:24, schrieb Michael Hampicke: > Am 07.10.2013 11:29, schrieb Stefan G. Weichinger: >> Am 03.10.2013 15:39, schrieb Michael Hampicke: >> >>> Server side: >>> >>> [ebuild R ~] app-emulation/libvirt-1.1.2-r3 USE="caps >>> libvirtd lvm macvtap nls numa python qemu udev vepa >>> virt-network -audit -avahi -firewalld -fuse -iscsi -lxc -nfs >>> -openvz -parted -pcap -phyp -policykit -rbd -sasl (-selinux) >>> -systemd -uml -virtualbox -xen" PYTHON_SINGLE_TARGET="python2_7 >>> -python2_6" PYTHON_TARGETS="python2_7 -python2_6" 0 kB >>> >>> I connect via ssh+pubkey >> >> Would you mind sharing your libvirtd.conf as well? Did you add a >> separate user/group for libvirtd on the server side? >> >> Thanks! >> >> > > Hi Stefan, I did not change my libvirtd.conf There are no options > set there, only comments. > > # egrep -i 'qemu|kvm|libvirt' /etc/passwd /etc/group > /etc/passwd:qemu:x:77:77:added by portage for > libvirt:/dev/null:/sbin/nologin /etc/group:kvm:x:78:qemu > /etc/group:qemu:x:77: > > > Once I had a problem with libvirt too. I remember that there was > some debug option. When enabled you could see what libvirt was > doing exactly. But I don't remeber where that options was. Maybe it > was some enviroment variable that you had to set? Something like > > DEBUGOPTIONS="whatever" virsh your commands > > and > > DEBUGOPTIONS="whatever" libvirt --option-to-not-fork-in-background > > I don't have the man page handy right now. HTH
Thanks for your reply ... I will check tomorrow when I am back at my office (the IPSEC-VPN is locked to my static IP etc etc). You use an URI like qemu+ssh://server ? I read about transports: http://libvirt.org/remote.html#Remote_transports and libvirtd is definitely running at the remote host. I somehow suspect that systemd does *something* to the used sockets ... dunno. Regards, Stefan
