group.of.nepali.translators team mailing list archive
  
  - 
     group.of.nepali.translators team group.of.nepali.translators team
- 
    Mailing list archive
  
- 
    Message #49140
  
 [Bug 2105142] Re: GCP kernels need	CONFIG_VIRTIO_BALLOON=m (not =y)
  
** No longer affects: linux-gcp (Ubuntu Xenial)
-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
  New
Status in linux-gcp source package in Focal:
  New
Status in linux-gcp source package in Jammy:
  New
Status in linux-gcp source package in Noble:
  New
Status in linux-gcp source package in Oracular:
  New
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