Public bug reported: 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. ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2105142 Title: GCP kernels need CONFIG_VIRTIO_BALLOON=m (not =y) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2105142/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
