#vfio — Public Fediverse posts

PSA for anyone using #QEMU #KVM for #SingleGPUPassthrough
Guides are all over the net suggesting hooks scripts invoking pci devices, unloading/loading kernel modules, and other unnecessary things. Here's my current hook script for starting the VM:

systemctl stop display-manager

That's it. And the reverse for teardown:

systemctl start display-manager

#IOMMU groups still apply, and you need to pass the correct PCI devices to your VM, but everything else is handled automatically.

Disclaimer that this is how it works currently for my AMD card. I did have a working setup with my NVIDIA card that did unload/load kernel modules, however it seems things have come a long way since I set that up.

#virtualization #libvirt #vfio

PSA for anyone using #QEMU #KVM for #SingleGPUPassthrough
Guides are all over the net suggesting hooks scripts invoking pci devices, unloading/loading kernel modules, and other unnecessary things. Here's my current hook script for starting the VM:

systemctl stop display-manager

That's it. And the reverse for teardown:

systemctl start display-manager

#IOMMU groups still apply, and you need to pass the correct PCI devices to your VM, but everything else is handled automatically.

Disclaimer that this is how it works currently for my AMD card. I did have a working setup with my NVIDIA card that did unload/load kernel modules, however it seems things have come a long way since I set that up.

#virtualization #libvirt #vfio

Through #WINE and absolute fuckery, I was able to get #SkyrimSE running with #MO2 and run my existing load order. No more messing with #VFIO and #KVM . Only thing that won't work is #ENB — for that I'm testing #CommunityShaders which so far looks good. Not quite as pretty, but far more performant.

Through #WINE and absolute fuckery, I was able to get #SkyrimSE running with #MO2 and run my existing load order. No more messing with #VFIO and #KVM . Only thing that won't work is #ENB — for that I'm testing #CommunityShaders which so far looks good. Not quite as pretty, but far more performant.

RE: https://furry.engineer/@Flaky/116059368890193901

lmao, Chris Titus Tech had an update to Looking Glass and now he can't access his Windows VM.

This is why vGPUs are important!

#VFIO #libvirt #KVM

RE: https://furry.engineer/@Flaky/116059368890193901

lmao, Chris Titus Tech had an update to Looking Glass and now he can't access his Windows VM.

This is why vGPUs are important!

#VFIO #libvirt #KVM

If anyone wants to passthrough their integrated GPU on an AMD Ryzen 7000 series, peep this. But I will say, it's actually not worth it. The reset bug is here despite the fact AMD has fixed it in Big Navi, and vendor-reset ain't gonna help. Just use an NVIDIA GPU instead, it'll be easier. Or just use VirtualBox if it's simple enough.

https://www.reddit.com/r/VFIO/comments/16mrk6j/amd_7000_seriesraphaelrdna2_igpu_passthrough/

#VFIO #AMD #Linux

If anyone wants to passthrough their integrated GPU on an AMD Ryzen 7000 series, peep this. But I will say, it's actually not worth it. The reset bug is here despite the fact AMD has fixed it in Big Navi, and vendor-reset ain't gonna help. Just use an NVIDIA GPU instead, it'll be easier. Or just use VirtualBox if it's simple enough.

https://www.reddit.com/r/VFIO/comments/16mrk6j/amd_7000_seriesraphaelrdna2_igpu_passthrough/

#VFIO #AMD #Linux

"Failure is simply the opportunity to begin again, this time more intelligently." — Henry Ford.

Introducing VxM, a hypervisor orchestration utility for Nitrux.

Concurrent, hardware-accelerated guest execution on multi-GPU workstations.

Coming to Nitrux 6.0.0

#Nitrux #VxM #VFIO

"Failure is simply the opportunity to begin again, this time more intelligently." — Henry Ford.

Introducing VxM, a hypervisor orchestration utility for Nitrux.

Concurrent, hardware-accelerated guest execution on multi-GPU workstations.

Coming to Nitrux 6.0.0

#Nitrux #VxM #VFIO

"Failure is simply the opportunity to begin again, this time more intelligently." — Henry Ford.

Introducing VxM, a hypervisor orchestration utility for Nitrux.

Concurrent, hardware-accelerated guest execution on multi-GPU workstations.

Coming to Nitrux 6.0.0

#Nitrux #VxM #VFIO

Hi, I'm Sparrow. I run KstrlWorks where we build high-performance, privacy-first tools for Linux users.

Built systems for F-35s and high-frequency trading desks. Now an executive that companies with deep pockets parachute into their disasters to fix operations and actually grow them.

