** Description changed:
# Overview
Hirsute and Impish daily builds are currently not booting on Google
Confidential Compute. Confidential compute is Google's platform that
enables the use of Secure Encrypted Virtualization extension via AMD
EPYC CPUs. Booting an image with version 1.
** Description changed:
# Overview
Hirsute and Impish daily builds are currently not booting on Google
Confidential Compute. Confidential compute is Google's platform that
enables the use of Secure Encrypted Virtualization extension via AMD
EPYC CPUs. Booting an image with version 1.
** Also affects: linux-gcp (Ubuntu Hirsute)
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/1931254
Title:
Google Confidential Compute fails to boot with 1.
@Peter Gonda -- You seem to be 100% correct.
Thank you for the helpful pointer!
I have confirmed the fix and shim-side of the changes that exposed the
issue.
I will SRU the fix asap.
** No longer affects: shim-signed (Ubuntu)
--
You received this bug notification because you are a member of U
Per the last comment, if the kernel is panicking, we should look at this
from the kernel side.
** Also 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://bug
I think that this kernel needs a new fix that has been posted to KVM
mailing list. The stack trace seems to match the report and the fix.
https://www.spinics.net/lists/kernel/msg396.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Summary changed:
- Google Confidnetial Compute fails to boot with 1.47
+ Google Confidential Compute fails to boot with 1.47
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931254
Title:
Google C
