Search results

i saw you also posted this in reddit. anyway i believe this is possible, although i dont have 3090, but previously i do have a 3060 passthrough to a windows 11 machine and working perfectly with HDMI and audio output to my AV Receiver to TV. i recently changed the 3060 to 2060, but there is no...

i had 3 VGA in my homelab system, CPU 12400 with built in iGPU, a GTX1660S and a RTX2060 Intel iGPU based on Alderlake (aka SRVIO that not working as expected to have HDMI output), but recently i had successfully make Alderlake with HDMI out working perfectly. you may refer here...

i dont have AMD, cant comment, but you might want to check my latest attend on this in Alderlake intel CPU. https://forum.proxmox.com/threads/alderlake-direct-passthrough-to-linux-vm-is-working-with-hdmi-output.138049/#post-615315

simply because windows just downloaded and installed the display driver. the easiest way i do everytime will be boot in windows with a standard display, then enabled rdp, shutdown windows and passthrough display card, boot in windows and connect with RDP, and setup the display driver. after...

i had uploaded a youtube video here https://www.youtube.com/watch?v=HtAGJ9KHSIY

Somehow i got the Alderlake passthrough the intel igpu to a linux VM inside proxmox, without any additional works. Grub only have intel_iommu and pstate disabled. no need to blacklist intel driver, so i can still have HDMI screen output to my ipkvm until i started the linux host which have...

thank you, i solved it, my mistake the HA services was disabled and i forgot to enable it last time during testing.

Problem Solved，the pve-ha crm and lrm was disabled... my bad... i just do the normal way upgrade via webgui. anyway here the output.

Use of uninitialized value in string eq at /usr/share/perl5/PVE/API2/HA/Resources.pm line 40. it say OK but none of the VM get started. disable HA and manual start is ok. how to make HA with this?

thank you anyway, i decided to reinstall the host. i do notice that when i do apt update, i always come to Time Out error.

I am getting this in starting VM, i had even tried to restart the host root@homelab:/var/lib/dpkg/info# qm start 100 command '/usr/bin/kvm --version' failed: got signal 7 Detected old QEMU binary ('unknown', at least 3.0 is required) starting any vm will return the same code my package...

i just want to confirm, is reloading the kernel also result in restart of all VM? i am asking this because i was remote login to my server and installed the kexec, i can switch kernel, but every time i switch it result in all my VM get restarted. if restart of VM is compulsory then it doesnt...

i am not using AMD, but i think you may check if: 1. AMD VGA driver is installed with correctly and latest. 2. installed latest MESA, if required you can try the daily build. 3. make sure your AMD VGA driver did not get blacklisted previously due to trying to direct passthrough to VM.

or you may manually apply this patch here https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=6f070e39dec2e6d1cc60718cc022b89c9a2b7355;hp=a183576e3038f9b06c3a6f23f694693386186591 "/usr/share/perl5/PVE/QemuServer.pm"

thank you Sir, this worked! `apt install --reinstall libpve-common-perl pve-manager qemu-server`

i did tried restart the host few times. editing the VM will cause this error to appear when trying to click OK. again /var/log/pveproxy/access.log does not have any log output from that error. i am afraid i might had did some edit on the GUI or Backend, is there anyway that i can reinstall...

thank you, kindly see below: root@homelab:~# apt update Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian bullseye-updates InRelease Hit:3 https://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu focal InRelease Get:4...

hello, any suggestion?

qm set VMID --vga virtio-gl

thanks pveversion -v proxmox-ve: 7.1-2 (running kernel: 5.13.19-6-pve) pve-manager: 7.1-12 (running version: 7.1-12/b3c09de3) pve-kernel-helper: 7.2-1 pve-kernel-5.13: 7.1-9 pve-kernel-5.17.4-edge: 5.17.4-1 pve-kernel-5.17-edge: 5.17.4-1 pve-kernel-5.17.3-edge: 5.17.3-1 pve-kernel-5.16-edge...