On September 2, 2019 4:27 pm, Stefan Reiter wrote: > A QEMU update can change supported CPU flags, thus we need to restart > API services (especially pvestatd) to refresh their cached values.
given the recent discussion about this exact change, we could also use PVE::QemuServer::kvm_user_version() to decide whether we want to reload the CPU flag information. it's one additional stat for each pvestatd update cycle, but given all the other stuff we do there, it's probably not that expensive ;) > Signed-off-by: Stefan Reiter <s.rei...@proxmox.com> > --- > debian/triggers | 1 + > 1 file changed, 1 insertion(+) > create mode 100644 debian/triggers > > diff --git a/debian/triggers b/debian/triggers > new file mode 100644 > index 0000000..59dd688 > --- /dev/null > +++ b/debian/triggers > @@ -0,0 +1 @@ > +activate-noawait pve-api-updates > -- > 2.20.1 > > > _______________________________________________ > pve-devel mailing list > pve-devel@pve.proxmox.com > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > > _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
