Windows 10 running in Virtualbox on my Debian host. The VM boots up in EFI mode.
I went to full-time Linux in april 2019, and I kept this old install as a fallback VM just in case I get an urgent job for which I need some of my Windows-only programs. I have used this VM approx 5…6 times during the years, and then I always needed the DVD Architect (unfortunately that doesn’t work well in WINE).
Well, it doesn’t perform as good as on bare metal, that’s true.
But on my desktop I assigned 5 cores, 6GB RAM, still not a gaming experience, however it’s capable to run Vegas pro 16 at a speed, that basic editing without hardware acceleration is possible, Photoshop runs just as fine as on real machine, DVD Architect (ancient software - without HW accel. initially) performs very similar as on the real machine. So I can do with it basically anything I could on real machine. Of course video editing is much less comfortable, becasue of missing horsepower. On the other hand, a real Windows would take up at least 64GB partition, plus data partitions. My VM is narrowed to approx 32GB virtual disk, all data goes to VBox shared folders, Windows in the VM is totally sandboxed, no updates, no network, the only connection to the outside is via the shared folders. It’s just a safety reserve conserved for the uncertain future, in case I need to do something with an old project, which was prepared before ditching Windows.
The issue of the official Gentoo Users Guide being very dated (eg it advocates fdisk and gdisk for partitioning) needs to be addressed. When you combine this with the amazing statement
" If you deviate from our instructions one iota, we will not offer assistance"
it becomes very unfriendly indeed.
It does not need to be like that. Gentoo is a good product with poor PR.
I have never used fdisk or gdisk for partitioning. If I am installing to HDD or SDD I will use gparted to partition the drive and use lsblk and Gentoo to make mout points and mount the partitions. If I install to VirtualBox I just use cfdisk.