Search results

In the meantime I upgraded to PVE 9.0.6 running kernel 6.14.11 but the "Warning firmware error detected FWSM" messages from the in-tree ixgbe kernel module kept coming. root@pve1:~# pveversion && journalctl --since today | fgrep 'Warning firmware error detected FWSM' | tail -2...

Same here on an R620 with Broadcom Dual 10GBASE-T (BCM57810) running PVE 8.3.5 kernel 6.8.12-8-pve. UBSAN complaining about Broadcom driver (bnx2x) during boot but all interfaces working without an issue. [ 39.054982] ------------[ cut here ]------------ [ 39.084793] UBSAN...

I am seeing exactly the same flood of warnings with two X520-T2 cards on an old Dell R710 running PVE 8.3.4 and kernel 6.8.12. root@pve1:~# pveversion pve-manager/8.3.4/65224a0f9cd294a3 (running kernel: 6.8.12-8-pve) root@pve1:~# dmesg | tail -4 [18376.827853] ixgbe 0000:06:00.1: Warning...

I had the exact same issue (DMAR ERROR) installing 8.3.1 on a 12 year old Dell R710. Adding "nomodeset intel_iommu=off" to the installer kernel command line solved it for me. https://pve.proxmox.com/wiki/Installation#nomodeset_kernel_param Thanks for the hints. Now it is running like a charm :)

Thank you. Worked like a charm for me, moving a Windows 10 VM from Windows 2019 Standard to Proxmox 8.

Thanks Fiona The update to pve-qemu-kvm 9.0.2-4 fixed the problem for us. Best regards Stefan

Hi @fiona. We have this problem as well. Host CPU AMD EPYC 7313 running PVE 8.2.7 from Enterprise repo with pve-qemu-kvm 9.0.2-3. The VM we are experiencing this with is a q35 machine with x86-64-v2-AES CPU running Rocky Linux 8. Virtual disks (virtio-scsi-single, discard, iothread, io_uring)...

Enhancement/feature request opened: #5255 Directed broadcast support for "pvenode wakeonlan" -- Stefan

I have the same issue (in 8.1.3) and looked for that feature/enhancement request in bugzilla but found nothing so I'll probably open it myself. Looking at the code it should be easy to replace the hardcoded local broadcast (255.255.255.255) with a new configuration option (e.g. "Broadcast...

I'd recommend to use home.arpa https://datatracker.ietf.org/doc/html/rfc8375 Stefan

In my case the (standalone) host waited for 3 minutes even though all guests had shut down long before. I actually used a drop-in snippet instead of editing the original service template. root@pve:~# systemctl edit pve-guests ... root@pve:~# cat...

Hi Thomas, With PVE5.2 and kernel 4.15.17-3-pve I was not able to run jumbo frames (MTU 9000) on an Intel I350 card (igb). Same configuration worked on two other nodes in the cluster with Broadcom NIC (tg3). Installation of pve kernel 4.15.17-13 solved the headache for me :) Thanks a lot Stefan