You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/trusted-launch-faq.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -393,7 +393,9 @@ This section answers questions about specific states, boot types, and common boo
393
393
This section provides additional details on Trusted Launch deployment failures for you to take proper action to prevent them.
394
394
395
395
```
396
-
Virtual machine <vm name> failed to create from the selected snapshot because the virtual Trusted Platform Module (vTPM) state is locked. To proceed with the VM creation, please select a different snapshot without a locked vTPM state. For more assistance, please refer to “Troubleshooting locked vTPM state” in FAQ page at https://aka.ms/TrustedLaunch-FAQ.
396
+
Virtual machine <vm name> failed to create from the selected snapshot because the virtual Trusted Platform Module (vTPM) state is locked.
397
+
To proceed with the VM creation, please select a different snapshot without a locked vTPM state.
398
+
For more assistance, please refer to “Troubleshooting locked vTPM state” in FAQ page at https://aka.ms/TrustedLaunch-FAQ.
397
399
```
398
400
This deployment error happens when the snapshot or restore point provided is inaccessible or unusable for the following reasons:
399
401
1. Corrupt virtual machine guest state (VMGS)
@@ -407,8 +409,8 @@ Retrying with the same snapshot/restore point will result in the same failure.
407
409
To resolve this:
408
410
409
411
1. On the source Trusted Launch VM where the snapshot or restore point was generated, the vTPM errors must be rectified.
410
-
a. If the vTPM state was modified by a workload on the virtual machine, you need to use the same to check the error states and bring the vTPM to a non-error state.
411
-
b. If TPM tools were used to modify the vTPM state, then you should use the same tools to check the error states and bring the vTPM to a non-error state.
412
+
1. If the vTPM state was modified by a workload on the virtual machine, you need to use the same to check the error states and bring the vTPM to a non-error state.
413
+
1. If TPM tools were used to modify the vTPM state, then you should use the same tools to check the error states and bring the vTPM to a non-error state.
412
414
413
415
Once the snapshot or restore point is free from these errors, you can use this to create a new Trusted Launch VM.
0 commit comments