Search results

That is correct.

Thank you for posting this... we had a couple other threads going and I couldn't figure out why i couldn't pass the card thru. After disabling rombar it now works!

This fixed my issues: https://forum.proxmox.com/threads/proxmox-ve-9-pcie-passthrough-truenas-vm.170330/#post-796150 Hope it helps someone else

Ok, mine is sorted out with: https://forum.proxmox.com/threads/proxmox-ve-9-pcie-passthrough-truenas-vm.170330/#post-796150 Seems its a power state issue, i can confirm this worked for me.

I'm also not getting exactly the same logs as seiichiro0185. This is my journal output: Sep 03 13:48:15 pve-backup pvedaemon[1549]: VM 700 started with PID 1596. Sep 03 13:48:15 pve-backup kernel: vfio-pci 0000:05:00.0: reset done Sep 03 13:48:15 pve-backup kernel: vfio-pci 0000:05:00.0...

I also tried the libata.force=nolpm and this did not work for me and I am running a asm1166. I also saw no differences in lspci. I'm also only using this as a backup so it only has 1 VM and 1 LXC on the machine... it doesn't get more bare bones.

I am also having this issue. Let me know if i can help with logs or testing. (ASM1166)

This does work, but was hoping to get 6.14 fixed up. I found one of the threads you were talking about but there is no fix at the moment from that thread. My only recourse appears to revert back to 6.8

So i didnt change my PCI passthru of a sata controller. I had this same setup on another intel version of the same type system. I did notice that PVE is loading the controller. I have it blocked in both grub and modprobe. lspci -n: 05:00.0 0106: 1b21:1166 (rev 02) Grub...

Here is output: root@pve-backup:~# grep -sR "hostpci" /etc /etc/pve/local/qemu-server/700.conf:hostpci0: 0000:05:00,pcie=1 /etc/pve/qemu-server/700.conf:hostpci0: 0000:05:00,pcie=1 /etc/pve/nodes/pve-backup/qemu-server/700.conf:hostpci0: 0000:05:00,pcie=1 root@pve-backup:~# lspci 00:00.0 Host...

I have upgraded several of our intel servers with ZERO issues... but i have a small backup server that it using a Ryzen 5 5600g and it ran like a top prior to upgrade, after the upgrade it wont start anything. No VM's not LXC's. It boots fine, seems likes its all there but as soon as you start a...

So i have a fully working sr-iov with a vm that works perfect, with the exception that PVE cant see it. So if i go to outside machine i can see all IP's, but if i go to the PVE machine it cant see the sr-iov adapter. Im hoping someone can point me in the right direction... i have a...

Ok, I just did the updates for today... so something else must have needed updated because its all working! Thank you!

1) - Yes, in fact i downed the server after update and brought it up fresh. 2) - pveversion output: proxmox-ve: 7.2-1 (running kernel: 5.15.39-3-pve) pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85) pve-kernel-5.15: 7.2-8 pve-kernel-helper: 7.2-8 pve-kernel-5.13: 7.1-9 pve-kernel-5.4...

Upgraded to 7 and still have the issue... Any other suggestions? On a reboot it just sits there stuck with less than 1% cpu doing nothing but showing a black screen. I've tried to use both a host and a kvm64 processor... both produced the same result.

So at one point this issue went away... maybe a few months ago... sorry id have to go back in this thread... I havent had any issues on 5.13 and qemu 6.2 until the most recent update. I'm using uefi (i know you were looking for people using the 4m version) and a Q35 machine. It acts very strange...

So i'm trying to do something unconventional on older hardware. Ill explain where i am and what doesnt work and see if anyone can help me. I setup ZFS under proxmox and passed it via a mount to an LXC container. I have that working great and Urbackup is backing up into this setup no problem...

I havent tried it a second time since the 7.2 upgrade. But prior to 7.2 yes I can replicate this issue over and over, mind you only since moving from 6 to 7. I'll do some more testing offline and let you know what I find.

Well I still have the same issue (fully upgraded on 7.2)... but i've found that if I shut down that seems to work ok... then I can just start from the console... but if I do a reboot from within the VM, it still hangs as before.

I'm using 6.2 now and the issue persists... and with new updates on ubuntu, I have the same issue now in linux. Maybe I wasnt clear in my last post... When i go to reboot the machines (now linux or windows) the machine goes down to a black screen... but never shuts off and never goes into a...