Currently shipping:
HardPass - GPU passthrough and #VFIO that actually works. For #LinuxGaming and power users.

I write about:
- Real #EngineeringLeadership. The kind that prevents incidents, not LinkedIn motivational posters.
- Running efficient, security-first teams that don't implode
- #Virtualization, systems architecture, and #Bootstrapping
- Building infrastructure so solid you never need to hire a fixer like me

High-performance, privacy-first tools built with the same standards I use for critical systems. Linux users deserve that.

Let's build things that work. 🐧

#Linux #SelfHosted #TechLeadership #Privacy #Introduction #FOSS #VFIO

Hi, I'm Sparrow. I run KstrlWorks where we build high-performance, privacy-first tools for Linux users.

Built systems for F-35s and high-frequency trading desks. Now an executive that companies with deep pockets parachute into their disasters to fix operations and actually grow them.

Currently shipping:
HardPass - GPU passthrough and #VFIO that actually works. For #LinuxGaming and power users.

I write about:
- Real #EngineeringLeadership. The kind that prevents incidents, not LinkedIn motivational posters.
- Running efficient, security-first teams that don't implode
- #Virtualization, systems architecture, and #Bootstrapping
- Building infrastructure so solid you never need to hire a fixer like me

High-performance, privacy-first tools built with the same standards I use for critical systems. Linux users deserve that.

Let's build things that work. 🐧

#Linux #SelfHosted #TechLeadership #Privacy #Introduction #FOSS #VFIO

Hi, I'm Sparrow. I run KstrlWorks where we build high-performance, privacy-first tools for Linux users.

Built systems for F-35s and high-frequency trading desks. Now an executive that companies with deep pockets parachute into their disasters to fix operations and actually grow them.

Currently shipping:
HardPass - GPU passthrough and #VFIO that actually works. For #LinuxGaming and power users.

I write about:
- Real #EngineeringLeadership. The kind that prevents incidents, not LinkedIn motivational posters.
- Running efficient, security-first teams that don't implode
- #Virtualization, systems architecture, and #Bootstrapping
- Building infrastructure so solid you never need to hire a fixer like me

High-performance, privacy-first tools built with the same standards I use for critical systems. Linux users deserve that.

Let's build things that work. 🐧

#Linux #SelfHosted #TechLeadership #Privacy #Introduction #FOSS #VFIO

Hi, I'm Sparrow. I run KstrlWorks where we build high-performance, privacy-first tools for Linux users.

Built systems for F-35s and high-frequency trading desks. Now an executive that companies with deep pockets parachute into their disasters to fix operations and actually grow them.

Currently shipping:
HardPass - GPU passthrough and #VFIO that actually works. For #LinuxGaming and power users.

I write about:
- Real #EngineeringLeadership. The kind that prevents incidents, not LinkedIn motivational posters.
- Running efficient, security-first teams that don't implode
- #Virtualization, systems architecture, and #Bootstrapping
- Building infrastructure so solid you never need to hire a fixer like me

High-performance, privacy-first tools built with the same standards I use for critical systems. Linux users deserve that.

Let's build things that work. 🐧

#Linux #SelfHosted #TechLeadership #Privacy #Introduction #FOSS #VFIO

Hi, I'm Sparrow. I run KstrlWorks where we build high-performance, privacy-first tools for Linux users.

Built systems for F-35s and high-frequency trading desks. Now an executive that companies with deep pockets parachute into their disasters to fix operations and actually grow them.

Currently shipping:
HardPass - GPU passthrough and #VFIO that actually works. For #LinuxGaming and power users.

I write about:
- Real #EngineeringLeadership. The kind that prevents incidents, not LinkedIn motivational posters.
- Running efficient, security-first teams that don't implode
- #Virtualization, systems architecture, and #Bootstrapping
- Building infrastructure so solid you never need to hire a fixer like me

High-performance, privacy-first tools built with the same standards I use for critical systems. Linux users deserve that.

Let's build things that work. 🐧

#Linux #SelfHosted #TechLeadership #Privacy #Introduction #FOSS #VFIO

RTX 5090 + llama.cpp bị treo sau 2-3 lần chạy mô hình (cấu hình VFIO, Ubuntu 24.04). Lỗi "illegal memory access", GPU lỗi, quạt quay 100%. Đã thử nhiều cách nhưng chưa khắc phục. Hỏi: lỗi từ Blackwell, driver, hay nên dùng Windows VM? #llamaCPP #RTX5090 #GPU #MLOps #VFIO #CUDA #Linux #LỗiGPU #AIModel #Ubuntu

