Discuss.
>>57934044
>"I can't form my own opinions" - OP
VM allows for running both OSs concurrently, but consumes more resources.
>>57934057
How much more? in percentage
>>57934139
3.50%
>>57934255
thanks
>>57934044
VM is almost always better. Both can run at the same time.
>>57934139
Well for starters, subtract whatever RAM you've allocated to the vm. A comfy 4 gb is working nicely for me with a lunix vm.
>>57934044
Dual boot. Things just run better. I still use VMware for some things though.
>full fledge games like skyrim
dualboot
>small porn games like witch trainer
virtual machine
does vmware work much better than virtualbox for anyone else?
>>57935294
Last time I tried, VB failed to boot every time, no matter what I tried. Vmw works perfectly. A little stutter here and there.
t. T420 owner
>>57935259
(Qemu) VGAPassthrough
>>57935526
For me it was the opposite, also in a T420 but with a quad core cpu.
Virtualbox with various VMs running fine.
>>57935259
Is this related to that Aladin game?
>>57934044
>>57935259
Windows VM with GPU passed through is the best. No need to reboot and you get full performance while still using Linux.
>>57934044
Neither. Latest fast ring Winbotnet 10 Insider preview build to get the sick new features they added to WSL, then switch your WSL to a better distro than fucking Ubuntu for Windows (c) using https://github.com/RoliSoft/WSL-Distribution-Switcher
And there you go, you can even run linux GUIs on your desktop, and if you really wanted to you could also run a complete xfce environment right there on windows.
Pretty much replaced my need for VMs for most of my programming projects.
I still do use VMs for running/testing my shit in a closed & clean environment, you can't really get rid of that.
But for every day computing, if you need to use windows at all as part of your workflow/for playing games/whatever, then it's better to double down on Microjews since WSL is becoming really good really fast.
>>57934044
>VirtualBox
complete pile of trash. can safely be discarded
>>57935259
this
If it can run on a shitty emulated graphics card, I'll run it inside a VM. But most of the time, those things work via ‘wine’ just as well
>>57935808
>No need to reboot and you get full performance while still using Linux.
The only caveat is that you either need to buy a second GPU or you lose the ability to lose your GPU under Linux
For some people that's acceptable, for others it's not.
>>57935912
Do you only lose the GPU while the VM is running or is it permanent?
>>57935912
Would the igpu work in this case if you already have a separate card?
>>57935954
Afaik you need to reboot if you want to use the GPU in Linux again
>>57936002
Yes, but that way you won't be able to e.g. play Linux games, or use the GPU for other stuff like video postprocessing or hardware decoding in mpv or whatever.
>>57936062
>you need to reboot
No, just unbind from vfio and bind it to the gpu driver.
>>57934139
100% (you can't share ANY ram).
>>57936143
Do you know if it would be possible to keep my X session running, switch VT, attach my GPU to the VM instead, run the VM; then after shutting down the VM again, re-attach my GPU to the X session and have all of my programs still open?
>>57936163
Yeah but that the only overhead you're paying is the overhead of running the base system (windows). Stuff like RAM consumed by the application doesn't need to be doubled between the host and the guest system
>>57936233
Yeah, but I'm assuming that OP needs X ram to have a decent experience in any OS. That needs to be 2 * X for a vm setup.
>>57936257
>Yeah, but I'm assuming that OP needs X ram to have a decent experience in any OS. That needs to be 2 * X for a vm setup.
Well that's simply not how things work. If you're not gonna be running your application on the host OS, then the host OS doesn't need to reserve RAM for the application.
Is VirtualBox any better than Qemu+kvm ?
>>57935869
https://github.com/microsoft/bashonwindows/issues/637
Interesting but looks like shit.
>>57936578
That's pretty old and only relevant to current builds (as in, not fast ring insider builds). It was pretty hacky and not very good since WSL was missing a lot of features at the time (Including nearly all of /proc/*), which caused shitty performance.
It's much better now that WSL is getting a lot of support from M$, definitely worth upgrading to an insider build to even just check it out IMO.
They're only missing a couple things at this point (notably some /proc/net/* stuff) but they've apparently fixed what was missing from networking in an upcoming build due sometime this month (fixed ipv4 routing, which windows handles atm).
Nowadays you can even invoke windows binaries from bash and vice versa (pretty recent insider build) so you could literally use windows executables inside shell scripts if you wanted. You can also set up your IDE (running on windows) to compile your code using a compiler running on WSL, and then run/debug your build on WSL all while staying inside your IDE.
>>57936208
As far as I know, you have to end you x-session to unbind tour GPU, at least I wasn't able to do it (that's preety much the reason I've started using transmission-daemon)
I rember to have read about a guy that was able to do it without killing X with ayyymd, but nobody, not even him, understood how he managed to do it.
You can unbind and rebind preety much anything else without restarting X though