Updates from editor

v-phoebh · web-flow · commit f2379c57fec7 · 2025-08-07T15:38:24.000+08:00
diff --git a/support/windows-server/virtualization/linux-virtual-machine-issue-hyper-v.md b/support/windows-server/virtualization/linux-virtual-machine-issue-hyper-v.md
@@ -1,6 +1,6 @@
 ---
 title: Troubleshoot Linux Virtual Machine Issues on Hyper-V
-description: Provides a comprehensive guide to diagnosing and resolving common issues encountered when deploying and managing Linux virtual machines (VMs) on Microsoft Hyper-V environments.
+description: Provides a comprehensive guide to diagnosing and resolving common issues encountered when deploying and managing Linux VMs in Microsoft Hyper-V environments.
 ms.date: 08/05/2025
 manager: dcscontentpm
 audience: itpro
@@ -12,15 +12,15 @@ ms.custom:
 ---
 # Troubleshoot Linux virtual machine issues on Hyper-V
 
-This article provides a comprehensive guide to diagnosing and resolving common issues in deploying and managing Linux virtual machines (VMs) on Microsoft Hyper-V environments.
+This article provides a comprehensive guide to diagnosing and resolving common issues in deploying and managing Linux virtual machines (VMs) in Microsoft Hyper-V environments.
 
-These issues might include installation challenges, live migration failures, time synchronization problems, missing VM information in management consoles, central processing unit (CPU) compatibility discrepancies, and licensing or support inquiries. Resolving these issues is critical for ensuring reliability, compatibility, and optimal performance of Linux workloads in Hyper-V infrastructures.
+These issues might include installation challenges, live migration failures, time synchronization problems, missing VM information in management consoles, central processing unit (CPU) compatibility discrepancies, and licensing or support inquiries. Resolving these issues is critical to ensuring the reliability, compatibility, and optimal performance of Linux workloads in Hyper-V infrastructures.
 
 ## Common issues observed in Linux VMs on Hyper-V
 
 - VM installation and boot issues:
 
-  - Installations of Linux operating system (OS), such as SUSE Linux Enterprise Server (SLES) 15 SP5, stall or fail on Generation 2 VMs but succeed on Generation 1.
+  - Installations of a Linux operating system (OS), such as SUSE Linux Enterprise Server (SLES) 15 SP5, stall or fail on Generation 2 VMs but succeed on Generation 1 VMs.
   - Installation menus appear, but the process fails to complete.
 
 - Live migration and VM state errors:
@@ -33,7 +33,7 @@ These issues might include installation challenges, live migration failures, tim
 - Management console and integration data issues:
 
   - Linux VM IP addresses and hostnames aren't visible in Hyper-V Manager, System Center Virtual Machine Manager (SCVMM), or other management consoles.
-  - Integration services are installed and configured, but the data remains missing.
+  - Integration services are installed and configured, but the data is still missing.
 
 - Time synchronization issues:
 
@@ -45,9 +45,9 @@ These issues might include installation challenges, live migration failures, tim
   - Missing CPU flags, such as `sse4_2`, inside Linux VMs (`cat /proc/cpuinfo`).
   - Applications or tools fail due to missing CPU instructions.
 
-- Frequent VM disconnects:
+- Frequent VM disconnections:
 
-  - Linux VMs, especially Red Hat Enterprise Linux (RHEL)-based, frequently disconnect from the Hyper-V console.
+  - Linux VMs, especially those based on Red Hat Enterprise Linux (RHEL), frequently disconnect from the Hyper-V console.
   - Error messages appear when connecting via Hyper-V Manager.
 
 - Licensing, support, and feature inquiries:
@@ -61,13 +61,13 @@ These issues might include installation challenges, live migration failures, tim
 - Configuration and compatibility:
 
   - Generation 2 VM incompatibility: Certain Linux distributions require specific Generation 2 Hyper-V settings, such as Secure Boot or UEFI, for successful installation.
