Comment # 6 on bug 1201565 from B Allen

I(In reply to James Fehlig from comment #5)
> Sorry, but it's not clear to me which files should be moved. Comment #1
> suggests moving libvirt-guests state file from /var/lib/libvirt/ to
> /var/run/libvirt/. Are the contents of /var/run guaranteed to persist across
> reboots?
I am not 100% sure about OpenSUSE, but on other systems /var/run is tmpfs and
does not persist and I think is not required to persist by standards, so what I
suggested in #1 is wrong (I was confused about how this file is used). The LST
file is created during stop, and read during start, so it does need to persist.
/var/lib is perhaps the correct place for it then, and the SELinux policy just
needed to be changed?

> Or is this about moving libvirt-guests.sh from /usr/lib64/libvirt/ to
> libexecdir? Note that since the early packaging days, libvirt had defined
> libexecdir as '%{_libdir}/libvirt'. I don't recall why, or know the
> ramifications of suddenly changing it.
There was no SELinux policy issue with the .sh living there, it executed fine -
the issue was with not being able to write the LST file during stop so it can
be read on next boot during start. As far as filesystem organization, it does
seem odd having an executable .sh in that directory, but I am not sure what the
established standard is here for OpenSUSE.