Sign up with Google
Jackal46
Expert Member
- Joined
- Feb 10, 2024
- Messages
- 1,119
- Reaction score
- 1,182
Been pulling a few depositories to compile software and let it run on a Win11 VBox but I needed to run Linux WSL inside the Win11 VBox. For this to work on a AMD I need to have Hyper-V running on the Host PC. I also need Hyper-V Management Tools, Hyper-V GUI Management Tools and Hyper-V Module for Windows PowerShell installed. Then I had to manually install Hyper-V Platform that consist of Hyper-V Hypervisor and Hyper-V Services.
At this point things will start to work BUT there is more stuff that is needed, these are actually not part of the installs above. They are called Virtual Machine Platform and Windows Hypervisor Platform. With these installed Virtual box will allow the following options in its system settings under processor. Enable PAE/NX and Enable Nested VT-x/AMD-V. Only it doesn't allow the VM to run another VM inside of it.
The Win11 Vbox is fully activated Win11 Pro. All the above steps was taken so that the OS will allow for VM services to run only it doesn't. It is fully updated and all installs was done successfully. Is Virtual Box the problem here or is it my AMD system? I know Intel 11th gen and 12th gen don't have this problem and we all know to stay away from 13th gen and up as those CPUs are essentially expensive mistakes.
To solve this problem I backed up the Win11 VBox to make space for a Ubuntu install. This will allow the instruction sets to run natively BUT now I need to relearn and or replace all the software I used on the Win11 Pro system.
Because the software is untested and not trust worthy I don't want to run it directly on my main OS. If you had this problem how did you solve it?
At this point things will start to work BUT there is more stuff that is needed, these are actually not part of the installs above. They are called Virtual Machine Platform and Windows Hypervisor Platform. With these installed Virtual box will allow the following options in its system settings under processor. Enable PAE/NX and Enable Nested VT-x/AMD-V. Only it doesn't allow the VM to run another VM inside of it.
The Win11 Vbox is fully activated Win11 Pro. All the above steps was taken so that the OS will allow for VM services to run only it doesn't. It is fully updated and all installs was done successfully. Is Virtual Box the problem here or is it my AMD system? I know Intel 11th gen and 12th gen don't have this problem and we all know to stay away from 13th gen and up as those CPUs are essentially expensive mistakes.
To solve this problem I backed up the Win11 VBox to make space for a Ubuntu install. This will allow the instruction sets to run natively BUT now I need to relearn and or replace all the software I used on the Win11 Pro system.
Because the software is untested and not trust worthy I don't want to run it directly on my main OS. If you had this problem how did you solve it?