System Does Not Boot Under Hyper-V on Windows Server 2016
This document (000021464) is provided subject to the disclaimer at the end of this document.
Environment
Any EFI OS running in a Hyper-V Gen2 virtual machine on Windows Server 2016
Situation
When booting an OS under a Gen2 Hyper-V virtual machine on Windows Server 2016, it may sometimes boot normally, and other times it may fail to boot. The frequency of the failures varies, with newer kernels appearing to be more likely to fail to boot.
Looking in the Hyper-V logs, the following message is seen:
After a failure, the system then returns to the Grub2 menu as if the reset button was pressed. This might repeat several times before the virtual machine powers down.
Attempts to boot from other OS disks fail similarly. Often, it is found that booting the rescue image on a SLES 15 installation ISO will result in the same behavior.
Looking in the Hyper-V logs, the following message is seen:
The guest operating system reported that it failed with the following error code: 0x1E
After a failure, the system then returns to the Grub2 menu as if the reset button was pressed. This might repeat several times before the virtual machine powers down.
Attempts to boot from other OS disks fail similarly. Often, it is found that booting the rescue image on a SLES 15 installation ISO will result in the same behavior.
Resolution
This is a bug in Hyper-V for Windows Server 2016. Upgrade to Windows Server 2019 or newer where this bug has not been observed.
A process is also described here under the heading "Additional Information" for getting a virtual machine to boot without upgrading the hypervisor as a temporary workaround if needed.
A process is also described here under the heading "Additional Information" for getting a virtual machine to boot without upgrading the hypervisor as a temporary workaround if needed.
Cause
Hyper-V creates a condition that causes the Linux kernel to fail to run correctly. It appears there is some amount of randomness or a timing requirement involved in triggering the bug, so the symptom does not always show up. It is theorized that the problem has something to do with Hyper-V's implementation of VLAN detection.
Status
Reported to Engineering
Additional Information
If a VM is showing this behavior, it may be possible to get it to boot by doing the following.
After using this workaround, check that your workloads are running correctly and restart them if needed.
- Go to the VM's settings in Hyper-V, select "Network Adapter", set "Virtual Switch" to "Not connected".
- Boot the VM. You should find that it is able to boot now.
- Re-connect the network adapters in the VM settings.
- Run the following command to bring up interfaces according to your configuration.
# wicked ifup all
After using this workaround, check that your workloads are running correctly and restart them if needed.
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000021464
- Creation Date: 05-Jun-2024
- Modified Date:07-Jun-2024
-
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Server for SAP Applications
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