-  - Unsupported Linux versions: Earlier or unlisted Linux versions might not work with Hyper-V integration components, leading to missing data or failed operations.
+  - Unsupported Linux versions: Earlier or unlisted Linux versions might not work with Hyper-V integration components, leading to data loss or operational failures.
   - Licensing and support gaps: Documentation might not cover all scenarios for OS/distribution/version compatibility.
 
 - Integration services and VM data reporting:
 
-  - Missing or misconfigured Integration services: Without proper configuration, Linux Integration services might fail to report data like IP addresses and hostnames.
-  - Console/SCVMM synchronization issues: Synchronization delays or database errors might prevent updated VM data from displaying.
+  - Missing or misconfigured integration services: Without proper configuration, Linux integration services might fail to report data like IP addresses and hostnames.
+  - Console/SCVMM synchronization issues: Synchronization delays or database errors might prevent updated VM data from being displayed.
 
 - File/state corruption and migration failures:
 
@@ -76,7 +76,7 @@ These issues might include installation challenges, live migration failures, tim
 
 - Guest OS settings and platform differences:
 
-  - RTC and time zone handling: Hyper-V provides system time to the guest RTC without time zone metadata; the guest OS settings determine interpretation.
+  - RTC and time zone handling: Hyper-V provides the system time to the guest RTC without time zone metadata; the guest OS settings determine the interpretation.
   - CPU compatibility mode: Enabling this mode restricts available CPU instructions for the guest, causing feature gaps.
 
 - External or unsupported scenarios:
@@ -86,7 +86,7 @@ These issues might include installation challenges, live migration failures, tim
 
 ## Resolve VM installation issues (Generation 2 Linux VMs)
 
-1. Review VM configuration:
+1. Review the VM configuration:
 
     - Disable Secure Boot or set it to use the correct template (for example, `MicrosoftUEFICertificateAuthority` for supported Linux distributions).
     - Ensure the VM generation matches the Linux distribution's requirements.
@@ -96,20 +96,20 @@ These issues might include installation challenges, live migration failures, tim
     - Set the firmware to boot from the correct device (DVD or ISO).
     - Remove unnecessary hardware, such as legacy network adapters.
 
-3. Retry installation: Reattempt the OS installation after making the necessary changes.
+3. Retry the OS installation after making the necessary changes.
 4. If issues persist, install the OS on a Generation 1 VM.
 
 ## Resolve live migration and state file errors
 
-1. Check event logs and error codes: Review Hyper-V logs for Event ID 21502 and error codes such as 0xC0370027, 0x80048054, or 0x80070037.
-2. Inspect VM state files: Ensure `.vmrs` and `.vmcx` files are accessible on both source and destination nodes.
+1. Check event logs and error codes. Review Hyper-V logs for Event ID 21502 and error codes such as 0xC0370027, 0x80048054, or 0x80070037.
+2. Inspect VM state files. Ensure `.vmrs` and `.vmcx` files are accessible on both the source and destination nodes.
 3. Create a new VM:
 
     1. Shut down the affected VM.
-    2. Create a new VM and attach the original OS/data disks. Match CPU and RAM settings to the original configuration.
+    2. Create a new VM and attach the original OS/data disks. Match the CPU and RAM settings to the original configuration.
 
-4. Test migration: Attempt live migration with the new VM.
-5. Monitor for recurrence: If the issue is resolved, continue monitoring the VM. If the issue persists, escalate for further disk or file system investigation.
+4. Test migration. Perform a live migration with the new VM.
+5. Monitor for recurrence. If the issue is resolved, continue monitoring the VM. If the issue persists, escalate for further disk or file system investigation.
 
 ## Resolve management console and integration data issues
 
@@ -118,19 +118,19 @@ These issues might include installation challenges, live migration failures, tim
     - Use the `lsmod | grep hv` command in the guest OS to confirm that Hyper-V modules are loaded.
     - Ensure the latest Linux integration services are installed.
 
