this post was submitted on 21 Oct 2024
199 points (98.5% liked)
Linux
48306 readers
640 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm a fan of dual booting AND using a passthrough VM. It's easiest to set up if your machine has two NVMe slots and you put each OS on its own drive. This way you can pass the Windows NVMe through to the VM directly.
The advantage of this configuration is that you get the convenience of not needing to reboot to run some Windows specific software, but if you need to run software that doesn't play nice with virtualization (maybe a program has too large a performance hit with virtualization, or software you want to run doesn't support virtualized systems, like some anticheat-enabled games), you can always reboot to your same Windows installation directly.
I can see that. I nuked my Windows partition years ago, though. Honestly, if I find a software is jerk enough to block virtualization, I don't find it worth using.
Fair enough! I think it's more common for games to do that, but sometimes I had trouble with software on Windows that used virtualization elements themself. I probably just didn't properly configure HyperV settings, but I know nested virtualization can be tricky.
For me it's also because I'm on a laptop, and my Windows VM relies on me passing through an external GPU over TB3 but my laptops' dedicated GPU has no connection to a display, so it would be tricky to try and do GPU passthrough on the VM if I were on the go. I like being able to boot Windows on the go to edit photos in Lightroom, for example, but otherwise I'd prefer to run the Linux host and use the Windows VM only as needed.
Yeh, I think it has to do with some CPU topology crap. I have it working pretty well, luckily - I once had an old Virtualbox VM with MacOS that I needed, and I was able to boot it in my Windows VM.
With Lightroom, you're right on that. Honestly, the state of FOSS image editors is a bit ridiculous, especially considering how good FOSS vector editors like Inkscape are these days compared to their commercial, proprietary counterparts.
Yeah there's a good chance you're right. Maybe something to do with memory management as well.
Long term I'll probably end up switching back to Darktable. I used it before and honestly it is quite good, but I currently have a free license for CC from my university and the AI denoise features in LR are pretty nice compared to the classical profiled denoise from Darktable. It does also help that the drivers for my SD card reader are less finicky on Windows so it's easier for me to quickly copy over images from my camera on there instead of Linux. Hopefully that also gets better over time!
Interesting, I’ve never heard of softwares that don’t support virtualized systems, I mean how would they… know?
I don't know exactly, but it's apparently a thing. Some game anti-cheat software such as Easy Anti-Cheat will give you an error message saying something along the lines of "Virtual machines are not supported." Some are easy to bypass by just tweaking your VM config, others not so much.
In some cases they look for generic virtual hw devices, in other cases things like available cpu flags or BIOS version.
There are ways to hide it though:
https://github.com/zhaodice/qemu-anti-detection
https://forum.proxmox.com/threads/how-do-i-hide-the-fact-to-windows-that-it-runs-in-a-vm.115627/