[ovirt-users] watchdog: BUG: soft lockup - CPU#3 stuck for XXXs! mitigations?

Hello, I noticed that when you have poor "storage" performances, al the VMs are frustrated with entry like the one in the subject. Searching around there is a case under redhat: https://access.redhat.com/solutions/5427 that is suggesting to address the issue (if not possible to have rocket performances from the storage) regulating the elevator scheduler in kernel. but in a virtual machine I have this default queue: root@openproject:# cat /sys/block/sda/queue/scheduler [none] mq-deadline So it seem a little bit outdated Is this solution resolutive? Kernel Guru here what suggests? The problem is also that the datetime function of local VM (also hosted engine) return also not correct date time (often in 2177 year) after these avents creating annoying problems in DaraWareHouse and stucking all the certificate clients....