RHEL guest running on VMware Hypervisor rebooted suddenly.

Issue

• RHEL guest running on VMware rebooted. Looking at /var/log/messsages file, it looks like the system was gracefully
  rebooted.

Jan 16 07:26:07 server1 systemd[1]: Stopped LVM event activation on device 8:2.
Jan 16 07:26:07 server1 systemd[1]: Removed slice system-lvm2\x2dpvscan.slice.
Jan 16 07:26:07 server1 itmcmd[1430467]: itmcmd agent: Sourcing db2profile for user eimdlp1
Jan 16 07:26:07 server1 systemd[1]: db2fmcd.service: Succeeded.
Jan 16 07:26:07 server1 systemd[1]: Stopped DB2 v11.1.4.6.
Jan 16 07:26:07 server1 itmcmd[1430887]: Processing. Please wait...
Jan 16 07:26:07 server1 itmcmd[1430947]: Processing. Please wait...
Jan 16 07:26:08 server1 itmcmd[1431014]: Stopping Watchdog process...
Jan 16 07:26:08 server1 itmcmd[1431120]: Processing. Please wait...
Jan 16 07:26:09 server1 systemd[1]: dracut-shutdown.service: Succeeded.
Jan 16 07:26:09 server1 systemd[1]: Stopped Restore /run/initramfs on shutdown.
Jan 16 07:26:09 server1 itmcmd[1430937]: Stopping Monitoring Agent for GSMA Linux OS ...
Jan 16 07:26:10 server1 itmcmd[1431172]: Stopping IBM Tivoli Composite Application Manager Agent for DB2 ...
Jan 16 07:26:12 server1 itmcmd[1431923]: Watchdog process was stopped.
Jan 16 07:26:13 server1 itmcmd[1431940]: Stopping Monitoring Agent for Linux OS ...
Jan 16 07:26:14 server1 itmcmd[1431172]: Product IBM Tivoli Composite Application Manager Agent for DB2 was stopped gracefully.
Jan 16 07:26:14 server1 itmcmd[1431172]: Agent stopped...
Jan 16 07:26:14 server1 systemd[1]: ITMAgents1.ud.eimdlp1.service: Succeeded.
Jan 16 07:26:14 server1 systemd[1]: Stopped IBM Tivoli Monitoring for "/opt/IBM/ITM".
Jan 16 07:26:23 server1 kernel: Command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-4.18.0-513.9.1.el8_9.x86_64 root=/dev/mapper/rootvg-rootlv ro crashkernel=auto resume=/dev/mapper/rootvg-paging00 rd.lvm.lv=rootv
g/rootlv rd.lvm.lv=rootvg/paging00 rd.lvm.lv=rootvg/usrlv net.ifnames=0 rhgb quiet

• Further investigation into VMware.log file available from SOSreport, observed below logs which indicate system
  reboot initiated from Hypervisor side.

• This must be an expected reboot performed manually from the vSphere Client since we observed below messages.

[2024-01-16T07:26:07.225Z] [ message] [vmsvc] [1368] Executing script for state change 'OS_Halt'.  <======
[2024-01-16T07:26:07.225Z] [ message] [powerops] [1368] Executing script: '/etc/vmware-tools/poweroff-vm-default' <===
[2024-01-16T07:26:07.396Z] [ message] [vmsvc] [1368] Script exit code: 0, success = 1  
[2024-01-16T07:26:07.396Z] [ message] [vmsvc] [1368] Initiating halt. <===