this post was submitted on 19 May 2025
28 points (96.7% liked)
Gaming
3710 readers
119 users here now
The Lemmy.zip Gaming Community
For news, discussions and memes!
Community Rules
This community follows the Lemmy.zip Instance rules, with the inclusion of the following rule:
You can see Lemmy.zip's rules by going to our Code of Conduct.
What to Expect in Our Code of Conduct:
- Respectful Communication: We strive for positive, constructive dialogue and encourage all members to engage with one another in a courteous and understanding manner.
- Inclusivity: Embracing diversity is at the core of our community. We welcome members from all walks of life and expect interactions to be conducted without discrimination.
- Privacy: Your privacy is paramount. Please respect the privacy of others just as you expect yours to be treated. Personal information should never be shared without consent.
- Integrity: We believe in the integrity of speech and action. As such, honesty is expected, and deceptive practices are strictly prohibited.
- Collaboration: Whether you're here to learn, teach, or simply engage in discussion, collaboration is key. Support your fellow members and contribute positively to shared learning and growth.
If you enjoy reading legal stuff, you can check it all out at legal.lemmy.zip.
founded 2 years ago
MODERATORS
Knowing how to do VFIO and putting windows where it belongs(In a VM) has been such a liberating feeling. Never ever do i have to deal with windows issues anymore.
The only down side of VFIO is that if you have never done it before the initial setup can be a bit tricky. That said, feel free to steal my configs https://git.xaetacore.net/jeroenmathon/vfio-configs :P
I did that, and since I got a dedicated SSD drive for it, I used it for the VM as a block device. Later after a GRUB update I discovered Windows in my GRUB boot menu. Turns out GRUB detected my VM, and now I can physically boot into my VM. Which I didn't even know was possible.
So yeah, I accidentally dual boot Windows without meaning to, even though it's a VM. Except when I boot into it, then it's not, apparently.
Grub did not detect your VM, it detected a bootable operating system on the drive because you passed it through to your VM. So yeah its a nice way to be able to do both VM and Dual boot.
But i prefer using a raw disk file image on my btrfs FS because i have a sub volume for the windows 11 disk images that allows me to use btrfs filesystem snapshots with windows, so whenever i make a mistake on windows i can restore it to working state within 5 minutes.
I also prefer windows not running on bare metal, because i don't trust it or what runs on it enough for that.
Yeah, the bootable drive that contained my VM install, that's what I'm saying.
I started that way, but I had a disk with a single partition that contained a single file - the raw disk image file, and eventually decided this is silly, the filesystem on that disk is useless.
1TB NVME: RootFS 8TB 2x SSD4TB: Home partition 2TB NVME: Neural Network Models, Games requiring fast storage.
Based on that i setup my mounts in fstab so its not just vm images on there, i have 3 virtual disks for each class on there and i try to keep my VM images as small as possible so that i have more space for non VM things