search for: l613

...ing the xendomains init script manually with bash -x to see where it's going wrong? You need to add 'set -x' to > /usr/lib64/xen/bin/xendomains as well for full output. > Sorry, I missed the CentOS 7 bit. Looking at https://github.com/CentOS-virt7/xen/blob/xen-46/SPECS/xen.spec#L613 it looks like xendomains is not enabled by default. It looks like that happened in https://github.com/CentOS-virt7/xen/commit/01a31207ef50ec8c664fa0807ac85075dca3aa53. No clue as to why. --Sarah

...On the other hand, it is useful to expose everything that comes out of the stub driver generator to see if it is useful. And for the UPSes where we don't have good documentation, well... I'm guilty of this, too: https://github.com/networkupstools/nut/blob/master/drivers/tripplite_usb.c#L613 Any thoughts? Does "ups.debug.*" work? Just "debug.*"? "vendor.XYZ.*"? Here are the two pull requests that prompted this email: * https://github.com/networkupstools/nut/pull/431 * https://github.com/networkupstools/nut/pull/440

PJ, I didn't have virsh installed (libvirt-client).? After having installed it, it still didn't see the process: virsh autostart testvm error: failed to connect to the hypervisor error: no valid connection error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory Then, after having installed libvirt, it gives essentially the same error.