#gpu passthrough + boot vm from disk

8 messages · Page 1 of 1 (latest)

tranquil hawk
#

I have a full disk with windows with most of my stuff set up pretty well. I'm now waiting on a new ssd which will be a full linux system on btrfs
I've never given arch a proper try, I want to try EOS for a pretty "clean" arch experience, basic stuff kde, use it as a daily system because dev on linux is much better than on windows.
With that said I would like to have a setup where my dedicated gpu goes to a vm that starts automagically at boot and basically runs my windows install. Ideally I can just switch os by changeing the m/kb and display output.
Is this feasible to get working with a stable environment and without crying in the corner for 5 days straight?
I'm not new to linux, I've used pretty much all the major distributions, but I can't say I'm experienced either. I can however read, which seems to be rare these days and the arch wiki seems pretty good. I am however scared of the "rolling" part of arch. Ideally I would like to find a way to lock myself like 1 major version behind in everything. Maybe kernel would be enough but 🤷

slate wasp
#

Also why do you want a windows wm?

tranquil hawk
# slate wasp Also why do you want a windows wm?

games, adobe, office(tho not so much), software that simply cannot run on linux, there's heaps. Even something as simple as samsung magician simply doesn't exist on linux, so in this case not a vm, but straight up a windows install is needed.

tranquil hawk
# slate wasp If you want to always have a stable system and be a version or two behind use so...

Fedora is quite interesting in their update philosophy, but I don't think it fits what I want.
More specifically this bit in their docs:
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#philosophy
A major version number reflects a more-or-less stable set of features and functionality. As a result, we should avoid major updates of packages within a stable release
Updates should aim to fix bugs, and not introduce features, particularly when those features would materially affect the user or developer experience

I don't want this, I want features, if a package breaks because of an update, well that's life, whatever. The thing I am worried about is the system, it shouldn't break because of an update to a package.

slate wasp
slate wasp
#

The main reason you can't play a game is anticheat and that still doesn't work in a wm