# Cpu disabled by guest operating system, Unwanted reboot issue on rocky linux 9.2 **URL:** \ **Category:** Rocky Linux Help & Support\ **Tags:** rocky-linux-9\ **Created:** [March 6, 2024, 2:51pm UTC](https://forums.rockylinux.org/t/cpu-disabled-by-guest-operating-system-unwanted-reboot-issue-on-rocky-linux-9-2/13122 "2024-03-06T14:51:20Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![m.balkrkishna](https://avatars.discourse-cdn.com/v4/letter/m/df788c/32.png) [@m.balkrkishna](https://forums.rockylinux.org/u/m.balkrkishna)\ **Post date:** [March 6, 2024, 2:51pm UTC](https://forums.rockylinux.org/t/cpu-disabled-by-guest-operating-system-unwanted-reboot-issue-on-rocky-linux-9-2/13122/1 "2024-03-06T14:51:20Z")
I have a VM on VmWare ESXI , with below version. Rocky linux VM rocky-release-9.2-1.4.el9 on kernel-5.14.0-284.11.1.el9\_2.x86\_64 Have multiple VMs deployed, which does not have issues. one of the VM goes for a quick/fast reboot with systemd getting killed and all services restarting. on esxi side below event can be seen. during these unwanted reboot The CPU has been disabled by the guest operating system. Power off or reset the virtual machine. any suggestion on the compatible kernel which can be used with rocky-release-9.2-1.4.el9 ? any other solution or workaround for the intermittent issue ? ---
**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\ **Post date:** [March 6, 2024, 3:14pm UTC](https://forums.rockylinux.org/t/cpu-disabled-by-guest-operating-system-unwanted-reboot-issue-on-rocky-linux-9-2/13122/2 "2024-03-06T15:14:45Z")
Rocky Linux 9.2 is not supported. [Rocky Linux Release Version Guide - Rocky Linux Wiki](https://wiki.rockylinux.org/rocky/version/#__tabbed_1_2) Update your system(s) to the latest release. With that said, you need to determine where the cause of this issue is. It may not he as cut and dry as you expect. [https://kb.vmware.com/s/article/2000542](https://kb.vmware.com/s/article/2000542) ---
**Author:** ![m.balkrkishna](https://avatars.discourse-cdn.com/v4/letter/m/df788c/32.png) [@m.balkrkishna](https://forums.rockylinux.org/u/m.balkrkishna)\ **Post date:** [March 6, 2024, 3:40pm UTC](https://forums.rockylinux.org/t/cpu-disabled-by-guest-operating-system-unwanted-reboot-issue-on-rocky-linux-9-2/13122/3 "2024-03-06T15:40:49Z")
thanks Louis for update, I have gone through the documentation form VMware for this. In our case I have checked the top results just before the reboot, there is no CPU spike I could see. there are some CPU freeze issues reported on the kernel-5.14.0-284.11.1.el9\_2.x86\_64, which also looks similar to my case. Can we use the kernel version 5.14.0-362.8.1 with Rocky 9.2 ? or it can not used ? ---
**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\ **Post date:** [March 6, 2024, 4:16pm UTC](https://forums.rockylinux.org/t/cpu-disabled-by-guest-operating-system-unwanted-reboot-issue-on-rocky-linux-9-2/13122/4 "2024-03-06T16:16:59Z")
Kernels of older releases are also not supported. As I said, update your systems to the latest available versions. Doing so will isolate if some or all of your issues have been resolved in the latest available packages. ---
**Author:** ![LinuxGuy1997](https://avatars.discourse-cdn.com/v4/letter/l/d26b3c/32.png) [@LinuxGuy1997](https://forums.rockylinux.org/u/LinuxGuy1997)\ **Post date:** [March 6, 2024, 4:30pm UTC](https://forums.rockylinux.org/t/cpu-disabled-by-guest-operating-system-unwanted-reboot-issue-on-rocky-linux-9-2/13122/5 "2024-03-06T16:30:15Z")
> [@m.balkrkishna](#): > > The CPU has been disabled by the guest operating system. Power off or reset the virtual machine. You did not specify the version of ESXi being used, but it sounds a lot like [this vmxnet3 bug](https://kb.vmware.com/s/article/2151480). You could try the included workaround and see if it helps… Good luck! ---
**Author:** ![m.balkrkishna](https://avatars.discourse-cdn.com/v4/letter/m/df788c/32.png) [@m.balkrkishna](https://forums.rockylinux.org/u/m.balkrkishna)\ **Post date:** [March 7, 2024, 6:18pm UTC](https://forums.rockylinux.org/t/cpu-disabled-by-guest-operating-system-unwanted-reboot-issue-on-rocky-linux-9-2/13122/6 "2024-03-07T18:18:13Z")
@LinuxGuy1997 thanks , I will check on this and see if can apply the patch on the esxi. below is the esxi details : Client version:1.34.4 Client build number: 16668064 ESXi version: 7.0.1 ESXi build number: 16850804 ---
**Author:** ![m.balkrkishna](https://avatars.discourse-cdn.com/v4/letter/m/df788c/32.png) [@m.balkrkishna](https://forums.rockylinux.org/u/m.balkrkishna)\ **Post date:** [March 11, 2024, 2:29pm UTC](https://forums.rockylinux.org/t/cpu-disabled-by-guest-operating-system-unwanted-reboot-issue-on-rocky-linux-9-2/13122/7 "2024-03-11T14:29:38Z")
Update There was one suspect, a cron job to clean the page cache which was running below command. "sync ; echo 3 \> /proc/sys/vm/drop\_caches " Coincidently it was getting conflicting with the other cron job which eventually will be running at same time. For fixing the time of this drop cache cron has be changed to a non conflicting time. Even after this change, we are seeing an unwanted reboot happening. below logs can be seen in /var/log/syslog during the reboot, which indicates some SIGTERM, any way we can get to know the root case of it ? ```auto Mar 09 12:00:53 systemd-journald[329]: Received SIGTERM from PID 1 (systemd). Mar 09 12:00:59 systemd-journald[704]: Received client request to flush runtime journal. Mar 09 12:01:09 rsyslogd[942]: [origin software="rsyslogd" swVersion="8.2102.0-113.el9_2" x-pid="942" x-info="https://www.rsyslog.com"] start Mar 09 12:01:09 rsyslogd[942]: imjournal: journal files changed, reloading... [v8.2102.0-113.el9_2 try https://www.rsyslog.com/e/0] ``` ---
**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\ **Post date:** [March 12, 2024, 8:52am UTC](https://forums.rockylinux.org/t/cpu-disabled-by-guest-operating-system-unwanted-reboot-issue-on-rocky-linux-9-2/13122/8 "2024-03-12T08:52:02Z")
> [@m.balkrkishna](#): > > Update Just to check: have you applied `dnf up` or do you still have old content? * * * There is no “Rocky 9.2” and “Rocky 9.3”. There is only “Rocky 9” that is _currently_ based on RHEL 9.3 content. Rocky 9 will shift to RHEL 9.4 content soon™ after RHEL 9.4 is released. ---
**Author:** ![m.balkrkishna](https://avatars.discourse-cdn.com/v4/letter/m/df788c/32.png) [@m.balkrkishna](https://forums.rockylinux.org/u/m.balkrkishna)\ **Post date:** [March 13, 2024, 12:32pm UTC](https://forums.rockylinux.org/t/cpu-disabled-by-guest-operating-system-unwanted-reboot-issue-on-rocky-linux-9-2/13122/9 "2024-03-13T12:32:25Z")
Still having the old content. As for now, we will have to stick to below once. Rocky linux VM rocky-release-9.2-1.4.el9 on kernel-5.14.0-284.11.1.el9\_2.x86\_64 `On recent occurrence of issue, I found that there is one more cron which runs every 2 hrs and run below command.` > sync ; echo 3 \> /proc/sys/vm/drop\_caches this looks to be one of the suspect to me. This cron has been removed now. As the issue is not consistent (1 out of 10 VMs), not sure if this is actual fix. Any thoughts on this ? ---
**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\ **Post date:** [May 12, 2024, 12:33pm UTC](https://forums.rockylinux.org/t/cpu-disabled-by-guest-operating-system-unwanted-reboot-issue-on-rocky-linux-9-2/13122/10 "2024-05-12T12:33:09Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.