kernel: fwbr118i0: port 2(tap118i0) entered disabled state

[zhangkun]

The physical node server named three, the virtual machine with id 118 above suddenly crashed.
After checking the physical machine log from the web page, the following error was found. The temporary solution is to restart the virtual machine, and it can be used again.
After a few days, the same situation occurs again, and the cycle repeats.
Taking the time range before and after the virtual machine crash as the range, query the physical machine resource usage is normal, query the virtual machine resource usage is normal

version:
root@three:~# pveversion
pve-manager/7.0-11/63d82f4e (running kernel: 5.11.22-4-pve)



Jun 05 18:35:00 three systemd[1]: Starting Proxmox VE replication runner...
Jun 05 18:35:01 three systemd[1]: pvesr.service: Succeeded.
Jun 05 18:35:01 three systemd[1]: Finished Proxmox VE replication runner.
Jun 05 18:35:28 three kernel: kvm[3893975]: segfault at 563b8cd93340 ip 0000563b8cd93340 sp 00007f82103c4fa8 error 15
Jun 05 18:35:28 three kernel: Code: 00 00 30 00 00 00 00 00 00 00 2f 6d 61 63 68 69 6e 65 2f 70 65 72 69 70 68 65 72 61 6c 2f 62 61 6c 6c 6f 6f 6e 30 00 61 63 6b <65> 6e 64 00 00 00 00 00 a1 00 00 00 00 00 00 00 b0 d2 f2 8b 3b 56
Jun 05 18:35:32 three kernel: fwbr118i0: port 2(tap118i0) entered disabled state
Jun 05 18:35:32 three kernel: fwbr118i0: port 2(tap118i0) entered disabled state
Jun 05 18:35:32 three systemd[1]: 118.scope: Succeeded.
Jun 05 18:35:32 three systemd[1]: 118.scope: Consumed 1d 21h 47min 51.035s CPU time.
Jun 05 18:35:32 three qmeventd[503885]: Starting cleanup for 118
Jun 05 18:35:32 three kernel: fwbr118i0: port 1(fwln118i0) entered disabled state
Jun 05 18:35:32 three kernel: vmbr0: port 7(fwpr118p0) entered disabled state
Jun 05 18:35:32 three kernel: device fwln118i0 left promiscuous mode
Jun 05 18:35:32 three kernel: fwbr118i0: port 1(fwln118i0) entered disabled state
Jun 05 18:35:32 three kernel: device fwpr118p0 left promiscuous mode
Jun 05 18:35:32 three kernel: vmbr0: port 7(fwpr118p0) entered disabled state
Jun 05 18:35:33 three qmeventd[503885]: Finished cleanup for 118
Jun 05 18:36:00 three systemd[1]: Starting Proxmox VE replication runner...
Jun 05 18:36:01 three systemd[1]: pvesr.service: Succeeded.
Jun 05 18:36:01 three systemd[1]: Finished Proxmox VE replication runner.
Jun 05 18:37:00 three systemd[1]: Starting Proxmox VE replication runner...
Jun 05 18:37:01 three systemd[1]: pvesr.service: Succeeded.
Jun 05 18:37:01 three systemd[1]: Finished Proxmox VE replication runner.
Jun 05 18:38:00 three systemd[1]: Starting Proxmox VE replication runner...
Jun 05 18:38:01 three systemd[1]: pvesr.service: Succeeded.

 

[cheiss]

After checking the physical machine log from the web page, the following error was found.

That's not an error, but rather an expected message.

Jun 05 18:35:28 three kernel: kvm[3893975]: segfault at 563b8cd93340 ip 0000563b8cd93340 sp 00007f82103c4fa8 error 15
Jun 05 18:35:28 three kernel: Code: 00 00 30 00 00 00 00 00 00 00 2f 6d 61 63 68 69 6e 65 2f 70 65 72 69 70 68 65 72 61 6c 2f 62 61 6c 6c 6f 6f 6e 30 00 61 63 6b <65> 6e 64 00 00 00 00 00 a1 00 00 00 00 00 00 00 b0 d2 f2 8b 3b 56

This is the actual cause - QEMU segfaults. What kind of hardware are you running on?
I'd suggest running a memtest86+ to see if maybe the RAM is faulty, which is not that uncommon.

 

[zhangkun]

We are running a Dell R740 server. We need to open the chassis to check the brand of the memory stick. We also used the tool you mentioned to check. Since the machine light is still blue, we did not rule out the problem of the memory stick. Thank you for your reply