$ lsmod | grep balloon virtio_balloon 24576 0 $ uname -r 5.4.0-1149-gcp
** Tags removed: verification-needed-focal-linux-gcp ** Tags added: verification-done-focal-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2105142 Title: GCP kernels need CONFIG_VIRTIO_BALLOON=m (not =y) Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp source package in Bionic: Fix Committed Status in linux-gcp source package in Focal: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Noble: Fix Committed Status in linux-gcp source package in Oracular: Fix Committed Status in linux-gcp source package in Plucky: Fix Released Bug description: SRU Justification [Impact] Google requested that the virtio_balloon module be made loadable, rather than built-in. This is to support disabling the module at runtime, which is specified as possible in their documentation: https://cloud.google.com/compute/docs/dynamic-resource- management#disabling_the_virtio_memory_balloon_device [Fix] Change CONFIG_VIRTIO_BALLOON to build the driver as a loadable module rather than a built-in, drivers/virtio/* is already in the inclusion list, so the driver will be included in the main modules package. [Test Plan] List files in the linux-modules package and verify that virtio_balloon.ko is there. [Regression potential] The regression potential is very low since the module will still be included with all cloud installations and a user has to manually disable it to get different behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2105142/+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
