Page 1 of 1
native API even though SVM is enabled in BIOS
Posted: 3. Apr 2022, 13:55
by warp
Hi!,
please, I need some help on this, as I cannot find any clue.
I have just installed vbox in my laptop, created a new vm and it seems that it does not recognize AMD SVM, so the guest is running in native API mode (log says "SVM - AMD Secure Virtual Machine extensions = 0 (0)", any suggestions?.
I attach the log and some screenshots.
Thanks in advance.
Virtualbox 6.1.32 with latest extension pack installed.
HP Elitebook 845 G8, AMD Ryzen 5 PRO 5650U, Windows 11 host
SVM is enabled in BIOS (it is grayed out however)
Re: native API even though SVM is enabled in BIOS
Posted: 3. Apr 2022, 14:34
by scottgus1
The log definitely shows Hyper-V still enabled. Try looking over
HMR3Init: Attempting fall back to NEM (Hyper-V is active).
One other thing:
00:00:06.087613 Guest OS type: 'Linux26_64'
That's a pretty early Linux setting, if I understand it correctly. Many Linux flavors have their own VM templates, which may provide better performance. Also, Virtualbox and Hyper-V have been playing together more nicely in some circumstances, so your VM may not need Hyper-V turned off.
Re: native API even though SVM is enabled in BIOS
Posted: 3. Apr 2022, 18:45
by warp
Well, that's a clue, I will check why it is enabled, as the option in windows features is not checked manually.
scottgus1 wrote:One other thing:
00:00:06.087613 Guest OS type: 'Linux26_64'
That's a pretty early Linux setting, if I understand it correctly. Many Linux flavors have their own VM templates, which may provide better performance. Also, Virtualbox and Hyper-V have been playing together more nicely in some circumstances, so your VM may not need Hyper-V turned off.
Thanks, it was just for testing, it even has no disk. I tried first to import a Win11 and an Ubuntu srv guest images from my desktop with the same result, so I tried a clean one just to see if the turtle appears at the bottom vbox icon bar.
Re: native API even though SVM is enabled in BIOS
Posted: 3. Apr 2022, 19:20
by scottgus1
warp wrote:the option in windows features is not checked manually.
You'll find that the tutorial mentions the unreliability of the Windows Features box in determining Hyper-V activation.
Re: native API even though SVM is enabled in BIOS
Posted: 4. Apr 2022, 00:32
by warp
Solved!
scottgus1 wrote:
You'll find that the tutorial mentions the unreliability of the Windows Features box in determining Hyper-V activation.
Indeed.
I read your other post:
I also follow that other thread, 2nd post, point 3 was the culprit, i.e.,
Windows Security > Core Isolation > Firmware Protection was the only option enabled there. I just disabled it.
Thank you very much for your help.