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: support/azure/virtual-machines/windows/understand-vm-reboot.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,7 +102,7 @@ Because some host server faults can be specific to that server, a repeated VM re
102
102
103
103
### Auto-recovery
104
104
105
-
The Azure platform is designed to handle host node issues with minimal impact on VM performance. When a host node encounters a problem, Azure first attempts the least disruptive recovery method, which is to reboot the host. If rebooting the host isn't possible or if the issue is hardware-related, Azure initiates an automatic recovery action to take the faulty host out of rotation for further investigation. As part of this automatic recovery, a process known as service healing will automatically relocate all VMs on the faulty host to another healthy one. This process is usually completed within 15 minutes, although the recovery time can vary depending on factors such as the host's memory size and used recovery methods. Service healing is typically used as a last resort for hardware failures to ensure that VMs continue to operate without significant downtime.
105
+
The Azure platform is designed to handle host node issues with minimal impact on VM performance. When a host node encounters a problem, Azure first attempts the least disruptive recovery method, which is to reboot the host. If rebooting the host isn't possible or if the issue is hardware-related, Azure initiates an automatic recovery action to take the faulty host out of rotation for further investigation. As part of this automatic recovery, a process known as service healing will automatically relocate all VMs on the faulty host to another healthy one. This process is usually completed within 15 minutes, although the recovery time can vary depending on factors such as the host's memory size and recovery methods used. Service healing is typically used as a last resort for hardware failures to ensure that VMs continue to operate without significant downtime.
106
106
107
107
For more details about how Azure handles these scenarios, see [Service Healing – Auto-recovery of Virtual Machines](https://azure.microsoft.com/blog/service-healing-auto-recovery-of-virtual-machines/).
108
108
@@ -117,7 +117,7 @@ Unplanned maintenance include the following:
117
117
118
118
### VM crashes
119
119
120
-
VMs might restart due to internal VM issues or hardware issues as described above such as an OS disk issue. The workloads or role running on the VM might trigger a bug check in the guest OS. To find the crash reason, check system and application logs for Windows VMs, and serial logs for Linux VMs. Collecting a memory dump is usually the best way to identify the root cause.
120
+
VMs might restart due to internal VM issues or hardware issues, such as an OS disk issue, as described earlier. The workload or role running on the VM might trigger a bug check in the guest OS. To find the reason for the crash, check the system and application logs for Windows VMs and the serial logs for Linux VMs. Collecting a memory dump is usually the best way to identify the root cause.
121
121
122
122
For more information, see the following articles:
123
123
@@ -132,8 +132,8 @@ VMs in Azure rely on virtual disks for operating system and data storage that is
132
132
133
133
In rare circumstances, a widespread issue can affect multiple servers in an Azure datacenter. If this issue occurs, the Azure team sends email notifications to the affected subscriptions. You can check the [Azure Service Health dashboard](https://azure.microsoft.com/status/) and the Azure portal for the status of ongoing outages and past incidents.
134
134
135
-
## Diagnose VM Restarts
135
+
## Diagnose VM restarts
136
136
137
-
You can use the Diagnose and Solve blade on the VM blade to run additional diagnostics. This may uncover more specific reasons for your recent VM restart. If there is any Guest OS issue, collect a memory dump and contact support.
137
+
You can use the **Diagnose and Solve** blade on the VM blade to run additional diagnostics. This may uncover more specific reasons for your recent VM restart. If there is any guest OS issue, collect a memory dump and contact support.
138
138
139
139
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
0 commit comments