Single-GPU-Passthrough VS WSL

Link to hook scripts: https://github.com/joeknock90/Single-GPU-Passthrough

Yes but that's a different kettle of fish. You then don't need two gpus, although if you do it can be useful. Start here and see how deep the rabbit hole goes https://github.com/joeknock90/Single-GPU-Passthrough

Im assuming you're on a single gpu setup and, as such are trying to do single gpu passthrough with a single nvidia card. so you'll likely have to run some libvirt hooks or smth to run scripts to unbind your gpu once you start your vm. In which case id suggest going through these two guides 1 2 which go over completely passing through your single gpu when you start your vm

Single GPU passthrough: https://github.com/joeknock90/Single-GPU-Passthrough

Out of curiosity, who is Muta, the video dude, or the guide writer, or someone else? From the GitHub it sounded like running the commands from the guide would create a qemu.d/[VM Name]/prepare/begin/start.sh . If I were to simply create those directories myself, and then script as described in the video, I should be good?

Thanks for the info. Some of these I recognize from a single gpu passthrough project on github that i used on my main rig... https://github.com/joeknock90/Single-GPU-Passthrough

It absolutely 100% can be true.

As an example: Windows Services for Linux 2 used a special init daemon to interact with the host OS.

That meant no systemd. That meant that the `systemctl` program wasn't there.

This baffled legions, armies, of wannabe sysadmins.

https://stackoverflow.com/questions/55579342/why-systemd-is-...

https://superuser.com/questions/1785697/systemd-in-wsl-on-wi...

https://github.com/microsoft/WSL/issues/9477

https://askubuntu.com/questions/1132230/unable-to-run-any-sy...

People on the whole have no idea how this stuff works, and they just copy magic incantations from StackOverflow to get stuff to happen. If that doesn't work, then this OS is broken. The end.

For these guys, WSL was broken.

Result:

MS hired Lennart Poettering.

https://www.theregister.com/2022/07/07/lennart_poettering_re...

He "fixed" it. Systemd now works in WSL2. All those guides for noobs now work. Everyone is happy.

In a world where tools like Flatpak and Snap are proliferating and it's driving deep divisions between Linux distros, if you think the average person struggling with Linux is going to use `ldd` to work out where the dependencies for something live, I'm afraid you are a deep guru who lives on a different plane of existence.

We now have widely-used packaging systems which simply embed an apps entire dependency tree into a package to avoid people having to work out the difference between `apt` and `rpm`. Thousands of terabytes of disk are being burned to make this stuff go away.

Yes, this is too hard. Way too hard.

Better source: https://github.com/Microsoft/WSL/issues/873#issuecomment-425...

One of the bugs where on the Docker side. As I have said, there have been several since release with a lot of impact period overlap. The latest and greatest is not resolved.

It's the issue of abysmal I/O performance in communication between the mounted WSL2 virtual hard disk and Windows mounts inside the WSL2 distro.

I found this github page and I was able to reproduce this from the answer

* Docker engine and not Docker Desktop in a VM. WSL2 works well after some configuration: https://github.com/microsoft/WSL/issues/6655#issuecomment-11...

Seems to more of a Defender issue than a WSL one, see https://github.com/microsoft/WSL/issues/8995

After adding exclusions for the fsnotifier-wsl process and and both variants of the WSL distro path my disk performance was improved.

Adding the idea64.exe process also helped since I was trying to run IntelliJ against projects inside WSL.