It seems on the former deployment I hit some memory bug which broke and stalled quite some allocations. While I haven't found what was causing that (would be an interesting bug report) the renewed systems seems good.
And in that environment I was able to verify the fix just as expected. Sorry for the noise before, but I try to take these verification serious :-/ With the fix in place I see a correct movement to node 8 for example: Wed Jul 17 12:33:16 2019: Advising pid 47693 (qemu-system-ppc) move from nodes (0,8) to nodes (8) Wed Jul 17 12:33:16 2019: PID 47693 moved to node(s) 8 in 0.0 seconds Wed Jul 17 12:38:21 2019: Advising pid 47693 (qemu-system-ppc) move from nodes (8) to nodes (8) Wed Jul 17 12:38:21 2019: PID 47693 moved to node(s) 8 in 0.0 seconds Wed Jul 17 12:43:26 2019: Advising pid 47693 (qemu-system-ppc) move from nodes (8) to nodes (8) Wed Jul 17 12:43:26 2019: PID 47693 moved to node(s) 8 in 0.0 seconds Set verification ok for Bionic, upgrading to Disco for the verification there ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832915 Title: numad crashes while running kvm guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1832915/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
