|
1 | 1 | --- |
2 | | -title: Linux VMs fail to boot due to Hyper-V driver issues |
3 | | -description: Provides solutions to Azure Linux VM boot failures that occur because Hyper-V drivers are missing or disabled. |
| 2 | +title: Troubleshoot LIS/Hyper-V Driver Issues on Linux Virtual Machines |
| 3 | +description: Provides solutions to Azure Linux VM issues that occur because Hyper-V drivers are missing or disabled. |
4 | 4 | ms.date: 02/26/2025 |
5 | 5 | ms.reviewer: divargas, msaenzbo, v-weizhu |
6 | 6 | ms.custom: sap:My VM is not booting, linux-related-content |
7 | 7 | --- |
8 | | -# Azure Linux virtual machines fail to boot due to Hyper-V driver issues |
| 8 | +# Troubleshoot LIS/Hyper-V driver issues on Linux virtual machines |
9 | 9 |
|
10 | 10 | **Applies to:** :heavy_check_mark: Linux VMs |
11 | 11 |
|
12 | | -When you run a Linux Virtual Machine (VM) on Azure, the Hyper-V drivers, also known as Linux Integration Services (LIS) drivers, are crucial for proper VM operations. These drivers allow the VM to communicate with the underlying Azure hypervisor. If these drivers are missing or not properly loaded, the VM might fail to boot. This article provides solutions to boot failures due to Hyper-V driver issues in Azure Linux VMs. |
| 12 | +When you run a Linux Virtual Machine (VM) on Azure, the Hyper-V drivers, also known as Linux Integration Services (LIS) drivers, are crucial for proper VM operations. These drivers allow the VM to communicate with the underlying Azure hypervisor. If these drivers are missing or not properly loaded, the VM might fail to boot. This article provides solutions to LIS/Hyper-V driver issues in Azure Linux VMs. |
13 | 13 |
|
14 | 14 | ## Prerequisites |
15 | 15 |
|
@@ -94,7 +94,7 @@ dracut:/# |
94 | 94 |
|
95 | 95 | ## Cause |
96 | 96 |
|
97 | | -Here are some reasons for VM boot failures: |
| 97 | +If LIS/Hyper-V drivers are missing or not correctly loaded, the VM might not start because of the following reasons: |
98 | 98 |
|
99 | 99 | - Missing disk and network drivers |
100 | 100 |
|
@@ -199,7 +199,9 @@ Here are some reasons for VM boot failures: |
199 | 199 |
|
200 | 200 | 4. Rebuild the initial RAM disk image for your affected kernel by following the steps in [Regenerate missing initramfs manually](kernel-related-boot-issues.md#missing-initramfs-manual). |
201 | 201 |
|
202 | | -## Verify the network driver is functional after a fresh boot or reboot |
| 202 | +## FAQ |
| 203 | + |
| 204 | +### If I'm experiencing some issue, such as connectivity, how can I make sure that the network driver, hv_netvsc, is working as expected after a fresh start or restart of the system? |
203 | 205 |
|
204 | 206 | To confirm that the Hyper-V network driver (`hv_netvsc`) is active and functional, check the system logs and look for the following entry: |
205 | 207 |
|
|
0 commit comments