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]
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...
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?
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)?
Alright, this is the rom file size:
~$ ls -lah /usr/share/kvm/
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...
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: start VM 103: UPID:rakete:00001EF3:00276797:61A2CE6F:qmstart:103:root@pam:
Nov 28 01:33:51 rakete pvedaemon: <root@pam> starting...
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.
~$ sudo journalctl -f
-- Logs begin at Sat 2021-11-27 16:59:16 CET. --
Nov 27 18:10:20 rakete pvedaemon: start VM 103: UPID:rakete:000045B5:000683CA:61A2667C:qmstart:103:root@pam:
Nov 27 18:10:20 rakete pvedaemon: <root@pam> starting task...
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_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo 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:
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...
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...
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...
I have two SSDs running Proxmox and two HDDs connected to it, which are mounted as "hddpool", see below:
Now, I am not sure, how to give access to the VMs/guests properly so they can reach the "hddpool" and store files there.
As far as I know, if I mount "hddpool" to each VM this...
I wanted to update my Proxmox host.
Unfortunately, apt update && apt upgrade && apt dist-upgrade tells me, everything has the newest state.
Is there something wrong with my sources?
I read through the repository documentation, aber could not find anything wrong in my sources so...