Incident affecting Google Compute Engine
SEV VMs on RHEL image fail to boot in zones -a and -b in all regions
Incident began at 2022-10-06 08:05 and ended at 2022-10-06 09:21 (all times are US/Pacific).
Previously affected location(s)
Taiwan (asia-east1)Hong Kong (asia-east2)Tokyo (asia-northeast1)Osaka (asia-northeast2)Seoul (asia-northeast3)Mumbai (asia-south1)Delhi (asia-south2)Singapore (asia-southeast1)Jakarta (asia-southeast2)Sydney (australia-southeast1)Melbourne (australia-southeast2)Warsaw (europe-central2)Finland (europe-north1)Madrid (europe-southwest1)Belgium (europe-west1)London (europe-west2)Frankfurt (europe-west3)Netherlands (europe-west4)Zurich (europe-west6)Milan (europe-west8)Paris (europe-west9)Montréal (northamerica-northeast1)Toronto (northamerica-northeast2)São Paulo (southamerica-east1)Santiago (southamerica-west1)Iowa (us-central1)South Carolina (us-east1)Northern Virginia (us-east4)Columbus (us-east5)Dallas (us-south1)Oregon (us-west1)Los Angeles (us-west2)Salt Lake City (us-west3)Las Vegas (us-west4)
| ||6 Oct 2022||09:21 PDT|| |
The issue with Google Compute Engine is believed to be affecting a very small number of customers and our Engineering Team is working on it.
If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved.
We thank you for your patience while we're working on resolving the issue.
| ||6 Oct 2022||08:05 PDT|| |
Summary: SEV VMs on RHEL image fail to boot in zones -a and -b in all regions
Description: We are experiencing an issue with Google Compute Engine.
Our engineering team continues to investigate the issue.
We will provide an update by Thursday, 2022-10-06 10:00 US/Pacific with current details.
Diagnosis: Any customer running a confidential VM in zones -a or -b with sev enabled and using the image rhel-8 may not be able to boot their vm and the vm experiences a kernel panic
Workaround: - Run the confidential VMs in zones ending with -c