Recent content by jsabater

I have not used PVE 9 yet. What kernel version does it use? There is this bug in the bug tracker, specific for kernel versions 6.8.12, but I have not been able to find a more recent one for PVE 9.

For future reference, as I presume users will keep on visiting this thread: dpkg -l |grep proxmox-kernel proxmox-boot-tool kernel pin 6.8.12-8-pve And reboot. P.S. Not sure if I already posted this before... :D

Would you confirm that kernel 6.8.12-13 fixed it for you? Which exact NIC model are you using?

From my experience, if you use kernel 6.8.12-8-pve, then you do not need to disable offloading, or adding additional parametres, for that matter.

The same happens to me, both in the nodes and inside the LXC. I two following commands failed: # resolvectl flush-caches Failed to flush caches: Unit dbus-org.freedesktop.resolve1.service not found. # systemd-resolve --flush-caches Failed to flush caches: Unit...

Reverting back to version 6.8.12-8-pve should solve the issue.

I am closely following this bug in the Bugzilla of Proxmox, but it is specific to kernel version 6.8.12-9-pve and above, as it affects my PBS servers. However, I am also in charge of Proxmox VE 7.4-20 nodes still running kernels 5.15.158-2, which also seem affected by the NIC bug. Would anyone...

List the kernels: # proxmox-boot-tool kernel list 6.5.13-6-pve 6.8.12-11-pve 6.8.12-8-pve 6.8.12-9-pve Ping the desired kernel: proxmox-boot-tool kernel pin 6.8.12-8-pve --next-boot In your case it would be, if I read correctly, 5.11.22-7-pve. Reboot. Uninstall the kernels you don't want...

Thanks for reporting this. Good to know!

Thanks a lot for your report, @leiwang15 . Much appreciated. Incidentally, I found this thread on these forums regarding E1000E vs VirtIO on Proxmox.

Hi, Fabian. Thanks for the link to the bug tracker. I have contributed to it. I hope it can be solved soon.

This is what I do to remove a node (e.g., proxmox5) from the cluster (Proxmox 7.4-19) after the pvecm delnode proxmox5 command has finished its execution at another node (e.g., proxmox1) and the deleted node has been shut down: rm --recursive --force /etc/pve/nodes/proxmox5 sed -i.bak...

I have come up with these two solutions for my plays/provision.yml Ansible playbook, that provisions LXC in the Proxmox cluster: Reinstall all packages containing the setcap command: apt-get --reinstall install iproute2 iputils-ping libcap2-bin. Fix permissions of the affected binary: setcap...

I followed the same procedure when re-adding a re-installed node and the first time it went fine (pvecm updatecerts did the job). But the second time I had to re-add the same node, after re-installing it again due to hardware issues, it did not. So I had to go through all the...

I presume that you executed the command in the PVE node, not inside the VM, correct? Moreover, what other guests did you have in the node? I have a mix of VMs and LXCs and this behaviour only happens where I have VMs. Would that be your case, too?