-2. Enable data exchange: In the VM settings, ensure "Data Exchange" is enabled under integration services.
-3. Update management console: Apply the latest updates to Hyper-V, SCVMM, or other management platforms.
-4. Correct SCVMM database (if needed):
+2. Enable data exchange. In the VM settings, ensure "Data Exchange" is enabled under integration services.
+3. Update the management console. Apply the latest updates to Hyper-V, SCVMM, or other management platforms.
+4. Correct the SCVMM database (if needed):
 
     1. Back up the SCVMM database.
     2. Use SQL queries to update missing VM names or IP addresses.
 
 ## Resolve time synchronization issues
 
-1. Update integration services: Ensure the guest OS has the latest Linux integration services installed.
-2. Verify time synchronization settings: In Hyper-V Manager, ensure "Time Synchronization" is enabled.
-3. Adjust guest OS settings: Use `timedatectl` to configure the system clock and time zone correctly. For example, `timedatectl set-timezone UTC`.
-4. Delay application startup: For time-sensitive applications, delay startup until synchronization completes.
+1. Update integration services. Ensure the guest OS has the latest Linux integration services installed.
+2. Verify time synchronization settings. In Hyper-V Manager, ensure "Time Synchronization" is enabled.
+3. Adjust guest OS settings. Use `timedatectl` to configure the system clock and time zone correctly. For example, `timedatectl set-timezone UTC`.
+4. Delay application startup. For time-sensitive applications, delay startup until synchronization completes.
 
 ## Resolve CPU feature/instruction set issues
 
@@ -140,15 +140,15 @@ These issues might include installation challenges, live migration failures, tim
     Set-VMProcessor -VMName -CompatibilityForMigrationEnabled $false
     ```
 
-2. Validate in guest OS: Run `cat /proc/cpuinfo` to confirm that required CPU flags are present.
-3. Restart VM: Restart the VM to apply changes.
+2. Validate in the guest OS. Run `cat /proc/cpuinfo` to confirm that the required CPU flags are present.
+3. Restart the VM to apply the changes.
 
-## Resolve frequent VM disconnects
+## Resolve frequent VM disconnections
 
-1. Check network and VM health: Verify that network adapters are correctly configured and functioning.
-2. Review VM cloning practices: Ensure unique MAC addresses and proper cleanup after cloning.
-3. Adjust Secure Boot settings: Enable or disable Secure Boot as required by the Linux distribution.
-4. Contact Linux vendor support: Escalate issues that persist to the Linux distribution vendor.
+1. Check network and VM health. Verify that network adapters are correctly configured and functioning.
+2. Review VM cloning practices. Ensure unique MAC addresses and proper cleanup after cloning.
+3. Adjust Secure Boot settings. Enable or disable Secure Boot as required by the Linux distribution.
+4. Contact Linux vendor support. Escalate issues that persist to the Linux distribution vendor.
 
 ## Resolve licensing, support, and feature inquiries
 
@@ -158,7 +158,7 @@ These issues might include installation challenges, live migration failures, tim
 
 ## Data collection
 
-To assist in troubleshooting, gather the following logs and information:
+To help with troubleshooting, gather the following logs and information:
 
 - VML traces (for live migration):
 
@@ -195,7 +195,7 @@ To assist in troubleshooting, gather the following logs and information:
 
 ## References
 
-- [Supported Linux and FreeBSD Virtual Machines on Hyper-V](/windows-server/virtualization/hyper-v/supported-centos-and-red-hat-enterprise-linux-virtual-machines-on-hyper-v)
-- [Linux Integration Services Documentation](/windows-server/virtualization/hyper-v/supported-debian-virtual-machines-on-hyper-v)
+- [Supported CentOS and Red Hat Enterprise Linux virtual machines on Hyper-V](/windows-server/virtualization/hyper-v/supported-centos-and-red-hat-enterprise-linux-virtual-machines-on-hyper-v)
+- [Supported Debian virtual machines on Hyper-V](/windows-server/virtualization/hyper-v/supported-debian-virtual-machines-on-hyper-v)
 
 If issues persist after following these steps, collect the relevant logs and contact Microsoft Support or your Linux distribution vendor for further assistance.
