This bug was fixed in the package linux-gcp - 5.11.0-1008.8+21.10.1
---------------
linux-gcp (5.11.0-1008.8+21.10.1) impish; urgency=medium
* impish/linux-gcp: 5.11.0-1008.8+21.10.1 -proposed tracker (LP:
#1927565)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms package versions
-- Paolo Pisati <paolo.pis...@canonical.com> Thu, 20 May 2021 13:01:39
+0200
** Changed in: linux-gcp (Ubuntu)
Status: Invalid => Fix Released
--
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/1927050
Title:
Enable BLK_DEV_NVME =y to support "shielded VM minimal images"
Status in linux-gcp package in Ubuntu:
Fix Released
Status in linux-gcp-4.15 package in Ubuntu:
Invalid
Status in linux-gcp source package in Bionic:
Invalid
Status in linux-gcp-4.15 source package in Bionic:
Fix Released
Status in linux-gcp source package in Focal:
Fix Released
Status in linux-gcp-4.15 source package in Focal:
Invalid
Status in linux-gcp source package in Groovy:
Fix Released
Status in linux-gcp-4.15 source package in Groovy:
Invalid
Status in linux-gcp source package in Hirsute:
Fix Released
Status in linux-gcp-4.15 source package in Hirsute:
Invalid
Bug description:
This is requested by CPC -- see the title.
[Impact]
nvme.ko exists outside the kernel currently
[Fix]
Enable BLK_DEV_NVME=y
[Test]
Tested by CPC crew / Google:
> The test images have passed testing and we would like this enabled so we
> can have minimal images boot with NVME boot disk and so we can enable
> GCE confidential VMs with minimal images.
[Regression Potential]
Not aware of any.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1927050/+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
