x86/split lock detection #AC: CPU 4/KVM/2577 took a split-lock trap at address...

[yunmkfed]

Hi,

I upgrade virtio to virtio-win-0.1.262.iso with two Windows VMs (Win Server 2016 and Win Server 2022). Proxmox is crashing.

Has anyone else experience this problem and is there a workaround (other than downgrading to 0.1.248.

Thanks

 

[yunmkfed]

Proxmox is still crashing irrespective of the VirtIO driver version.

I disabled split-lock detection by following the guide at https://pve.proxmox.com/wiki/Split_lock_detection. Would this prevent proxmox from crashing, taking all the VMs and Containers down?

Thanks

 

[BobhWasatch]

That is probably not your issue. This Wiki entry explains what split lock detection is.
https://pve.proxmox.com/wiki/Split_lock_detection

If you think this or the crashes was caused by upgrading virtio, the first line of troubleshooting would be to downgrade virtio to where it was before.

ETA: Oh, you linked to that Wiki article. Did you not read the whole thing?

 

[yunmkfed]

I concur. I downgraded but the issue remained. I uninstalled 0.1.262 and did a fresh install of 0.1.248.

I did and if you are saying that the problem when code addresses memory I agree, My only two observations were that I did not install any new software on the two VMs Windows Server 2016 and Windows Server 2022 (excluding upgrades). with the only thing that is different being the upgrade of VirtIIO.

VirtIO is code. I now verified that a downgrade did not sort the problem and maybe some software (Windows?) was updated - I don't know.

In the guide (end of it) there is an option to turn it split lock off. I implemented this using the second options (proxmox rather than GRUB changes). Would this solve the problem?

Thanks