I'm trying to put windows 11 in a VM to have a look at it, and am getting this error My OS is slackware-15.0. I simply installed the a/ package set, & bootloader and rsync'ed a backup for the rest, including configuration files. The old box was Legacy boot, this is UEFI, in case it matters.

My box has a AMD Ryzen 5 5600(6 core) in an MSI Mag B550M Bazooka motherboard with an AMD RX6600 XT graphics & 16 GB ram. I trawled the web and found common causes.

1. It's not the BIOS - System Virtualisation is enabled in the BIOS cpu settings.
2. No, Hyper-V is not enabled in (the dual booting) Windows 10.
3. I tried the VM with only has one core enabled but it still pukes.
4. No, setting the VM machine type to windows 7 or windows 2003 doesn't help.

So it still pukes, which is irritating.

My installer is some developer thing. It does an initial boot and has a number of flavours of windows. But it won't do the initial boot, it throws that error immediately.

The old box (i3 with Intel chipset) does the initial boot no issue, though it hasn't the poke to run anything above windows 7 in a vm

Anyone got any ideas for what to try? I think the only other iso to hand is windows 10

https://www.cgdirector.com/svm-mode-bios/
See if you have this option.

What linux distro are you using? How did you create the VM?

Thanks for the reply and sorry for the delay. Life was busy here and I'm operating (personally) at 1/3 of the speed at best. I had that well hidden option in the BIOS and enabled it.

I'm using Slackware-15.0. I installed that by installing the 'a/' package set (basic console & get-you-going stuff) and then rsyncing a backup of my legacy box in, which got me all configs & setup. But my new box's installed kernel-5.15.19 in elilo which conflicted with the kernel-5.15.27 headers. So I have since installed kernel-5.15.27 in agreement with headers. VB-6.1.34 was installed from the .run file, and that was transferred over. After that, it was "New machine…", and I'm trying to install Windows 11 to have a look before I update the dual boot windows system. I want to have a look at it anyway. The last windows I was any way familiar with was windows '98 (complete with regular BSODs).

I tried VB with the new setup. There's no complaint about SVM or unsigned modules, but I'm dumped into a UEFI shell of some sort that makes the inscrutable busybox shell look like child's play. The modules are still unsigned, but I havge managed to import a signing key. I've mounted the iso I'm trying to boot from, and indeed tried a few others, and they certainly look UEFI capable. I installed Windows 7 from the same iso (some developer thing with all recently decent versions of windows) in the legacy box.

EDIT: The file signing process calls up 'sign-file.sh,' but the kernel/scripts dir only provides sign-file.c . My guide must be out of date.