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/devtest-labs/troubleshoot-vm-environment-creation-failures.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,24 +20,25 @@ If you're using the Azure portal, the first place to look at is the **notificati
20
20
### VM in corrupted state
21
21
If you see the status of your VM in the lab as **Corrupted**, the underlying VM might have been deleted from the **Virtual Machine** page that user can navigate to from the **Virtual Machines** page (not from the DevTest Labs page). Clean up your lab in DevTest Labs by deleting the VM from the lab. Then, recreate your VM in the lab.
22
22
23
-

24
-
25
23
:::image type="content" source="media/troubleshoot-vm-environment-creation-failures/vm-corrupted-state.png" alt-text="Screenshot showing a VM in a corrupted state." lightbox="media/troubleshoot-vm-environment-creation-failures/vm-corrupted-state.png":::
26
24
27
25
## Activity logs
28
-
Look at activity logs if you're investigating a failure sometime after attempting the creation of your VM or environment. There are three types of activity logs available from the Lab page; logs for activities affecting lab configuration and policies, logs for VMs and logs for environments. This section shows you how to find these logs.
26
+
Look at activity logs if you're investigating a failure sometime after attempting the creation of your VM or environment. There are three types of activity logs available from the Lab page; logs for activities affecting lab configuration and policies, logs for VMs and logs for environments. The error you're troubleshooting might be in any one of these logs, depending on it's source. This section shows you how to find these logs.
29
27
30
-
## Activity logs for lab configuration and policies
28
+
## Activity log for lab configuration and policies
31
29
32
30
Activity logs for configuration and policies show events generated by the lab configuration settings or any lab policies you set. In this example, you see the error that details the VM creation failure referenced in the [portal notification](#portal-notifications) shown earlier. To see the activity logs for lab configuration and policies, follow these steps:
33
31
34
32
1. On the home page for your lab, select **Configuration and policies** on the left menu.
35
33
1. On the **Configuration and policies** page, select **Activity log** on the menu.
36
34
1. In the activity log items, expand the failed operation `Create a virtual machine`, then select the failed operation `Add or modify virtual machine` to see the details.
37
-
1. In the right pane, switch to the JSON tab. You see the details in the JSON view of the log.
38
35
39
36
:::image type="content" source="media/troubleshoot-vm-environment-creation-failures/configuration-policies-activity-log.png" alt-text="Screenshot of Azure portal showing a Lab Configuration and policies activity log." lightbox="media/troubleshoot-vm-environment-creation-failures/configuration-policies-activity-log.png":::
40
37
38
+
1. In the right pane, switch to the JSON tab. You see the details in the JSON view of the log.
39
+
40
+
:::image type="content" source="media/troubleshoot-vm-environment-creation-failures/configuration-policies-error-json.png" alt-text="Screenshot of Azure portal showing details of a Lab Configuration and policies activity log event in JSON." lightbox="media/troubleshoot-vm-environment-creation-failures/configuration-policies-error-json.png":::
41
+
41
42
1. Look through the JSON log until you find the `statusMessage` property. It gives you the main error message and further detail information, if applicable. The following JSON is an example for the core quoted exceeded error seen earlier in this article.
42
43
43
44
```json
@@ -54,7 +55,7 @@ Activity logs for virtual machines show events generated by the virtual machine,
54
55
1. On the home page for your lab, select the VM to launch the **Virtual Machine** page.
55
56
1. On the **Virtual Machine** page, in the **General** section of the left menu, select **Activity log** to see all logs associated with the VM.
56
57
57
-
:::image type="content" source="media/troubleshoot-vm-environment-creation-failures/vm-activity-log.png" alt-text="Screenshot of Azure portal showing a Lab Configuration and policies activity log." lightbox="media/troubleshoot-vm-environment-creation-failures/vm-activity-log.png":::
58
+
:::image type="content" source="media/troubleshoot-vm-environment-creation-failures/vm-activity-log.png" alt-text="Screenshot of Azure portal showing a virtual machine activity log." lightbox="media/troubleshoot-vm-environment-creation-failures/vm-activity-log.png":::
58
59
59
60
1. Select the event you're interested in to see the details.
60
61
1. To see the details of the event, switch to the JSON tab.
@@ -86,4 +87,5 @@ To see the lab template deployment logs, follow these steps:
86
87
1. You see details about the operation that failed in the **Operation details** window.
87
88
88
89
## Next steps
90
+
89
91
See [Troubleshooting artifact failures](devtest-lab-troubleshoot-artifact-failure.md).
0 commit comments