Recent content by Stefan Radman

With regards to the E610 you might be interested in this Intel Community Support thread. https://community.intel.com/t5/Ethernet-Products/E610-XT2-No-Longer-Seen-in-Proxmox-9-PC/m-p/1725698

No, I don't have any E610 card in my systems.

Here are the steps: root@pve1:~# wget https://github.com/intel/ethernet-linux-ixgbe/releases/download/v6.3.4/ixgbe-6.3.4.tar.gz root@pve1:~# tar xvpf ixgbe-6.3.4.tar.gz root@pve1:~# cd ixgbe-6.3.4/src/ root@pve1:~/ixgbe-6.3.4/src# apt install pve-headers build-essential...

Update: PVE 9.1 kernel 6.17.4-2-pve requires ixgbe-6.3.4 or later. With older driver versions you'll run into a build error.

I had the same build issue with ixgbe-6.2.5 under PVE 9.1 (kernel 6.17.4-2-pve). This now appears to be resolved in the latest driver release ixgbe-6.3.4. Today I successfully built ixgbe-6.3.4 with kernel 6.17.4-2-pve (to resolve this issue) and it is working well for me.

I had a private email exchange with julienfortin a while ago to make him aware of the issue. His motivation for the commit was that "On Mellanox switches, having a sub interface on a physical port that is part of a bond is an invalid config". Today I notified him that his patch has largely been...

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...