The service worked fine even through a full release upgrade from Bionic to Debian I saw it moving processes just fine.
When on Disco I pushed some load in the guest to get more movements but things worked fine still.
Setting verified for Disco.
P.S. I also think I have found the "other" crash that I have seen, it seems to be triggered by restarting numad while a numad-guided process is active. So in the scenario here get your guest first and then restart numad. I'm filing a bug 1836913 for it so that someone can take a look at that later ...
To be sure that this isn't caused by this update (already quite sure since the place is different) I downgraded to
sudo apt install numad=0.5+20150602-5
And there this issue is triggered as well on restart.
The service worked fine even through a full release upgrade from Bionic to Debian I saw it moving processes just fine.
When on Disco I pushed some load in the guest to get more movements but things worked fine still.
Setting verified for Disco.
P.S. I also think I have found the "other" crash that I have seen, it seems to be triggered by restarting numad while a numad-guided process is active. So in the scenario here get your guest first and then restart numad. I'm filing a bug 1836913 for it so that someone can take a look at that later ... 5+20150602- 5
To be sure that this isn't caused by this update (already quite sure since the place is different) I downgraded to
sudo apt install numad=0.
And there this issue is triggered as well on restart.