Half of the SWEs I work with don’t game.
Half of the SWEs I work with don’t game.
* Can run two OS at one time, each with half the resources * Can run one with full resources if needed * Can have multiple linux and windows installs * Can have snapshots of installs * Takes around 5-10 seconds to swap one of the running installs for a different install * Can run headless VMs on a core or two while doing all the above, ie a test runner or similar service if needed
I use a 49" ultrawide with PBP, have one GPU connected to each side, so the booted installs automatically appear side to side, and Synergy to make mouse movement seamless, etc, etc
It took a little work to set up, but I've worked this way for ~ 3 years now and never had to think about the setup after the initial time investment, and during upgrades. Highly recommend it.
I definitely can see the advantage for a small team for having a single large machine with multiple GPUs, and letting them sit at a thin workspace and "Check out" whatever install they want to use, how much CPU power and RAM they need, etc, clone and duplicate installs and get a copy with their personal files in home, ready to go, and can check out larger slices of the machine when they have more CPU/GPU intensive tasks, that's probably my ideal office machine, after using my solo workstation for a while
The only real hurdle hardware wise is your IOMMU groups and your CPU compatibility, if you have a moderately modern system it should be a problem.
I also have a couple of inexpensive PCIe USB cards that I pass through to the guests for direct USB access, highly recommended.
The guides will use qcow2 images or pass through a block device, as I mentioned I have a giant LVM pool, I just create lvs for each vm and pass the volume through to the vm as a disk , and let the vm handle it. In the host you can use kpartx to bind and mount the partitions if you ever need to open them up.
[1] https://wiki.archlinux.org/index.php/PCI_passthrough_via_OVM...
This is like the Arch Linux of computer hardware. You don't install Arch Linux to get shit done. You do it because you like building and configuring, and to learn about Linux.
I'm on Mac at the moment and frequently pine for Arch. 'What on Earth just happened...', 'What did that...', 'What is this...', 'Well that wouldn't have happened on Arch.'
People claim Mac 'just works' because of out-of-the-box readiness, well I'd say in contrast Arch 'still works' or 'keeps working': it does what you tell it and if you don't tell it to change, it stays working in the same way.
I just wish I could pay a company that would have engineers and designers building an actual user-friendly, stable OS on top of Linux. Mac OS, with all its faults, is still miles ahead in terms of usability and polish.
Not if you "borrowed them from work for testing"...