CLI/GUI shouldn’t matter for Linux. The problem is that you can only nest virtualisation so far in hardware accelerated environments like SVM or VT-X.
If you run software virtualisation (Bochs, jslinux, QEMU, 32 bit VirtualBox) you can nest until you run out of resources, but the VMs will get progressively slower as you keep nesting.
I’m using the most trimmed Windows installs I can find (and manually trimming bits myself) to try and keep overhead as low as possible, but it’s still… rough. Don’t know how far I’ll actually be able to get. Once I get to XP I may just skip to 95, but we’ll see.
I got sidetracked trimming Windows services on my primary install, lol.
Enderman tried Windows 10 for each layer and failed to install the 4th.
I think you can get deeper with older Windows, or very deep if you use CLI-only Linux in each layer.
CLI/GUI shouldn’t matter for Linux. The problem is that you can only nest virtualisation so far in hardware accelerated environments like SVM or VT-X.
If you run software virtualisation (Bochs, jslinux, QEMU, 32 bit VirtualBox) you can nest until you run out of resources, but the VMs will get progressively slower as you keep nesting.
Sounds like a challenge
What resources would one have to worry about? Just RAM, or other things? My server has 156GB of RAM and I haven’t used it for anything yet.
I’m using the most trimmed Windows installs I can find (and manually trimming bits myself) to try and keep overhead as low as possible, but it’s still… rough. Don’t know how far I’ll actually be able to get. Once I get to XP I may just skip to 95, but we’ll see.
I got sidetracked trimming Windows services on my primary install, lol.
Here is an alternative Piped link(s):
failed to install the 4th
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.