Yes, please disable CONFIG_ARCH_HIBERATION_POSSIBLE and CONFIG_ARCH_SUSPEND_POSSIBLE and the obligatory dependencies. We don't rely on these guest cooperation to pause or suspend a VM.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1776293 Title: [Hyper-V] Disable CONFIG_HOTPLUG_CPU in linux-azure Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Bionic: In Progress Bug description: While Hyper-V may present all potential CPUs via ACPI MADT, CPU add/remove is not supported. This results in kernel data structures created for the largest potential size based on the number of CPUs when those CPUs will never be added during the time the guest is up (it can certainly be resized when it's down and deallocated). Please disable CONFIG_HOTPLUG_CPU in linux-azure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1776293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
