BANK1 CMCI storm detected

N

nymphxyz

New Member
Jul 20, 2024
3
0
1
I am trying to install the win 11 VM on PVE 8.2.4.

Here are my pve machine details:
1721478669843.png


And I just found if I set my win 11 vcpu to 20 (I only start this VM) it will have these error:

1721478743619.png

journalctl :

Code: 
root@pve:~# journalctl -f
Jul 20 22:17:21 pve systemd[2149]: Reached target default.target - Main User Target.
Jul 20 22:17:21 pve systemd[2149]: Startup finished in 91ms.
Jul 20 22:17:21 pve systemd[1]: Started user@0.service - User Manager for UID 0.
Jul 20 22:17:21 pve systemd[1]: Started session-2.scope - Session 2 of User root.
Jul 20 22:17:21 pve login[2165]: ROOT LOGIN  on '/dev/pts/0'
Jul 20 22:19:57 pve pvedaemon[1277]: <root@pam> update VM 103: -cores 8 -cpu host -delete vcpus,affinity,cpuunits,cpulimit -numa 0 -sockets 2
Jul 20 22:19:57 pve pvedaemon[1277]: cannot delete 'vcpus' - not set in current configuration!
Jul 20 22:19:57 pve pvedaemon[1277]: cannot delete 'affinity' - not set in current configuration!
Jul 20 22:19:57 pve pvedaemon[1277]: cannot delete 'cpuunits' - not set in current configuration!
Jul 20 22:19:57 pve pvedaemon[1277]: cannot delete 'cpulimit' - not set in current configuration!
Jul 20 22:20:05 pve pvedaemon[1278]: <root@pam> starting task UPID:pve:000009F8:0000D2D2:669BAB75:qmstart:103:root@pam:
Jul 20 22:20:05 pve pvedaemon[2552]: start VM 103: UPID:pve:000009F8:0000D2D2:669BAB75:qmstart:103:root@pam:
Jul 20 22:20:05 pve systemd[1]: Created slice qemu.slice - Slice /qemu.
Jul 20 22:20:05 pve systemd[1]: Started 103.scope.
Jul 20 22:20:05 pve kernel: tap103i0: entered promiscuous mode
Jul 20 22:20:05 pve kernel: vmbr2: port 2(fwpr103p0) entered blocking state
Jul 20 22:20:05 pve kernel: vmbr2: port 2(fwpr103p0) entered disabled state
Jul 20 22:20:05 pve kernel: fwpr103p0: entered allmulticast mode
Jul 20 22:20:05 pve kernel: fwpr103p0: entered promiscuous mode
Jul 20 22:20:05 pve kernel: vmbr2: port 2(fwpr103p0) entered blocking state
Jul 20 22:20:05 pve kernel: vmbr2: port 2(fwpr103p0) entered forwarding state
Jul 20 22:20:05 pve kernel: fwbr103i0: port 1(fwln103i0) entered blocking state
Jul 20 22:20:05 pve kernel: fwbr103i0: port 1(fwln103i0) entered disabled state
Jul 20 22:20:05 pve kernel: fwln103i0: entered allmulticast mode
Jul 20 22:20:05 pve kernel: fwln103i0: entered promiscuous mode
Jul 20 22:20:05 pve kernel: fwbr103i0: port 1(fwln103i0) entered blocking state
Jul 20 22:20:05 pve kernel: fwbr103i0: port 1(fwln103i0) entered forwarding state
Jul 20 22:20:05 pve kernel: fwbr103i0: port 2(tap103i0) entered blocking state
Jul 20 22:20:05 pve kernel: fwbr103i0: port 2(tap103i0) entered disabled state
Jul 20 22:20:05 pve kernel: tap103i0: entered allmulticast mode
Jul 20 22:20:05 pve kernel: fwbr103i0: port 2(tap103i0) entered blocking state
Jul 20 22:20:05 pve kernel: fwbr103i0: port 2(tap103i0) entered forwarding state
Jul 20 22:20:05 pve pvedaemon[1278]: <root@pam> end task UPID:pve:000009F8:0000D2D2:669BAB75:qmstart:103:root@pam: OK
Jul 20 22:20:05 pve kernel: x86/split lock detection: #AC: CPU 13/KVM/2668 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:20:05 pve kernel: x86/split lock detection: #AC: CPU 1/KVM/2656 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:20:05 pve kernel: x86/split lock detection: #AC: CPU 2/KVM/2657 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:20:05 pve kernel: x86/split lock detection: #AC: CPU 3/KVM/2658 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:20:05 pve kernel: x86/split lock detection: #AC: CPU 12/KVM/2667 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:20:05 pve kernel: x86/split lock detection: #AC: CPU 11/KVM/2666 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:20:05 pve kernel: x86/split lock detection: #AC: CPU 5/KVM/2660 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:20:05 pve kernel: x86/split lock detection: #AC: CPU 7/KVM/2662 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:20:05 pve kernel: x86/split lock detection: #AC: CPU 14/KVM/2669 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:20:05 pve kernel: x86/split lock detection: #AC: CPU 4/KVM/2659 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:20:06 pve pvedaemon[2674]: starting vnc proxy UPID:pve:00000A72:0000D34C:669BAB76:vncproxy:103:root@pam:
Jul 20 22:20:06 pve pvedaemon[1277]: <root@pam> starting task UPID:pve:00000A72:0000D34C:669BAB76:vncproxy:103:root@pam:
Jul 20 22:20:42 pve pvedaemon[1277]: <root@pam> end task UPID:pve:00000A72:0000D34C:669BAB76:vncproxy:103:root@pam: OK
Jul 20 22:20:47 pve pvedaemon[2768]: stop VM 103: UPID:pve:00000AD0:0000E36A:669BAB9F:qmstop:103:root@pam:
Jul 20 22:20:47 pve pvedaemon[1277]: <root@pam> starting task UPID:pve:00000AD0:0000E36A:669BAB9F:qmstop:103:root@pam:
Jul 20 22:20:47 pve kernel: tap103i0: left allmulticast mode
Jul 20 22:20:47 pve kernel: fwbr103i0: port 2(tap103i0) entered disabled state
Jul 20 22:20:47 pve kernel: fwbr103i0: port 1(fwln103i0) entered disabled state
Jul 20 22:20:47 pve kernel: vmbr2: port 2(fwpr103p0) entered disabled state
Jul 20 22:20:47 pve kernel: fwln103i0 (unregistering): left allmulticast mode
Jul 20 22:20:47 pve kernel: fwln103i0 (unregistering): left promiscuous mode
Jul 20 22:20:47 pve kernel: fwbr103i0: port 1(fwln103i0) entered disabled state
Jul 20 22:20:47 pve kernel: fwpr103p0 (unregistering): left allmulticast mode
Jul 20 22:20:47 pve kernel: fwpr103p0 (unregistering): left promiscuous mode
Jul 20 22:20:47 pve kernel: vmbr2: port 2(fwpr103p0) entered disabled state
Jul 20 22:20:47 pve qmeventd[878]: read: Connection reset by peer
Jul 20 22:20:47 pve pvedaemon[1278]: VM 103 qmp command failed - VM 103 not running
Jul 20 22:20:47 pve pvedaemon[1277]: <root@pam> end task UPID:pve:00000AD0:0000E36A:669BAB9F:qmstop:103:root@pam: OK
Jul 20 22:20:48 pve systemd[1]: 103.scope: Deactivated successfully.
Jul 20 22:20:48 pve systemd[1]: 103.scope: Consumed 29.690s CPU time.
Jul 20 22:20:48 pve qmeventd[2795]: Starting cleanup for 103
Jul 20 22:20:48 pve qmeventd[2795]: Finished cleanup for 103
Jul 20 22:21:01 pve pvedaemon[1278]: <root@pam> update VM 103: -ide2 local:iso/Win11_23H2_English_x64v2.iso,media=cdrom
Jul 20 22:21:17 pve pvedaemon[1278]: <root@pam> update VM 103: -boot order=virtio0;ide2;net0;ide0
Jul 20 22:21:20 pve pvedaemon[2873]: start VM 103: UPID:pve:00000B39:0000F039:669BABC0:qmstart:103:root@pam:
Jul 20 22:21:20 pve pvedaemon[1277]: <root@pam> starting task UPID:pve:00000B39:0000F039:669BABC0:qmstart:103:root@pam:
Jul 20 22:21:20 pve systemd[1]: Started 103.scope.
Jul 20 22:21:20 pve kernel: tap103i0: entered promiscuous mode
Jul 20 22:21:21 pve kernel: vmbr2: port 2(fwpr103p0) entered blocking state
Jul 20 22:21:21 pve kernel: vmbr2: port 2(fwpr103p0) entered disabled state
Jul 20 22:21:21 pve kernel: fwpr103p0: entered allmulticast mode
Jul 20 22:21:21 pve kernel: fwpr103p0: entered promiscuous mode
Jul 20 22:21:21 pve kernel: vmbr2: port 2(fwpr103p0) entered blocking state
Jul 20 22:21:21 pve kernel: vmbr2: port 2(fwpr103p0) entered forwarding state
Jul 20 22:21:21 pve kernel: fwbr103i0: port 1(fwln103i0) entered blocking state
Jul 20 22:21:21 pve kernel: fwbr103i0: port 1(fwln103i0) entered disabled state
Jul 20 22:21:21 pve kernel: fwln103i0: entered allmulticast mode
Jul 20 22:21:21 pve kernel: fwln103i0: entered promiscuous mode
Jul 20 22:21:21 pve kernel: fwbr103i0: port 1(fwln103i0) entered blocking state
Jul 20 22:21:21 pve kernel: fwbr103i0: port 1(fwln103i0) entered forwarding state
Jul 20 22:21:21 pve kernel: fwbr103i0: port 2(tap103i0) entered blocking state
Jul 20 22:21:21 pve kernel: fwbr103i0: port 2(tap103i0) entered disabled state
Jul 20 22:21:21 pve kernel: tap103i0: entered allmulticast mode
Jul 20 22:21:21 pve kernel: fwbr103i0: port 2(tap103i0) entered blocking state
Jul 20 22:21:21 pve kernel: fwbr103i0: port 2(tap103i0) entered forwarding state
Jul 20 22:21:21 pve pvedaemon[1277]: <root@pam> end task UPID:pve:00000B39:0000F039:669BABC0:qmstart:103:root@pam: OK
Jul 20 22:21:21 pve kernel: split_lock_warn: 4 callbacks suppressed
Jul 20 22:21:21 pve kernel: x86/split lock detection: #AC: CPU 15/KVM/2988 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:21:21 pve kernel: x86/split lock detection: #AC: CPU 2/KVM/2975 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:21:21 pve kernel: x86/split lock detection: #AC: CPU 1/KVM/2974 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:21:21 pve kernel: x86/split lock detection: #AC: CPU 13/KVM/2986 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:21:21 pve kernel: x86/split lock detection: #AC: CPU 12/KVM/2985 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:21:21 pve kernel: x86/split lock detection: #AC: CPU 10/KVM/2983 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:21:21 pve kernel: x86/split lock detection: #AC: CPU 4/KVM/2977 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:21:21 pve kernel: x86/split lock detection: #AC: CPU 5/KVM/2978 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:21:21 pve kernel: x86/split lock detection: #AC: CPU 6/KVM/2979 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:21:21 pve kernel: x86/split lock detection: #AC: CPU 11/KVM/2984 took a split_lock trap at address: 0x7ee5d050
Jul 20 22:21:21 pve pvedaemon[2992]: starting vnc proxy UPID:pve:00000BB0:0000F0B5:669BABC1:vncproxy:103:root@pam:
Jul 20 22:21:21 pve pvedaemon[1276]: <root@pam> starting task UPID:pve:00000BB0:0000F0B5:669BABC1:vncproxy:103:root@pam:
Jul 20 22:21:39 pve kernel: mce: [Hardware Error]: Machine check events logged
Jul 20 22:21:39 pve kernel: mce: [Hardware Error]: Machine check events logged
Jul 20 22:21:39 pve kernel: CPU12 BANK1 CMCI storm detected
Jul 20 22:21:39 pve kernel: CPU16 BANK1 CMCI storm detected
Jul 20 22:21:56 pve pvedaemon[1276]: <root@pam> end task UPID:pve:00000BB0:0000F0B5:669BABC1:vncproxy:103:root@pam: OK
Jul 20 22:22:00 pve pvedaemon[1278]: <root@pam> starting task UPID:pve:00000C22:0000FFC7:669BABE8:qmstop:103:root@pam:
Jul 20 22:22:00 pve pvedaemon[3106]: stop VM 103: UPID:pve:00000C22:0000FFC7:669BABE8:qmstop:103:root@pam:
Jul 20 22:22:00 pve kernel: tap103i0: left allmulticast mode
Jul 20 22:22:00 pve kernel: fwbr103i0: port 2(tap103i0) entered disabled state
Jul 20 22:22:00 pve kernel: fwbr103i0: port 1(fwln103i0) entered disabled state
Jul 20 22:22:00 pve kernel: vmbr2: port 2(fwpr103p0) entered disabled state
Jul 20 22:22:00 pve kernel: fwln103i0 (unregistering): left allmulticast mode
Jul 20 22:22:00 pve kernel: fwln103i0 (unregistering): left promiscuous mode
Jul 20 22:22:00 pve kernel: fwbr103i0: port 1(fwln103i0) entered disabled state
Jul 20 22:22:00 pve kernel: fwpr103p0 (unregistering): left allmulticast mode
Jul 20 22:22:00 pve kernel: fwpr103p0 (unregistering): left promiscuous mode
Jul 20 22:22:00 pve kernel: vmbr2: port 2(fwpr103p0) entered disabled state
Jul 20 22:22:00 pve qmeventd[878]: read: Connection reset by peer
Jul 20 22:22:00 pve pvedaemon[1276]: VM 103 qmp command failed - VM 103 not running
Jul 20 22:22:00 pve pvedaemon[1278]: <root@pam> end task UPID:pve:00000C22:0000FFC7:669BABE8:qmstop:103:root@pam: OK
Jul 20 22:22:00 pve systemd[1]: 103.scope: Deactivated successfully.
Jul 20 22:22:00 pve systemd[1]: 103.scope: Consumed 1min 25.743s CPU time.
Jul 20 22:22:00 pve qmeventd[3133]: Starting cleanup for 103
Jul 20 22:22:00 pve qmeventd[3133]: Finished cleanup for 103
Jul 20 22:22:06 pve kernel: RAS: Soft-offlining pfn: 0xa2bf43
Jul 20 22:22:06 pve kernel: Memory failure: 0xa2bf43: unhandlable page.
Jul 20 22:22:10 pve pvedaemon[1277]: <root@pam> update VM 103: -cores 10 -cpu host -delete vcpus,affinity,cpuunits,cpulimit -numa 0 -sockets 2
Jul 20 22:22:10 pve pvedaemon[1277]: cannot delete 'vcpus' - not set in current configuration!
Jul 20 22:22:10 pve pvedaemon[1277]: cannot delete 'affinity' - not set in current configuration!
Jul 20 22:22:10 pve pvedaemon[1277]: cannot delete 'cpuunits' - not set in current configuration!
Jul 20 22:22:10 pve pvedaemon[1277]: cannot delete 'cpulimit' - not set in current configuration!
Jul 20 22:22:13 pve pvedaemon[3161]: start VM 103: UPID:pve:00000C59:000104D1:669BABF5:qmstart:103:root@pam:
Jul 20 22:22:13 pve pvedaemon[1277]: <root@pam> starting task UPID:pve:00000C59:000104D1:669BABF5:qmstart:103:root@pam:
Jul 20 22:22:13 pve systemd[1]: Started 103.scope.
Jul 20 22:22:13 pve kernel: tap103i0: entered promiscuous mode
Jul 20 22:22:13 pve kernel: vmbr2: port 2(fwpr103p0) entered blocking state
Jul 20 22:22:13 pve kernel: vmbr2: port 2(fwpr103p0) entered disabled state
Jul 20 22:22:13 pve kernel: fwpr103p0: entered allmulticast mode
Jul 20 22:22:13 pve kernel: fwpr103p0: entered promiscuous mode
Jul 20 22:22:13 pve kernel: vmbr2: port 2(fwpr103p0) entered blocking state
Jul 20 22:22:13 pve kernel: vmbr2: port 2(fwpr103p0) entered forwarding state
Jul 20 22:22:13 pve kernel: fwbr103i0: port 1(fwln103i0) entered blocking state
Jul 20 22:22:13 pve kernel: fwbr103i0: port 1(fwln103i0) entered disabled state
Jul 20 22:22:13 pve kernel: fwln103i0: entered allmulticast mode
Jul 20 22:22:13 pve kernel: fwln103i0: entered promiscuous mode
Jul 20 22:22:13 pve kernel: fwbr103i0: port 1(fwln103i0) entered blocking state
Jul 20 22:22:13 pve kernel: fwbr103i0: port 1(fwln103i0) entered forwarding state
Jul 20 22:22:13 pve kernel: fwbr103i0: port 2(tap103i0) entered blocking state
Jul 20 22:22:13 pve kernel: fwbr103i0: port 2(tap103i0) entered disabled state
Jul 20 22:22:13 pve kernel: tap103i0: entered allmulticast mode
Jul 20 22:22:13 pve kernel: fwbr103i0: port 2(tap103i0) entered blocking state
Jul 20 22:22:13 pve kernel: fwbr103i0: port 2(tap103i0) entered forwarding state
Jul 20 22:22:13 pve pvedaemon[1277]: <root@pam> end task UPID:pve:00000C59:000104D1:669BABF5:qmstart:103:root@pam: OK
Jul 20 22:22:14 pve kernel: split_lock_warn: 2 callbacks suppressed
Jul 20 22:22:14 pve kernel: x86/split lock detection: #AC: CPU 16/KVM/3281 took a split_lock trap at address: 0x7ee1c050
Jul 20 22:22:14 pve kernel: x86/split lock detection: #AC: CPU 18/KVM/3283 took a split_lock trap at address: 0x7ee1c050
Jul 20 22:22:14 pve kernel: x86/split lock detection: #AC: CPU 17/KVM/3282 took a split_lock trap at address: 0x7ee1c050
Jul 20 22:22:14 pve kernel: x86/split lock detection: #AC: CPU 6/KVM/3271 took a split_lock trap at address: 0x7ee1c050
Jul 20 22:22:14 pve kernel: x86/split lock detection: #AC: CPU 12/KVM/3277 took a split_lock trap at address: 0x7ee1c050
Jul 20 22:22:14 pve kernel: x86/split lock detection: #AC: CPU 14/KVM/3279 took a split_lock trap at address: 0x7ee1c050
Jul 20 22:22:14 pve kernel: x86/split lock detection: #AC: CPU 19/KVM/3284 took a split_lock trap at address: 0x7ee1c050
Jul 20 22:22:14 pve kernel: x86/split lock detection: #AC: CPU 15/KVM/3280 took a split_lock trap at address: 0x7ee1c050
Jul 20 22:22:14 pve kernel: x86/split lock detection: #AC: CPU 7/KVM/3272 took a split_lock trap at address: 0x7ee1c050
Jul 20 22:22:14 pve kernel: x86/split lock detection: #AC: CPU 1/KVM/3266 took a split_lock trap at address: 0x7ee1c050
Jul 20 22:22:26 pve pvedaemon[1277]: <root@pam> starting task UPID:pve:00000D07:000109FC:669BAC02:vncproxy:103:root@pam:
Jul 20 22:22:26 pve pvedaemon[3335]: starting vnc proxy UPID:pve:00000D07:000109FC:669BAC02:vncproxy:103:root@pam:
Jul 20 22:22:36 pve kernel: CPU16 BANK1 CMCI storm subsided
Jul 20 22:22:36 pve kernel: CPU12 BANK1 CMCI storm subsided


And then my machine will restart.

If I changed the CPU to 18 cores, everything would be back to normal.

I don't know much about hardware and PVE; not sure what's going on here.
 
18 is still unstable. I tried to start it a few times, and it has a 40% chance of breaking. It breaks at the time it displays the logo of Win 11.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom