Imported VM fails to start

[mawaaz]

I exported a RHEL9 virtualbox VM on a windows 10 system and copied the created .ova file to a windows 11 computer.
I imported the exported .ova file, which seemed to complete fine.

When I start the RHEL9 VM, it fails to start and errors out with the following.
end Kernel panic - not syncing: Fatal exception

Vitualbox version is the most recent and the same version on both windows computers.

I tried the youtube fix that claims to solve this error of "Turn Windows features on or off" > "unchecking Virtual Machine Platform," but it did not.

Is there a fix for this so I don't have to re-create the vm from scratch?

[mpack]

Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

[mawaaz]

Uploaded is the log for the VM, saved while VM was shutdown.

[mpack]

You have Hyper-v enabled, plus the VM could probably use 2 CPU cores and WAY more than 16MB graphics RAM (especially with 3D acceleration enabled).

00:00:02.110988 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:02.133015 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:02.133063 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
00:00:02.133065 NEM: WHvCapabilityCodeExtendedVmExits = 0x0000000000007fff
...
00:00:02.110930 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)

On ditching Hyper-v properly, see: HMR3Init: Attempting fall back to NEM (Hyper-V is active).

[mawaaz]

Since Turn windows features on and off shows hyper-v is not selected, i'll have to look into your link.

hyper-v off

hypervoff.png (14.74 KiB) Viewed 3173 times

thanks

[scottgus1]

Since Turn windows features on and off shows hyper-v is not selected, i'll have to look into your link.

If you looked at the link first before troubling yourself with the screenshot, you'd see that the tutorial would have told you not to bother with the screenshot, because that's the wrong place to look.

[mawaaz]

Just documenting that I checked the, Turn Windows features on and off, settings to show that hyper-v is not enabled there, since googling to disable hyper-v all starts with checking Windows Features first.

[mpack]

I assure you that we are already well aware of the checkbox. Please read the FAQ.

[mawaaz]

I ran the commands from the link To turn Hyper-V off completely. The VM still fails. Is there a way I can determine the following on the windows 11 PC?

C:\Windows\System32>bcdedit /set hypervisorlaunchtype off
The operation completed successfully.

C:\Windows\System32>DISM /Online /Disable-Feature:Microsoft-Hyper-V

Deployment Image Servicing and Management tool
Version: 10.0.22621.1

Image Version: 10.0.22621.819

Disabling feature(s)
[==========================100.0%==========================]
The operation completed successfully.

bcdedit

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 11
locale en-US
inherit {bootloadersettings}
recoverysequence {98d6d533-3ac3-11ed-b24d-089204e5acda}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {98d6d530-3ac3-11ed-b24d-089204e5acda}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Off

Attached is a new log showing:

00:00:02.640881 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:02.672116 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:02.672172 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
00:00:02.672176 NEM: WHvCapabilityCodeExtendedVmExits = 0x0000000000007fff

[fth0]

Did you also turn off Windows Core Isolation > Memory Integrity?

Please see VBS/HVCI + Hyper-V for details.

@scottgus1:
I'd suggest to add parts of my post linked above to your (locked) Hyper-V Howto thread. Rationale is that on newly created Windows installations, using the bcdedit command is IME not sufficient, and the important part related to Memory Integrity is a bit "hidden" in your step number two and the link to the other Howto.

[mawaaz]

Did you also turn off Windows Core Isolation > Memory Integrity?

I just tried that and still not success in starting the VM.

2022-11-27 13_57_51-Windows Security.png (13.35 KiB) Viewed 2953 times

[mawaaz]

To recap this is everything that I did in Windows 11 and VB VMs still will not start.

Disable Hyper-V from the Control Panel
• Select Programs and Features > Turn Windows features on or off
• Expand Hyper-V, expand Hyper-V Platform, and then clear the Hyper-V Hypervisor check box.

Disable Device Guard and Credential Guard
• Local Group Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn On Virtualization Based Security > Select Disabled

Turn off Windows Core Isolation Memory Integrity
• Device security > Core isolation > Memory integrity > Toggle Off

Disable Hyper-V beyond Windows Features
• Run Command Prompt as Administrator
• Enter the command: bcdedit /set hypervisorlaunchtype off
• Some report this command was needed also: DISM /Online /Disable-Feature:Microsoft-Hyper-V

Rebooted the PC

[fth0]

Do you still have the green turtle in the status line of the VM's window (or the NEM-related log messages in the VBox.log file)? I'm asking because the VM could now have another problem than before.

Assuming the answer is yes:

On the Windows host, start msinfo32 and check the security related information in the right pane near the end.

On the Windows host, start regedit, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard and export the information tree under this key.

[mawaaz]

1. There never was a green turtle icon.
2. Attached is the exported deviceguard from the registry.
3.

On the Windows host, start msinfo32 and check the security related information in the right pane near the end.

Time Zone Pacific Standard Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.7 GB
Available Physical Memory 24.7 GB
Total Virtual Memory 36.4 GB
Available Virtual Memory 27.4 GB
Page File Space 4.75 GB
Page File C:\pagefile.sys
Kernel DMA Protection On
Virtualization-based security Not enabled
Windows Defender Application Control policy Enforced
Windows Defender Application Control user mode policy Off
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

Since I undid all the settings and changes yesterday, I re-did them today (in the order below) to provide the information above, except for the DISM command. The VM now works. I don't know if it was the order of steps or excluding the DISM command that made it work.

Disable Device Guard and Credential Guard
• Local Group Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn On Virtualization Based Security > Select Disabled

Turn off Windows Core Isolation Memory Integrity
• Device security > Core isolation > Memory integrity > Toggle Off

Disable Hyper-V beyond Windows Features
• Run Command Prompt as Administrator
• Enter the command: bcdedit /set hypervisorlaunchtype off
• I did not do this command this time: Some report this command was needed also: DISM /Online /Disable-Feature:Microsoft-Hyper-V

The only difference in steps from today, was previously I did the DISM command and I disabled device guard and memory integrity after a reboot from the bcdedit command.
Anyway thanks for all the replies.

[fth0]

Thanks for reporting back!

I disabled device guard and memory integrity after a reboot from the bcdedit command.

I'm not sure if Windows forces you to reboot after disabling Device Guard and Memory Integrity, but you also have to reboot for those changes to take effect.