https://www.reddit.com/r/LocalLLaMA/comments/1pxv14g/help_rtx_5090_llamacpp_crashes_after_23/

WHY IS IT SO HARD TO DUMP A VBIOS

#server #gpu #vfio #proxmox

So my HP Prolaint ML350 Gen 9 has a intigrated matrox gpu in the motherboard but apparently still would rather piggyback of whatever gpu is installed by shadowing its vbios so now i have isssues with my intel arc a310. Good job HP

#HPE #server #vfio #intel #intelarc #a310 #HP #proxmox

One Open-source Project Daily

Tutorial on how to setup GPU Passthrough with KVM on Linux

https://github.com/bryansteiner/gpu-passthrough-tutorial

#1ospd #opensource #vfio #linux #gpu #windows

One Open-source Project Daily

Tutorial on how to setup GPU Passthrough with KVM on Linux

https://github.com/bryansteiner/gpu-passthrough-tutorial

#1ospd #opensource #vfio #linux #gpu #windows

One Open-source Project Daily

Tutorial on how to setup GPU Passthrough with KVM on Linux

https://github.com/bryansteiner/gpu-passthrough-tutorial

#1ospd #opensource #vfio #linux #gpu #windows

One Open-source Project Daily

Tutorial on how to setup GPU Passthrough with KVM on Linux

https://github.com/bryansteiner/gpu-passthrough-tutorial

#1ospd #opensource #vfio #linux #gpu #windows

One Open-source Project Daily

Tutorial on how to setup GPU Passthrough with KVM on Linux

https://github.com/bryansteiner/gpu-passthrough-tutorial

#1ospd #opensource #vfio #linux #gpu #windows

Just realised I haven’t touched the VFIO with looking glass setup that I spent days to get it work for months… damn

#linux #vfio #lookingglass

Just realised I haven’t touched the VFIO with looking glass setup that I spent days to get it work for months… damn

#linux #vfio #lookingglass

Just realised I haven’t touched the VFIO with looking glass setup that I spent days to get it work for months… damn

#linux #vfio #lookingglass

Just realised I haven’t touched the VFIO with looking glass setup that I spent days to get it work for months… damn

#linux #vfio #lookingglass

Just realised I haven’t touched the VFIO with looking glass setup that I spent days to get it work for months… damn

#linux #vfio #lookingglass

yesterday, i booted into the VFIO specialization for the first time since i reinstalled NixOS. i opened OBS and, as i kinda expected, it didn't work; i couldn't record the screen or capture windows. today, i booted into normal NixOS, where the GPU isn't restricted to virtual machines. and uh. yeah. OBS stopped working again

so i have a theory:

somehow, the NixOS specialization for VFIO is interfering in some way with files or configs or bindings or whatever, that are persistent, even after i turn off my laptop and boot into normal NixOS. this is the only logical explanation i can come up with. i'm using the exact same config i was using before reinstalling, when it was broken, and it was working, and then it stopped working

TLDR there's something that persists after the first boot into VFIO mode, that's preventing things from working normally in some way

#NixOS #linux #VFIO #OBS help me. i do not know what to do. here's my NixOS virtualization config file ​:boosts_ok_gay:​

RE: https://plasmatrap.com/notes/aar5ckbegw

yesterday, i booted into the VFIO specialization for the first time since i reinstalled NixOS. i opened OBS and, as i kinda expected, it didn't work; i couldn't record the screen or capture windows. today, i booted into normal NixOS, where the GPU isn't restricted to virtual machines. and uh. yeah. OBS stopped working again

so i have a theory:

somehow, the NixOS specialization for VFIO is interfering in some way with files or configs or bindings or whatever, that are persistent, even after i turn off my laptop and boot into normal NixOS. this is the only logical explanation i can come up with. i'm using the exact same config i was using before reinstalling, when it was broken, and it was working, and then it stopped working

TLDR there's something that persists after the first boot into VFIO mode, that's preventing things from working normally in some way

#NixOS #linux #VFIO #OBS help me. i do not know what to do. here's my NixOS virtualization config file ​:boosts_ok_gay:​

RE: https://plasmatrap.com/notes/aar5ckbegw

yesterday, i booted into the VFIO specialization for the first time since i reinstalled NixOS. i opened OBS and, as i kinda expected, it didn't work; i couldn't record the screen or capture windows. today, i booted into normal NixOS, where the GPU isn't restricted to virtual machines. and uh. yeah. OBS stopped working again

so i have a theory:

