GPU-Passthrough-Arch-Linux-to-Windows10
systemd
GPU-Passthrough-Arch-Linux-to-Windows10 | systemd | |
---|---|---|
14 | 517 | |
247 | 12,516 | |
- | 1.2% | |
0.0 | 10.0 | |
almost 3 years ago | about 10 hours ago | |
C | ||
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
GPU-Passthrough-Arch-Linux-to-Windows10
- How to get KVM, libvirtd and virt-manager working on Arch
-
Windows 11 Start menu ads look set to get even worse – this is getting painful
I'm not sure I'd describe the process as "sane", but I basically did as described in this guide[0], followed by following the setup guide for Looking Glass[1].
[0](https://github.com/vanities/GPU-Passthrough-Arch-Linux-to-Wi...)
-
Freezing During Windows Installation in QEMU/KVM
I followed this and this guides, and managed to isolate the card. Sadly, every single time i try to install the OS, the system freezes, and is said to be paused by virt manager. I cannot unfreeze it, and i don't know how to troubleshoot it. I also tried to do a normal installation (without passthrough), and it still froze
- Good vm for windows games with a linux host
-
Single GPU passthrough to VM
This is for Arch. But should be doable on any distro.
-
Single GPU Passthrough on laptop on Pop-Os 22.04?
Here is the guide for Arch Linux just in case if you want to disregard the advice above. The differences amount to a different package manager and a different initramfs generator (so, steps 2 and 3 of that guide become different, and apt should be used instead of pacman). For PopOS, you will need to edit the /etc/initramfs-tools/modules file (and just list the needed modules) and run update-initramfs -u -k all.
- doe's anybody know any good guides for a gpu passthrough vm for manjaro? The ones i've been using haven't worked for me. idk if this matters for it but my gpu is a evga 1660ti
-
Nvidia Discrete GPU Passthrough
Hi, My main focus is to use "moonlight host" in the win10 VM, I have an Nvidia 880M (discrete GPU) and the host GPU is a cheap Intel graphic card. I've used this beautiful guide: https://github.com/vanities/GPU-Passthrough-Arch-Linux-to-Windows10 to configure VFIO and libvirtd.
-
Qemu drops to EFI shell when firmware is set to UEFI instead of BIOS
GitHub - vanities/GPU-Passthrough-Arch-Linux-to-Windows10: GPU Passthrough and virt-manager walkthrough
- My experience with VFIO
systemd
-
Run0 – systemd based alternative to sudo announced
> 3. even `adduser` will not allow it by default
5. useradd does allow it (as noted in a comment). 6. Local users are not the only source, there things like LDAP and AD.
7. POSIX allows it:
* https://github.com/systemd/systemd/issues/6237#issuecomment-...
-
Systemd Rolling Out "run0" As sudo Alternative
> I for one love to type out 13 extra characters
FWIW, systemd is normally pretty good at providing autocomplete suggestions, so even if you don't want to set up an alias you'll probably just have to type `--b ` to set it.
> I wonder what random ASCII escape sequences we can send.
According to the man page source[0]:
> The color specified should be an ANSI X3.64 SGR background color, i.e. strings such as `40`, `41`, …, `47`, `48;2;…`, `48;5;…`
and a link to the relevant Wikipedia page[1]. Given systemd's generally decent track record wrt defects and security issues, and the simplicity of valid colour values, I expect there's a fairly robust parameter verifier in there.
In fact, given the focus on starting the elevated command in a highly controlled environment, I'd expect the colour codes to be output to the originating terminal, not forwarded to the secure pty. That way, the only thing malformed escapes can affect is your own process, which you already have full control over anyway.
(Happy to be shown if that's a mistaken expectation though.)
[0] https://github.com/systemd/systemd/blob/main/man/run0.xml
[1] https://en.wikipedia.org/wiki/ANSI_escape_code#SGR_(Select_G...
- Crash-only software: More than meets the eye
-
Systemd Wants to Expand to Include a Sudo Replacement
bash & zsh are supported by upstream: https://github.com/systemd/systemd/tree/main/shell-completio...
-
"Run0" as a Sudo Replacement
the right person to replace sudo, not: https://github.com/systemd/systemd/issues/6237
PS: https://pwnies.com/systemd-bugs/
-
Linux fu: getting started with systemd
https://github.com/systemd/systemd/issues/32028#issuecomment...
There are some very compelling arguments made there if you care to read them
-
Ubuntu 24.04 (and Debian) removed libsystemd from SSH server dependencies
Maybe it was because you weren't pointing out anything new?
There was a pull request to stop linking libzma to systemd before the attack even took place
https://github.com/systemd/systemd/pull/31550
This was likely one of many things that pushed the attackers to work faster, and forced them into making mistakes.
-
Systemd minimizing required dependencies for libsystemd
The PR for changing compression libraries to use dlopen() was opened several weeks before the xz-utils backdoor was revealed.
https://github.com/systemd/systemd/pull/31550
- Going in circles without a real-time clock
-
The xz sshd backdoor rabbithole goes quite a bit deeper
I find this the most plausible explanation by far:
* The highly professional outfit simply did not see teknoraver's commit to remove liblzma as standard dependency of systemd build scripts coming.
* The race was on between their compromised code and that commit. They had to win it, with as large a window as possible.
* This caused serious errors.
* The performance regression is __not__ big. It's lucky Andres caught it at all. It's also not necessarily all that simple to remove it. It's not simply a bug in a loop or some such.
* The payload of the 'hack' contains fairly easy ways for the xz hackers to update the payload. They actually used it to remove a real issue where their hackery causes issues with valgrind that might lead to discovering it, and they also used it to release 5.6.1 which rewrites significant chunks; I've as yet not read, nor know of any analysis, as to why they changed so much.
Extra info for those who don't know:
https://github.com/systemd/systemd/commit/3fc72d54132151c131...
That's a commit that changes how liblzma is a dependency of systemd. Not because the author of this commit knew anything was wrong with it. But, pretty much entirely by accident (although removing deps was part of the point of that commit), almost entirely eliminates the value of all those 2 years of hard work.
And that was with the finish line in sight for the xz hackers: On 24 feb 2024, the xz hackers release liblzma 5.6.0 which is the first fully operational compromised version. __12 days later systemd merges a commit that means it won't work__.
So now the race is on. Can they get 5.6.0 integrated into stable releases of major OSes _before_ teknoraver's commit that removes liblzma's status as direct dep of systemd?
I find it plausible that they knew about teknoraver's commit _just before_ Feb 24th 2024 (when liblzma v5.6.0 was released, the first backdoored release), and rushed to release ASAP, before doing the testing you describe. Buoyed by their efforts to add ways to update the payload which they indeed used - March 8th (after teknoraver's commit was accepted) it was used to fix the valgrind issue.
So, no, I don't find this weird, and I don't think the amateurish aspects should be taken as some sort of indication that parts of the outfit were amateuristic. As long as it's plausible that the amateuristic aspects were simply due to time pressure, it sounds like a really bad idea to make assumptions in this regard.
What are some alternatives?
Single-GPU-Passthrough
openrc - The OpenRC init system
Complete-Single-GPU-Passthrough - Single GPU VFIO Passthrough Guide
tini - A tiny but valid `init` for containers
KVM-GPU-Passthrough - This is a simple, mostly automated guide to pass a GPU through to a VM.
inotify-tools - inotify-tools is a C library and a set of command-line programs providing a simple interface to inotify.
vfio
s6 - The s6 supervision suite.
LEDs-single-gpu-passthrough - Single GPU passthrough guide 单显卡直通教程资源
earlyoom - earlyoom - Early OOM Daemon for Linux
GPU-Passthrough-Arch-Linux-to-Wi
supervisor - Supervisor process control system for Unix (supervisord)