Search results

apt update && apt install pve-kernel-6.8.12-11-pve promox-boot-tool kernel pin 6.8.12-11-pve and then you'll need to update-initramfs -u -k all Thanks again @v95klima !

Has anyone had any luck passing through an LSI SAS9207-8e HBA to an unprivileged Proxmox LXC? SYSTEM: OS: Proxmox VE bookworm 8.4.1 x86_64 Kernel: Linux 6.11.11-2-pve MoBo: ASRock X570 Taichi CPU: AMD Ryzen 9 5950X (32) @ 5.08 GHz GPU: MSI Radeon RX 560 4GT LP OC Memory: 64 GiB Kingston -...

Unfortunately, it appears that resolving this issue is not on Proxmox's agenda (note the length of time for this thread). Like you, one day it worked, and then it didn't. I suspect this is a problem for many others using PCI passthrough for their GPUs; they just haven't realized yet that it is...

I'm still troubleshooting and I'm not sure if this dmsg could be a clue: dmesg | grep vfio-pci [ 11.784824] vfio-pci 0000:0f:00.0: vgaarb: deactivate vga console [ 11.784830] vfio-pci 0000:0f:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem [ 105.058516]...

I just updated Proxmox and the Win 11 VM today, but I'm receiving the same output as in my earlier posts. post-746917 post-753865 I am happy to complete detailed troubleshooting with you if you'd like to PM... or let me know exactly what you'd like.

Still broken. Rebooting a windows VM with PCI Passthrough (GPU) reboots the system. OS: Proxmox VE bookworm 8.4.1 x86_64 Kernel: Linux 6.11.11-2-pve CPU: AMD Ryzen 9 5950X (32) @ 5.08 GHz GPU: AMD Radeon RX 560 Series Memory: 18.10 GiB / 62.72 GiB (29%)

I installed pve-qemu-kvm (9.2.0-2) over (9.2.0-1) rebooted. Adjusted the vm to use qm 9.2 Tested. No fix to the system crash. I then replaced kernel 6.8.12-8-pve with kernel 6.11.11-1-pve rebooted Tested. No fix to the system crash.

Out of curiosity, has this problem been resolved for anyone else monitoring this thread? Thanks

I am having similar problems. Rebooting my Windows 11 VM(120) w RX560 PCIe Passthrough causes my Host to reboot on: pcieport 0000:00:03.1: AER: Correctable error message received from 0000:00:03.1 pcieport 0000:00:03.1: PCIe Bus Error: severity=Correctable, type=Transaction Layer, (Receiver ID)...

I had the same issue but with the rx560. Originally, I used "non-whql-radeon-software-adrenalin-2020-21.2.3-win10-64bit-feb22" which would work with Spice. But I could not install any newer drivers nor Arenaline. My solution was : VM > Hardware > Display > Graphic Card: none Install AMD...

Did you try hostpci0: 00:02,pcie=1,x-vga=1 or hostpci0: 00:02,x-vga=1 Note: hostpci0 vs 1

Nevermind. My steps were basically correct... Find the drive name fdisk -l Partition the disk sgdisk -N 1 /dev/sdb reboot Create a Physical Volume pvcreate /dev/sdb1 Create Volume Group vgcreate vg-taichi /dev/sdb Create Thin Pool lvcreate -l 100%FREE --thinpool tp-taichi vg-taichi My...

So I started over. I installed PVE on a new drive (sdb) and I was able to see the and create VGs on the second drive (sda). I hate asking this question, because the instructions are somewhere probably blatantly obvious the I am overlooking, but how do I add a thin storage on sda to house my VMs...

...Shouldn't this have been enough? sgdisk -N 1 /dev/sdb reboot pvcreate /dev/sdb1 vgcreate vg-taichi /dev/sdb1 Should I even need to do these through the console? lvcreate -l 100%FREE --thinpool tp-taichi vg-taichi lvcreate -V 250G --thin -n tv-taichi_data vg-taichi/tp-taichi

I agree with you. That's kind of my problem. At each step in the process I expected to see the volumes in the dashboard (or have the option to create something with them), but the disks/volumes were never available. The dashboard shows sdb, but nothing is in LVM or LVM-Thin. I just went down my...

Hi, I am lost. I have a new installation of Proxmox 6. My goal is to add a new thin storage area for vm's on separate physical storage from pve. But I can not see the storage/volumes in the Proxmox front end. I have followed every manual and post I could find ...so I am obviously missing...