search for: watchdog_thresh

Not sure if this was the last email on this.? If not ignore me. However I found a post for new operating systems that says to set the watchdog_thresh value instead of softlockup_thresh.? http://askubuntu.com/questions/592412/why-is-there-no-proc-sys-kernel-softlockup-thresh this is an Ubuntu post, but on my CentOS 7 system this parameter exists, and softlockup_thresh does not.??I have set it but I will need to see if I still get the CPU lock up...

...m0 scheduler a chance to run. As this is not performance critical it should not be a problem. I can reproduce this with SLES11-SP3 with Linux 3.0.101 and xen-4.2.2. # cat dummy name = "DummyOS" memory = 10000 maxmem = 12000 builder=''hvm'' # echo 1 > /proc/sys/kernel/watchdog_thresh # xm create -c dummy This leads to a kernel message: kernel: [ 5019.958089] BUG: soft lockup - CPU#4 stuck for 3s! [xend:20854] Any comments are welcome. Thanks. Dietmar. -- Company details: http://ts.fujitsu.com/imprint.html

Hi, here is the next version of changes to enable Linux to run as an SEV-ES guest. The code was rebased to v5.7-rc3 and got a fair number of changes since the last version. What is SEV-ES ============== SEV-ES is an acronym for 'Secure Encrypted Virtualization - Encrypted State' and means a hardware feature of AMD processors which hides the register state of VCPUs to the hypervisor by

Hi, here is the next version of changes to enable Linux to run as an SEV-ES guest. The code was rebased to v5.7-rc3 and got a fair number of changes since the last version. What is SEV-ES ============== SEV-ES is an acronym for 'Secure Encrypted Virtualization - Encrypted State' and means a hardware feature of AMD processors which hides the register state of VCPUs to the hypervisor by