I don’t remember the exact process but I ran Linux on computer A and windows on computer B. I installed windows onto a second drive on computer B and set Virtual box on computer A to use that drive as its boot drive over the network. I then shared the primary drive as well so I could boot computer B into either Windows install and run the other as a VM on Computer A.
I have no idea why I did this but it worked and no one was impressed.
Do attempts without Windows as the first step count e.g running Windows in QEMU on Wine on Linux?
Also, depending on which version of WSL you used, you might be breaking your own rule with WSL on VMs since WSL2 uses Hyper-V. You might also be breaking it again with QEMU.
What actually counts as "VM software"? Are you defining it as a hypervisor, or does, for instance, emulating Linux on ARM in an emulator of a RISC V system in an emulator of a PowerPC system break the rule. In addition, do you mean consecutive VM software steps, or could I for instance emulate an ARM CPU that supports hypervisors and run a VM software in there?
Did you actually get that to run or is this a fun thought exercise? It seems like a lot of nested virtualization. If you’re clever enough maybe you could get
Windows > WSL > WSL Wayland compatibility layer > Ubuntu Wayland session > LXC > Fedora > QEMU > macOS > Wine > Windows app
I really want to try it because I can't resist stupid projects, but I'm stuck on a crappy old Thinkpad for now, and it probably would die at step 1 install Windows 11 😅 So it's only theoretical for now, but I hope to try it whenever I get a new PC !
I needed to make a docker image based on Core OS (RedHat) and the docker host had to be RHEL compatible. My machine is Ubuntu. To get it to work, I installed Rocky Linux on LXC and docker inside that machine. Turns out there are a lot of security settings isolating LXC and restricting nested virtualization, but fortunately Canonical posts a 20 minute video explaining how to modify the permissions for that use case. I cannot imagine virtualizing much further without the machine refusing to comply!