[SOLVED] Critical Error on ISO load; meditation error 1155

[AetherError]

Hello. Newb to virtualization and the forum, hope I put this in the correct place.

As title says, once ISO loads up I get the critical error, on the windows splash. Find attached my log folder zipped and a screen of the generic error window. Hope it's obvious!

vb crit error window.png (22.65 KiB) Viewed 625 times

Guessing this stuff is in the logs, but just in case......
Trying to load win server 19 evaluation ISO.
My system: AMD 1500x, 16 GB RAM; win 10 home 1903.
VM provisioned: 2 GB RAM; 50 GB fixed .vdi drive..
Enabled VSM on mobo and windows "virtual machine platform" feature.


Thanks for time and input in advance

EDIT: also, googling has suggested i mention these things: nx bit is enabled on host, i also have checked the enable pae/nx box on settings>system>processor. Tho you can see that in log
and tried making a new vm with .vhd instead of .vdi, since vhd is microsoft preferred, or whatever. no dice so far.
EDIT2: disabled "virtual machine platform" feature, i guess it's related to hyper-v? Anyway, still getting the meditation error 1155
Found this in log

00:00:01.930886 HM: HMR3Init: Attempting fall back to NEM: AMD-V is not available
00:00:01.971997 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

Not sure why amd-v not available when it's enabled... or why it's found hypervisor code with both features disabled
Updating log attachment to latest (fresh vm), tho i think it's identical stuff

[mpack]

Yes, get rid of Hyper-v. The details are in viewtopic.php?f=1&t=62339 posts #2 and later.

Otherwise, your VM specs look weak for server 2019. I would increase CPU cores to 2 (no more), and RAM to 4096MB. I'd also consider enabling 3D acceleration.

You haven't installed the extension pack on the host, so no USB2/USB3 or vRDP will be available in this VM.

[AetherError]

Yes, get rid of Hyper-v. The details are in

Edit:  posts #2 and later. Otherwise, your VM specs look weak for server 2019. I would increase CPU cores to 2 (no more), and RAM to 4096MB. I'd also consider enabling 3D acceleration. You haven't installed the extension pack on the host, so no USB2/USB3 or vRDP will be available in this VM.

Thanks very much! I unfortunately didn't notice the /bcdedit command when i scanned through that topic last night. That's what did it for me. I guess I had some lingering hyper-v stuff from when I thought having the Virtual Machine Platform feature enabled was a good idea, and unchecking that box was insufficient.

Will mark this thread solved.