After multiple reboots, it turns out that the problematic host's boot arg is "nmi_watchdog=0".
If I set the host with only those: sdeziel@xeon:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic root=UUID=40a302c9-82d9-4574-ac2f-efcf5c9d126f ro hugepages=3008 kaslr possible_cpus=2 transparent_hugepage=never vsyscall=none All 17 guests boot fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742286 Title: [regression] Xenial host with 4.4.0-108.131 fails to power some KVM guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
