#AC: CPU 3/KVM/363077 took a split_lock trap at address: 0x2c7236b15f3报错

[tangshuai]

I found that when the memory allocation of the Windows virtual machine exceeds 32g, the host syslog will continue to prompt August 21 17:49:59 WG node55 kernel: x86/split lock detection: # AC: CPU 3/KVM/363077 too k a split-lock trap at address: 0x2c7236b15f3

Aug 21 17:50:15 WG-node55 kernel: x86/split lock detection: #AC: CPU 1/KVM/363220 took a split_lock trap at address: 0x1dc898315f3

Aug 21 17:50:19 WG-node55 kernel: x86/split lock detection: #AC: CPU 0/KVM/363218 took a split_lock trap at address: 0x1dc898353d2

Aug 21 17:50:20 WG node55 kernel: x86/split lock detection: # AC: CPU 3/KVM/363222 too a split-lock trap at address: 0x1dc89836bbd related logs, may I know what impact it will have, or what solutions are available

 

[tangshuai]

And I found that when allocating 64g of virtual machine memory, if hot swapping is enabled, the virtual machine cannot start normally, and hot swapping needs to be turned off to start normally

 

[cheiss]

Regarding split-lock detection, we have a dedicated wiki entry for this: Split lock detection

if hot swapping is enabled

I assume you mean hot plugging?

And I found that when allocating 64g of virtual machine memory

Please again see the appropriate section in our wiki: https://pve.proxmox.com/wiki/Hotplu...em_regions_when_hotplug_is_for_more_than_64GB
You might be also interested in the accompanying forum thread linked there, that discussed exactly this problem: https://forum.proxmox.com/threads/problem-with-hotplug-and-64gb-ram.73621/