Recent content by xvegax

  1. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    It seems to have worked. I can see the device in the guest now: sudo lspci -v 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Caicos PRO [Radeon HD 7450] Physical...
  2. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    Thank you for the information. Unfortunately, something is still wrong there. When I chose "install" (not graphical install) in the Proxmox VNC, this happened: I changed the Display to default and removed the serial0: socket and then I got this: Is this the right way or do we need the...
  3. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    Yeah, as mentioned in the beginning, I just need the R5 230 passthrough, so other progammes can see/use the GPU (driver), but it is not used to really give output to a monitor. One question though, does the GPU passthrough always work only for one instance/VM?
  4. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    I can try to use a different image, but I cannot verify anything with a physical monitor. My host/server is around 50 km away in a data centre. :) So, I guess, I have to do a fresh installation of the Debian image without graphical (as it was before)?
  5. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    Alright, this is the rom file size: ~$ ls -lah /usr/share/kvm/ total 16M drwxr-xr-x 5 root root 62 Nov 28 01:28 . drwxr-xr-x 113 root root 113 Sep 28 18:12 .. -rw-r--r-- 1 root root 64K Nov 28 01:18 vgabios-asus-r5-230.rom I changed back the hostpci0 to hostpci0...
  6. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    Alright, this is it where it is now: vega@rakete:/$ sudo journalctl -f -- Logs begin at Sat 2021-11-27 18:23:33 CET. -- Nov 28 01:33:51 rakete pvedaemon[7923]: start VM 103: UPID:rakete:00001EF3:00276797:61A2CE6F:qmstart:103:root@pam: Nov 28 01:33:51 rakete pvedaemon[3190]: <root@pam> starting...
  7. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    Yes, the server has only this one GPU, unfortunately. Also, yes, the vfio-pci 0000:09:00.0: No more image in the PCI ROM message came again, even when starting with OMFV BIOS and IDE2 (DVD-ROM/Image) chosen as first startup device.
  8. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    ~$ sudo journalctl -f -- Logs begin at Sat 2021-11-27 16:59:16 CET. -- Nov 27 18:10:20 rakete pvedaemon[17845]: start VM 103: UPID:rakete:000045B5:000683CA:61A2667C:qmstart:103:root@pam: Nov 27 18:10:20 rakete pvedaemon[3056]: <root@pam> starting task...
  9. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    ~$ sudo cat /proc/cmdline BOOT_IMAGE=/ROOT/pve-1@/boot/vmlinuz-5.4.140-1-pve root=ZFS=rpool/ROOT/pve-1 ro root=ZFS=rpool/ROOT/pve-1 boot=zfs quiet iommu=pt amd_iommu=on video=vesafb:off video=efifb:off It seems, the parameters were applied. ~$ sudo efibootmgr -v EFI variables are not supported...
  10. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    Okay, changes on host are active now, too: ~$ sudo cat /etc/default/grub GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="Proxmox Virtual Environment" GRUB_CMDLINE_LINUX_DEFAULT="quiet iommu=pt amd_iommu=on video=vesafb:off video=efifb:off" GRUB_CMDLINE_LINUX="root=ZFS=rpool/ROOT/pve-1 boot=zfs"...
  11. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    Alright, I removed the hostpci0 entry on the guest in the Proxmox webgui and then I was able to reboot the VM and reach it again. I changed this: ~$ sudo vi /etc/default/grub GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`...
  12. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    Oh, thank you, I understand. So, I added what you mentioned, but somehow I cannot reach the guest remotely (using SSH) anymore. This is weird. It looks, as if the VM is not booting properly. These are the settings from within Proxmox webgui: The Proxmox webgui console shows this:
  13. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    Okay, I changed vfio.conf back to disable_vga=1 and restarted the host. ~$ sudo cat /etc/modprobe.d/vfio.conf options vfio-pci ids=1002:677b,1002:aa98 disable_vga=1 Also, I changed in the Proxmox webgui the vga/display setting to display: none for the guest. Yes, this is the complete...
  14. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    Thank you for your reply. Alright, I just changed the disable_vga=1 to vga=none and rebooted the host. ~$ sudo cat /etc/modprobe.d/vfio.conf options vfio-pci ids=1002:677b,1002:aa98 vga=none Also, yes, after update-initramfs -u I rebooted the host (and with it the guests then), yesterday...
  15. Proxmox (Ryzen) GPU (ATI) passthrough to a existing VM with Debian

    Hi guys, I have a Proxmox host with a Ryzen processor and one GPU, an old AMD card (R5 230 with TeraScale 2). I would like to pass the GPU through to a existing guest with Debian (64 bit), although I am not using the desktop there. I just need the card to be active and having a responsive...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!