On 30 Jun 2017, at 12:41, Petr Kotas <pkotas(a)redhat.com>
I am kindly asking for help with understanding the origin of conflict within the
libvirt-guests.service and vdsmd.service.
I am working on a graceful VM shutdown as described by the feature in a Bugzilla
One way (the simplest one as described in the Bugzilla) of achieving the required
functionality is to utilize "libvirt-guests.service", which does exactly what is
as long as it is properly configured to ON_SHUTDOWN=shutdown
The second option is to write a new service that does the shutdown
and utilizes the vdsm. Since I am new, I do not know what is the best solution.
less new services == better solution:)
Staying with the fist one I have discovered an old conflict between
"vdsmd.service" and "libvirt-guests.service" explained in bug
. I have tried to reproduce described
scenario and found that it is no longer an issue. Therefore I have created a proposal
draft patch to start a discussion, whether it is really needed or not.
it’s ancient, from the pre-systemd times when the libvirt-guest service was just…not good
Further, the research in git history showed this conflict precedes the git history,
effectively blocking me in understanding details.
right….it’s time to test it again. It should work just fine these days
Does somebody know about this issue? I am grateful for any information that can point me
in the right direction.
Thank you in advance for any help.
Devel mailing list