virtualbox.org

Hello,
Thanks for taking some of your precious time checking my case

I have configured a windows server 2019 machine on my VBOX and I have an error when launching it.
Virtualization is enabled on my BIOs.
I have attached all requested log in a .zip file

Error :

VirtualBox - Guru Meditation

A critical error has occurred while running the virtual machine and machine
execution has been stopped.

[...]

Press OK if you want to power off the machine of press Ignore if you want
to leave it as for debugging. Please note that debugging requires special
knowledge and tools, so it is recommended to press OK no

Only two things I see:
Windows 2019 likely uses Hyper-V paravirtualization, and your guest is set to None. Paravirtualizaton is just a communication channel, and does not enable or disable Windows's Hyper-V. Set paravirtualization back to Hyper-V.

Your host has 4 processor cores, you only have 1 in the guest, and Server 2019, being 10 on server steroids, probably would like 2 cores.

Thanks for your help

I applied what you recommended

and it still gives the same error

My One drive link for logs is in the txt file as i'm not allowed to post links , being a member here for less than one day

scottgus1 wrote:Windows 2019 likely uses Hyper-V paravirtualization, and your guest is set to None.

There maybe is a bug in VirtualBox, which I didn't bother to report on the Bugtracker (for being ignored there in the past ):

If you create a VM with Basic > Version set to Windows 2019 (64-bit), and System > Acceleration > Paravirtualization Interface set to Default, the VM is running with the Provider None. This also applies to Windows 2016 (64-bit).

fth0 wrote:the VM is running with the Provider None

Sho nuff, looks like a bug to me!

Nwer, please post logs like you did at the beginning.

Ok so here is the update,

I tried on configuring a windows 10 machine and it works fine.
I made the changes you asked for (Paravirtualization to Hyper-V and processors cores to 2
and it's the same error

logs : first part file
-------------------------
After this I tried another turning Hyper-V off executing these on CMD :

bcdedit /set hypervisorlaunchtype off

shutdown -s -t 2

I set Paravirtualization to Default
logs : second part

After reading 550 MB from the ISO file, some software in the guest tries to break into a debugger (INT 3). I don't have an immediate idea what to investigate further.

You are not gonna believe it.
I just went in settings and changed from Windows 2019 to 2016 and it mounted !

No explanation here

That's actually weird. I've tried the same thing by changing to Windows Server 2016, and now it is mounted.
Thank you!

For some time, the 2019 template had a bug in it, and the workaround was to set to the 2016 template and set Paravirtualization to Hyper-V.

This should not be necessary anymore, starting around Virtualbox 6.1.26-ish.

Anyone running 6.1.26 or later and still needs to set a 2019 VM to the 2016 template to get the 2019 OS to boot, please start a new topic with an attached vbox.log.