Skip to main content

Windows Server 2019/2022 VMs gets to the recovery mode after reboot

  • Updated
Applies to:
  • Virtuozzo Hybrid Server 7.x
  • Virtuozzo Hybrid Infrastructure 5.x
  • Virtuozzo Hybrid Infrastructure 4.x

Symptoms

One or multiple VMs with Windows guest OS boots to the Recovery mode after VM reboot and additionally both following conditions are true:

1. The recovery console is unable to detect any drives on VM:

--------------------------------------------------------
wmic logicaldisk get deviceid, volumename, description
--------------------------------------------------------

all commands below show no disks detected:

diskpart
list disk

2. Windows had KB5030214 and/or KB5030216 had been installed before the issue occurred.


Cause

The root cause is within a SeaBIOS firmware. Windows update KB5030214 breaks the code which detects bootable Hyper-V devices in SeaBIOS and this makes the Windows guest unable to detect any disks and forces it to fall into a rescue mode.

Resolution

Virtuozzo Hybrid Server

The issue is fixed in Virtuozzo Hybrid Server 7.5 Update 5 Hotfix 1 in scope of PSBM-150623.

Update the VHS host with affected VMs to this version and stop/start the affected VMs.

Important: sending the VM to reboot will not apply the fix, stop/start sequence is required)

Virtuozzo Hybrid Infrastructure 

The issue is fixed in Virtuozzo Hybrid Infrastructure 5.4 Update 4 (build 5.4.4-112) in scope of VSTOR-74916.

Update your VHI cluster to this version and stop/start the affected VMs.

Important: sending the VM to reboot will not apply the fix, stop/start sequence is required)

 

Workaround

For VHS versions earlier than Hybrid Server 7.5 Update 5 Hotfix 1 and VHI versions 5.1-5.3 the below manual workaround is available which does not require updating the whole cluster. However the preferable way is to update your cluster to the latest version.

The suggested workaround is to update the affected SeaBIOS packages manually. Please follow the steps below. 

Virtuozzo Hybrid Server

1. Use the command line on the node where the specified VM or its instance is registered. Install the update on the affected package:

# yum install -y seabios-bin-1.11.0-2.vz7.5.noarch seavgabios-bin-1.11.0-2.vz7.5.noarch

2. Stop/start the affected VMs (do not use reboot, the changes will get propagated only after stop and start of a VM.

Virtuozzo Hybrid Infrastructure

1. Download the following SeaBIOS packages to the affected host from this URL:

seabios-bin-1.11.0-2.vz7.5.noarch
seavgabios-bin-1.11.0-2.vz7.5.noarch

in CLI

# wget https://repo.virtuozzo.com/vz-platform/releases/hci-5.4.4-112/x86_64/os/Packages/s/seabios-bin-1.11.0-2.vz7.5.noarch.rpm https://repo.virtuozzo.com/vz-platform/releases/hci-5.4.4-112/x86_64/os/Packages/s/seavgabios-bin-1.11.0-2.vz7.5.noarch.rpm


2. Install them manually:

# yum localupdate seabios-bin-1.11.0-2.vz7.5.noarch.rpm seavgabios-bin-1.11.0-2.vz7.5.noarch.rpm

 

3. Stop/start the affected VMs (do not use reboot, the changes will get propagated only after stop and start of a VM.

NOTE: In case you decide to follow the manual workaround path instead of updating the whole cluster to the required mentioned version and your VHI cluster is running on versions 5.1-5.3 - make sure SeaBIOS packages versions remain intact after performing cluster-wide updates in future.

Related articles