This bug was fixed in the package linux-gcp-5.4 - 5.4.0-1055.59~18.04.1
---
linux-gcp-5.4 (5.4.0-1055.59~18.04.1) bionic; urgency=medium
* bionic/linux-gcp-5.4: 5.4.0-1055.59~18.04.1 -proposed tracker (LP:
#1947075)
[ Ubuntu: 5.4.0-1055.59 ]
* focal/linux-gcp: 5.4.0-1055.59
This bug was fixed in the package linux-gcp - 5.4.0-1055.59
---
linux-gcp (5.4.0-1055.59) focal; urgency=medium
* focal/linux-gcp: 5.4.0-1055.59 -proposed tracker (LP: #1947072)
* NVME errors in confidential vms (LP: #1943902)
- swiotlb: remove the tbl_dma_addr argument to
** Changed in: linux-gcp (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-gcp (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-gcp-5.4 (Ubuntu)
Status: New => Invalid
** Changed in: linux-gcp (Ubuntu)
Status: New => Invalid
--
You
** Description changed:
See
https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view
for more info
[Impact]
Using nvme with swiotlb in confidential VMs can encounter hardware read/write
errors.
[Fix]
- The following upstream patches address this:
+ The
** Description changed:
See
https://canonical.lightning.force.com/lightning/r/Case/5004K09WBzrQAG/view
for more info
[Impact]
- Using nvme hardware that uses swiotlb in confidential VMs can encounter
hardware read/write errors.
-
+ Using nvme hardware that uses in confidential
