You are not logged in.
Ever since libvirt 1.2.8-1 was released, I cannot run my session-level virtual machines through virt-manager.
To get my VMs working again, I have to rollback to libvirt 1.2.7-1. Recently, I had to also rollback libvirt-python to version 1.2.7-1 as well.
When I start virt-manager, it reports a socket connection error. Specifically, it cannot connect to "/run/user/1000/libvirt/libvirt-sock"
Indeed, that file does not exist when libvirt 1.2.8-1 is installed. After rollback to 1.2.7-1, the socket is created in the directory specified.
I make absolutely no changes whatsoever to any config files. To rollback, I use "pacman -U /var/cache/pacman/pkgs/libvirt-1.2.7-1-x86_64.pkg.tar.gz" (and likewise for libvirt-python). Everything works. If I do a system upgrade with "pacman -Syu" then the socket connection fails... until I rollback.
I have also tried a clean install of libvirt by issuing "pacman -Rnsu libvirt virt-manager" followed by a reinstall. I have re-read the Arch Wiki and if there's something that addresses this, then I'm blind, stupid, and need someone to hit me over the head with the info.
So, am I the only one that gets this error? It wouldn't surprise me if I made some screwy config when I first set up KVM and QEMU. But it's been working since libvirt 1.2.5-1 (according to my package cache).
Last edited by CptnChristo (2014-12-04 03:30:28)
Offline
I'm using libvirt 1.2.8-2 and libvirt-python 1.2.8-1, just been testing the Python API to qemu locally, and getting the same socket errors.
Found a socket in
/run/libvirt/libvirt-socknot sure if you can manually specify a location.
Using the Python API you can connect using the qemu:///system string,
import libvirt
conn = libvirt.open("qemu:///system")Also, just found the conf files in /etc/libvirt/
/etc/libvirt/libvirtd.conf - line 110, is commented out
# unix_sock_dir = "/var/run/libvirt"Could manually set a new sock dir?
Not sure if this helps you, but found this thread and it didn't seem too old.
Last edited by hhtpcd (2014-10-03 20:50:26)
Offline
I appreciate the reply. I'd abandoned hope on this question after two or three days with no response.
Fortunately, my problem has been "fixed" with an upgrade to libvirt 1.2.10-1 and libvirt-python 1.2.10-1.
I continued to update my system with "pacman -Syu --ignore libvirt --ignore libvirt-python" every so often. Today, I omitted the ignore switches, and I was able to launch my virtual machines like normal. So, the problem was addressed with (a) the 1.2.10-1 releases, (b) other, non-ignored packages, or (c) a combination of both.
As for your suggestions, I had not tried them. But again, I appreciate the effort you made looking into it.
Offline