[Cialug] Ongoing Xen saga

[L. V. Lammert]

Had a problem with a 12.1 machine a while back, so I have been trying to
upgrade it to fix. The new Virtualization Repository is setup and the
system has been updated.


* VMM refuses to start, throwing the error:

Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file
or directory

Now, that's REALLY weird, as there IS no libvirt-sock in that location:

# ll /var/run/libvirt/
total 0
drwxr-xr-x 2 root root 40 Jan 17 14:30 libxl/
drwx------ 2 root root 60 Jan 17 14:31 network/

[libxl is empty]


* The Xen kernel appears to be running:

# ps ax | grep xen
65 ? S 0:00 [xenwatch]
66 ? S 0:00 [xenbus]
729 ? Ss 0:00 avahi-daemon: running [xen.local]
792 ? S< 0:00 [xen_pciback_wor]
986 ? S 0:00 /usr/sbin/xenstored --pid-file /var/run/xenstored.pid
1159 ? SLl 0:00 /usr/sbin/xenconsoled --pid-file=/var/run/xenconsoled.pid
1245 ? Sl 0:00 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 0 -xen-attach
-name dom0 -nographic -M xenpv -daemonize -monitor /dev/null -serial
/dev/null -parallel /dev/null -pidfile /var/run/qemu-dom0.pid


* libvirtd does not respond to any service commands:

# service libvirtd status
libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
Active: inactive (dead) since Fri 2014-01-17 14:45:29 CST; 3s ago
Process: 4354 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited,
status=0/SUCCESS)
Main PID: 4354 (code=exited, status=0/SUCCESS)

Jan 17 14:45:28 xen systemd[1]: Started Virtualization daemon.
Jan 17 14:45:29 xen libvirtd[4354]: libvirt version: 1.1.2

Even though it appears to start, it does not.


* The only entries in libxl-driver.log are cache misses:

xc: debug: hypercall buffer: total allocations:18 total releases:18
xc: debug: hypercall buffer: current allocations:0 maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:13 misses:4 toobig:1

It appears that the base problem is in libvirtd, ... any thoughts?
Suggestions on troubleshooting?

	Lee