We are currently facing the same problems with Linux Virtual Machines running Ubuntu 18.04 and 20.04, both LTS releases.
Upon examining the Event Viewer on one of the Hosts machines, there's a critical error message:
Event ID: 18602
Source: Hyper-V-Worker
<VM_NAME> has encountered a fatal error and a memory dump has been generated. The guest operating system reported that it failed with the following error code: 0x1E. If the problem persists, contact Product Support for the guest operating system. (Virtual machine ID XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX)
These are some fixes we have tried so far:
- Install linux-azure packages and kernel;
- Enable Secure boot on Guest Machine;
- Scan the disk for corruption;
- Try different kernels.
We couldn't try other fixes like Updating the Hyper-V Server to 2019 or disabling secure boot on Host machines, the reason being that we have around 200 VMs across 8 Hosts.
Current configuration:
- 2 Clusters;
- 4 Hosts per cluster;
- All hosts are running Hyper-V 2016.
Unfortunately, we are not the only ones with the issue, the bug also affects Debian and RHEL distros:
We are currently facing the same problems with Linux Virtual Machines running Ubuntu 18.04 and 20.04, both LTS releases.
Upon examining the Event Viewer on one of the Hosts machines, there's a critical error message:
Event ID: 18602
Source: Hyper-V-Worker
<VM_NAME> has encountered a fatal error and a memory dump has been generated. The guest operating system reported that it failed with the following error code: 0x1E. If the problem persists, contact Product Support for the guest operating system. (Virtual machine ID XXXXXXXX- XXXX-XXXX- XXXX-XXXXXXXXXX XX)
These are some fixes we have tried so far:
- Install linux-azure packages and kernel;
- Enable Secure boot on Guest Machine;
- Scan the disk for corruption;
- Try different kernels.
We couldn't try other fixes like Updating the Hyper-V Server to 2019 or disabling secure boot on Host machines, the reason being that we have around 200 VMs across 8 Hosts.
Current configuration:
- 2 Clusters;
- 4 Hosts per cluster;
- All hosts are running Hyper-V 2016.
Unfortunately, we are not the only ones with the issue, the bug also affects Debian and RHEL distros:
https:/ /access. redhat. com/solutions/ 4796261 /docs.microsoft .com/en- us/answers/ questions/ 530961/ windows- server- 2016-hyper- v-boot- error-w- virtual- s.html
https:/
These ones are the same: /docs.microsoft .com/en- us/answers/ questions/ 52937/failure- to-boot- on-red- hat-enterprise- linux-rhel- o.html /social. technet. microsoft. com/Forums/ en-US/1da1f987- 52f0-4304- 84f1-2c0ab52f35 86/failure- to-boot- on-red- hat-enterprise- linux-rhel- or-centos- 8-using- hyperv- 2016?forum= linuxintegratio nservices /social. technet. microsoft. com/Forums/ en-US/3c48c962- a28d-44bb- bd80-5b7a902404 d8/failure- to-boot- on-red- hat-enterprise- linux-rhel- or-centos- 8-using- hyperv- 2016?forum= winserverhyperv /www.reddit. com/r/HyperV/ comments/ hx2cps/ failure_ to_boot_ on_red_ hat_enterprise_ linux_rhel/
https:/
https:/
https:/
https:/