Search results

we are working on a small Proxmox enviroment with 3 nodes and mesh network. All servers have 2x 10GB copper in mesh for Ceph cluster network 2x 1GB copper in mesh (corosync) 2x 1GB free for exiting network to customer 2x10GB SFP+ not used yet. (might be used for VM traffic and Ceph public subnet...

Addition: on the current latest virtio drivers package (0.1.217) there is an official Windows11 driver for VirtIO.

Funny, i'm still investigating. Last weekend i updated all nodes. I still have the mentioned temporary fix active (run with Cron @reboot)and after a reboot i saw "some but not many" spurious logs again. Trying to manual disable interrupts it said "nothing to change" so Cron is working. After...

Run the command above. Keep in mind the interface will reinitialize and disconnect for a few seconds. It worked for our enviroment. CPU raise not noticable.

@smasty Have you a solution yet?

This morning our 3th node crashed again (out of diskspace) After deleting: /var/log/syslog /var/log/messages /var/log/kern.log and a reboot it is working again. The spurious interrupt records are filling up logging very fast. For now solved by creating a cronjob emptying these files every hour.

Same problem here. Since update yesterday from version 5.4.x to 6.1-5 We have the same Intel 10Gbit interfaces. We had over 64GB of logging in kern.log filling up OS disk