[pve-devel] applied: [PATCH 0/2] Fix systemd ordering for qmeventd.service

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

On 12.11.20 16:43, Stefan Reiter wrote:
> Reported in the forum:
> https://forum.proxmox.com/threads/shutdown-reboot-error-nodes.78906/
> 
> Since qmeventd is now responsible for stopping QEMU instances after they shut
> down, it needs to keep running for as long as there are guests, otherwise the
> host will hang waiting for guests to exit.
> 
> Fix this in pve-guests.service for regular VMs and pve-ha-lrm.service for HA.
> 
> I'm not too familiar with systemd services, but I figured the After is enough,
> since Wants implies that qmeventd must be running for the services to work,
> which is not true, the VMs will work fine, as long as the user takes care of
> cleanup themselves somehow or doesn't use shutdown (and by default
> qmeventd.service is enabled anyway). But easy enough to change if that's wrong.
> 
> Not sure how to handle version bumping, I'd assume qemu-server needs a depends
> on new pve-manager and pve-ha-manager to ensure non-broken behaviour?
> 
> 
> manager: Stefan Reiter (1):
>   stop qmeventd.service after pve-guests.service
> 
>  services/pve-guests.service | 1 +
>  1 file changed, 1 insertion(+)
> 
> ha-manager: Stefan Reiter (1):
>   stop qmeventd.service after pve-ha-lrm.service
> 
>  debian/pve-ha-lrm.service | 1 +
>  1 file changed, 1 insertion(+)
> 



applied the reverse to qemu-server, thanks!