somehow, the NixOS specialization for VFIO is interfering in some way with files or configs or bindings or whatever, that are persistent, even after i turn off my laptop and boot into normal NixOS. this is the only logical explanation i can come up with. i'm using the exact same config i was using before reinstalling, when it was broken, and it was working, and then it stopped working

TLDR there's something that persists after the first boot into VFIO mode, that's preventing things from working normally in some way

#NixOS #linux #VFIO #OBS help me. i do not know what to do. here's my NixOS virtualization config file ​:boosts_ok_gay:​

RE: https://plasmatrap.com/notes/aar5ckbegw

yesterday, i booted into the VFIO specialization for the first time since i reinstalled NixOS. i opened OBS and, as i kinda expected, it didn't work; i couldn't record the screen or capture windows. today, i booted into normal NixOS, where the GPU isn't restricted to virtual machines. and uh. yeah. OBS stopped working again

so i have a theory:

somehow, the NixOS specialization for VFIO is interfering in some way with files or configs or bindings or whatever, that are persistent, even after i turn off my laptop and boot into normal NixOS. this is the only logical explanation i can come up with. i'm using the exact same config i was using before reinstalling, when it was broken, and it was working, and then it stopped working

TLDR there's something that persists after the first boot into VFIO mode, that's preventing things from working normally in some way

#NixOS #linux #VFIO #OBS help me. i do not know what to do. here's my NixOS virtualization config file ​:boosts_ok_gay:​

RE: https://plasmatrap.com/notes/aar5ckbegw

Мой идеальный компьютер

Я сижу под Linux, но иногда нужна винда. До недавнего времени у меня был обычный dual boot, но сейчас я реализовал свой идеальный сетап: - основная система - Linux - Windows - на выделенной SSD - на нее можно загрузиться как из груба, так и из виртуалки - с пробросом второго GPU (дисплей на отдельный физический выход) - с качественным удаленным подключением (как RDP, но быстрое) - можно играть в игры Ниже опишу что и как сделал.

https://habr.com/ru/articles/921160/

#linux #virtualization #virtmanager #gpu #nvidia #vfio #nvme #pci_passthrough

Мой идеальный компьютер

Я сижу под Linux, но иногда нужна винда. До недавнего времени у меня был обычный dual boot, но сейчас я реализовал свой идеальный сетап: - основная система - Linux - Windows - на выделенной SSD - на нее можно загрузиться как из груба, так и из виртуалки - с пробросом второго GPU (дисплей на отдельный физический выход) - с качественным удаленным подключением (как RDP, но быстрое) - можно играть в игры Ниже опишу что и как сделал.

https://habr.com/ru/articles/921160/

#linux #virtualization #virtmanager #gpu #nvidia #vfio #nvme #pci_passthrough

Мой идеальный компьютер

Я сижу под Linux, но иногда нужна винда. До недавнего времени у меня был обычный dual boot, но сейчас я реализовал свой идеальный сетап: - основная система - Linux - Windows - на выделенной SSD - на нее можно загрузиться как из груба, так и из виртуалки - с пробросом второго GPU (дисплей на отдельный физический выход) - с качественным удаленным подключением (как RDP, но быстрое) - можно играть в игры Ниже опишу что и как сделал.

https://habr.com/ru/articles/921160/

#linux #virtualization #virtmanager #gpu #nvidia #vfio #nvme #pci_passthrough

Мой идеальный компьютер

Я сижу под Linux, но иногда нужна винда. До недавнего времени у меня был обычный dual boot, но сейчас я реализовал свой идеальный сетап: - основная система - Linux - Windows - на выделенной SSD - на нее можно загрузиться как из груба, так и из виртуалки - с пробросом второго GPU (дисплей на отдельный физический выход) - с качественным удаленным подключением (как RDP, но быстрое) - можно играть в игры Ниже опишу что и как сделал.

https://habr.com/ru/articles/921160/

#linux #virtualization #virtmanager #gpu #nvidia #vfio #nvme #pci_passthrough

Sometimes I feel really stupid that I just went to set the screen to 4k for my Windows virtual machine while the GPU I passed through is 2060 Super...

#vfio

Sometimes I feel really stupid that I just went to set the screen to 4k for my Windows virtual machine while the GPU I passed through is 2060 Super...

#vfio

Sometimes I feel really stupid that I just went to set the screen to 4k for my Windows virtual machine while the GPU I passed through is 2060 Super...

#vfio

Sometimes I feel really stupid that I just went to set the screen to 4k for my Windows virtual machine while the GPU I passed through is 2060 Super...

#vfio

