ARCH LINUX | GPU PASSTHROUGH MANAGER EASY? | I'm having serious problems here!

I just happened to stumble upon these two videos.
Got my GPU up and running right after a new install of ArcoLinuxB - Plasma.
Went with the guide, not the first video. And two reboots later, I got it running.

  • vfio drivers unloaded

  • WARNING!

IF YOU DO NOT HAVE TWO GPU’S & TWO MONITORS
IT’S GOING TO BE A BLACK SCREEN AFTER DOING THIS!
SO GO INTO THE BIOS, SET YOUR iGPU TO PRIMARY
USE THAT ON ONE MONITOR, THEN ONE ON THE GPU
OR IF YOU HAVE MULTIPLE GPU’S, THEN JUST HAVE ONE
MONITOR PER GPU, SET ONE AS PRIMARY SOURCE IN
THE BIOS AND YOU ARE GOOD TO GO. CHEERS!

  • WARNING!

GPU PASSTHROUGH MANAGER - GITHUB
GPU PASSTHROUGH MANAGER - AUR

GUIDE IN SHORT! - GPUPM - CREATORS GUIDE (LINK)

GUIDE IN SHORT! - Install QEMU/KVM (LINK)

  • sudo pacman -Syy

  • sudo pacman -S archlinux-keyring

  • sudo pacman -S qemu

  • sudo pacman -S virt-manager virt-viewer dnsmasq vde2 bridge-utils openbsd-netcat

  • sudo pacman -S eptables iptables-nft

  • sudo pacman -S libguestfs

  • sudo systemctl enable libvirtd.service

  • sudo systemctl start libvirtd.service

UNCOMMENT LINE 85 & 108
85 » unix_sock_group = “libvirt”
108 » unix_sock_rw_perms = “0770”

  • kate /etc/libvirt/libvirtd.conf
    (or use ‘sudo vim’ or ‘sudo nano’ )

  • sudo usermod -a -G libvirt $(whoami)

  • newgroup libvirt

  • sudo systemctl restart libvirtd.service

  • REBOOT
    (Optional, but I always do.)

  • Open ‘Virtual Machine Manager’

  • Rightclick ‘QEMU/KVM’
    image

  • Click ‘Details’, then the ‘Virtual Networks’ tab. Have the Network start at boot.
    image

  • IF YOU WANT TO HAVE NESTED VIRTUALISATION
    GO TO THE LINK AT THE BEGINNING OF THIS GUIDE.

INSTALL A WINDOWS/LINUX/AMIGA VM (or whatever floats your boat)
PCIE PASS THE DEVICE OF YOUR CHOICE.
TIP! - MOUSE AND KEYBOARD PASSTHROUGH CAN BE HANDY TOO!
(I have to remake the VM, with keyboard & mouse passthrough :stuck_out_tongue_winking_eye: )

EASY? I thought so. Till I actually used my VM…

It starts, then it stops the output. I don’t know why. The VM’s own driver might fudge it up?

  • Unloaded the vfio driver.
    It’s not working as expected. Sure the GPU is seen in the VM, but it’s not displaying out to the GPU displayports. Is that just a setting in the Windows VM? ALSO! The VM seemed sluggish, it was like my mouse wasn’t accelerated when I was in the VM, but I don’t know, it can be some kind of sidelag. I don’t know what to do. To be honest.

  • MY IOMMU GROUPINGS » IOMMU

  • MY QEMU OVERVIEW - WIN10 » XML - WIN10

  • MY QEMU OVERVIEW - WIN11 » XML - WIN11

  • CPU Pinning (12 core/threads)

  • image

  • image

OH YEAH!

My iGPU does not like being used at all. I’m thinking … Maybe I should just not use it at all.
I have an Idea though. I need to change the hooks so that they use a little bit of both, because I don’t have money to buy another GPU to have in the computer. I thought it would be enough using the iGPU, and it should be, but it have the indecency to break on me…

  • This start on random for me!

  • My VM Overview XML file.

I keep getting an error message though. "/

image

Summary

Unable to complete install: ‘internal error: qemu unexpectedly closed the monitor: 2023-04-04T23:05:15.551651Z qemu-system-x86_64: Hyper-V synthetic interrupt controller (hv-synic) requires Hyper-V VP_INDEX MSR (hv-vpindex)’

Traceback (most recent call last):
File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 72, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File “/usr/share/virt-manager/virtManager/createvm.py”, line 2008, in _do_async_install
installer.start_install(guest, meter=meter)
File “/usr/share/virt-manager/virtinst/install/installer.py”, line 695, in start_install
domain = self._create_guest(
File “/usr/share/virt-manager/virtinst/install/installer.py”, line 637, in _create_guest
domain = self.conn.createXML(initial_xml or final_xml, 0)
File “/usr/lib/python3.10/site-packages/libvirt.py”, line 4481, in createXML
raise libvirtError(‘virDomainCreateXML() failed’)
libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: 2023-04-04T23:05:15.551651Z qemu-system-x86_64: Hyper-V synthetic interrupt controller (hv-synic) requires Hyper-V VP_INDEX MSR (hv-vpindex)

I’m really tired atm. I have no Idea how to fix this. "/

I did what any sane person would. I deleted the hyper v section… :stuck_out_tongue_winking_eye: Not really! I deleted some of the lines that I had added to that section.

Hyper-V

These lines to give details.

  • <synic state=“on”/
  • <stimer state=“on”/
  • <reset state=“on”/
  • <frequencies state=“on”/

Following this guide now. "/