The manipulations that I tried
This last point works, but I don't know what to check or what to look for to restart the VM
In the console logs, i have this:
[{
"insertId": "2","jsonPayload": {
"lateBootReportEvent": {
"actualMeasurements": [
{
"hashAlgo": "SHA1",
"pcrNum": "PCR_14",
"value": "xxwkxkw,xw"
}
],
"policyMeasurements": [
{
"value": "hhhh+jjjjj=",
"hashAlgo": "SHA1",
"pcrNum": "PCR_9"
}
],
"policyEvaluationPassed": false
},
"@type": "type.googleapis.com/cloud_integrity.IntegrityEvent",
"bootCounter": "31"
},
"resource": {
"type": "gce_instance",
"labels": {
"instance_id": "00000000",
"zone": "europe-000000
"project_id": "HHHHHHHHH"
}
},
"timestamp": "2022-04-28T21:35:52.092570946Z",
"severity": "ERROR",
"logName": "/logs/compute.googleapis.com%2Fshielded_vm_integrity",
"receiveTimestamp": "2022-04-28T21:35:54.103571412Z"
}]
Does the shielded_vm_integrity type error speak to you please?
Thank you
Your VM is failing to boot because of a boot integrity check. You resized the disk which changed the boot configuration.
The solution is to disable the shielded VM options:
CLI command:
gcloud compute instances update VM_NAME \
--no-shielded-secure-boot \
--no-shielded-vtpm \
--no-shielded-integrity-monitoring
Once your VM is running successfully, you can enable these features.
Determining the cause of boot integrity validation failure
There is a free book download on TPM which contains details on the Platform Configuration Registers mentioned in your logs (PCR-9 and PCR-14):