Sometimes I feel really stupid that I just went to set the screen to 4k for my Windows virtual machine while the GPU I passed through is 2060 Super...

#vfio

yk what i'll just tell you what's wrong

even when i select the "no passthrough please" option, when the systemd output is on screen it ocasionally says something along the lines of "the gpu is already bound to vfio" which leads me to believe that the boot option is not working bc it's not letting the host use what i'm passing through to it. oddly enough i can't use virt-manager when i'm not in passthrough mode

yea i need help pls help me ​:BlobCat_BigSob:​ #nixos #nix #vfio #virtualmachine #virtualmachines my current virtualisation config is at github.com/JuxGD/nixconfig/blob/94d149a7d81fbd48735a091a7d0fa470318d79a6/virtualisation.nix

(edit: I FIXED IT it's all good go check the latest version of the file :3 the structure was totally off but it's fine now)

yk what i'll just tell you what's wrong

even when i select the "no passthrough please" option, when the systemd output is on screen it ocasionally says something along the lines of "the gpu is already bound to vfio" which leads me to believe that the boot option is not working bc it's not letting the host use what i'm passing through to it. oddly enough i can't use virt-manager when i'm not in passthrough mode

yea i need help pls help me ​:BlobCat_BigSob:​ #nixos #nix #vfio #virtualmachine #virtualmachines my current virtualisation config is at github.com/JuxGD/nixconfig/blob/94d149a7d81fbd48735a091a7d0fa470318d79a6/virtualisation.nix

(edit: I FIXED IT it's all good go check the latest version of the file :3 the structure was totally off but it's fine now)

yk what i'll just tell you what's wrong

even when i select the "no passthrough please" option, when the systemd output is on screen it ocasionally says something along the lines of "the gpu is already bound to vfio" which leads me to believe that the boot option is not working bc it's not letting the host use what i'm passing through to it. oddly enough i can't use virt-manager when i'm not in passthrough mode

yea i need help pls help me ​:BlobCat_BigSob:​ #nixos #nix #vfio #virtualmachine #virtualmachines my current virtualisation config is at github.com/JuxGD/nixconfig/blob/94d149a7d81fbd48735a091a7d0fa470318d79a6/virtualisation.nix

(edit: I FIXED IT it's all good go check the latest version of the file :3 the structure was totally off but it's fine now)

yk what i'll just tell you what's wrong

even when i select the "no passthrough please" option, when the systemd output is on screen it ocasionally says something along the lines of "the gpu is already bound to vfio" which leads me to believe that the boot option is not working bc it's not letting the host use what i'm passing through to it. oddly enough i can't use virt-manager when i'm not in passthrough mode

yea i need help pls help me ​:BlobCat_BigSob:​ #nixos #nix #vfio #virtualmachine #virtualmachines my current virtualisation config is at github.com/JuxGD/nixconfig/blob/94d149a7d81fbd48735a091a7d0fa470318d79a6/virtualisation.nix

(edit: I FIXED IT it's all good go check the latest version of the file :3 the structure was totally off but it's fine now)

yk what i'll just tell you what's wrong

even when i select the "no passthrough please" option, when the systemd output is on screen it ocasionally says something along the lines of "the gpu is already bound to vfio" which leads me to believe that the boot option is not working bc it's not letting the host use what i'm passing through to it. oddly enough i can't use virt-manager when i'm not in passthrough mode

yea i need help pls help me ​:BlobCat_BigSob:​ #nixos #nix #vfio #virtualmachine #virtualmachines my current virtualisation config is at github.com/JuxGD/nixconfig/blob/94d149a7d81fbd48735a091a7d0fa470318d79a6/virtualisation.nix

(edit: I FIXED IT it's all good go check the latest version of the file :3 the structure was totally off but it's fine now)

when you accidentally started krfb that the libvirt vm spice server moved to port 5901 automatically and then I am there trying to figure out why looking glass keeps crashing ​:neocat_googly_woozy_shocked_explode:​

#linux #libvert #qemu #krfb #lookingglass #vfio

when you accidentally started krfb that the libvirt vm spice server moved to port 5901 automatically and then I am there trying to figure out why looking glass keeps crashing ​:neocat_googly_woozy_shocked_explode:​

#linux #libvert #qemu #krfb #lookingglass #vfio

when you accidentally started krfb that the libvirt vm spice server moved to port 5901 automatically and then I am there trying to figure out why looking glass keeps crashing ​:neocat_googly_woozy_shocked_explode:​

#linux #libvert #qemu #krfb #lookingglass #vfio