This bug is awaiting verification that the linux-gcp/6.8.0-1030.32 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-gcp' to 'verification-done-noble- linux-gcp'. If the problem still exists, change the tag 'verification- needed-noble-linux-gcp' to 'verification-failed-noble-linux-gcp'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-gcp-v2 verification-needed-noble-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
