Virtualize in a virtualized (Win2019 RDS) session

[OlivierMuet]

Hello,

Is it possible to use a Virtualbox VM in a Windows 2019 RDS session ?

Unfortunately it seems no :

Failed to load API DLL: WinHvPlatform.dll: VERR_MODULE_NOT_FOUND; vid.dll: VERR_MODULE_NOT_FOUND (VERR_NEM_INIT_FAILED).
VT-x is not available (VERR_VMX_NO_VMX).
Code d'erreur :
E_FAIL (0x80004005)
Composant :
ConsoleWrap
Interface :
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

In configurations tabs, I tried to uncheck harware virtualization, but ok button keeps on being disabled.
I haven't found no other topic even if I think I'm not alone with having this problem...

[BillG]

I doubt it. I would not even think of trying!

An RDS client is a thin client, not windows 10. You can run it on a smartphone. Would you try to install VirtualBox in that?

[OlivierMuet]

Hello Bill,

I did ! Installation runs fine, it also seems to be able to create new VMs (only x86 systems) but it never can run any of mine.
I always get this error message and I never can update configuration file.

It's right that it's a thin client, but client only prints screen. The server does all the work.
Maybe I should disable hardware virtualization functionnalities in the rds vm ?

[BillG]

Why would you do that? VirtualBox 6.1 requires it. Your problem is probably that you do not have it in the thin client.

[scottgus1]

I tried to uncheck harware virtualization, but ok button keeps on being disabled.

That check box is for 'nested' hardware virtualization, for passing VT-x/AMD-V/SVM into Virtualbox's VM so another layer of Virtualbox installed in the VM can run another VM. It is not for fixing "VT-x is not available (VERR_VMX_NO_VMX)", which is a host hardware problem.

Your 2019 RDS session is not presenting VT-x/AMD-V/SVM to the first layer of Virtualbox. VT-x/AMD-V/SVM is off in the 2019 server computer's BIOS, or VT-x/AMD-V/SVM is in use by 2019's Hyper-V, which is far more likely. This is the same problem many 10 users face.

If you have control over the physical server, try checking if VT-x/AMD-V/SVM is enabled and if Hyper-V can be disabled: I have a 64bit host, but can't install 64bit guests

If you don't have control of the server, the best you might try is to run 6.0.x, which still has no-virtualization-tech code, but can only run 32-bit one-processor VMs Windows 8.0 and earlier, probably similar limitations in Linux.

[OlivierMuet]

Thanks a lot for so many informations.

I now can understand what kind of problem I face.

On my physical server, virtualization is on in the bios, and Hyper-V is already disabled !
I attached the screen capture of Hyper-V "uninstalled".

Maybe nested virtualization cannot be used by 2019 or my processors ?

[scottgus1]

There's lots of other things that can use Hyper-V besides 'Hyper-V'. Did you read the linked tutorial? Posts 2 and 3.

Snice you have physical control over the server, did you try the admin-level bcdedit command followed by shutdown -s -t 0 and power plug pull?