The issue reported involves virtual machines within a VNF that are facing cyclic reboot issues.
7.0 U3t
7.0 U3s
The logs show a series of "hard" and "soft" CPU resets during the reboot process. The "hard" CPU reset is a hardware signal triggering a reset, while the "soft" CPU reset is software-initiated, typically to reinitialize the system’s CPU cores. These resets are common during system-level reboots and don’t necessarily point to any specific error at the ESXi level.
VMware.log
vmware.log:####-##-##T##:##:##.###Z In(05) vcpu-0 - Unknown int 10h func 0x0000
vmware.log:####-##-##T##:##:##.###Z In(05) vcpu-0 - Unknown int 10h func 0x0000
vmware.log:####-##-##T##:##:##.###Z In(05) vcpu-0 - Unknown int 10h func 0x0000
####-##-##T##:##:##.###Z In(05) vcpu-0 - CPU reset: hard (mode Emulation)
####-##-##T##:##:##.###Z In(05) vcpu-2 - CPU reset: hard (mode Emulation)
####-##-##T##:##:##.###Z In(05) vcpu-1 - CPU reset: hard (mode Emulation)
####-##-##T##:##:##.###Z In(05) vcpu-1 - CPU reset: soft (mode Emulation)
####-##-##T##:##:##.###Z In(05) vcpu-2 - CPU reset: soft (mode Emulation)
####-##-##T##:##:##.###Z In(05) vcpu-3 - CPU reset: soft (mode Emulation)
It’s recommended to reach out to the vendor of the guest OS to further investigate the issue. The logs indicate "CPU reset: hard (mode Emulation)" and "CPU reset: soft (mode Emulation)", which may suggest an issue related to OS-level or hardware emulation. These types of resets are typically associated with deeper issues within the OS or the underlying hardware emulation, which should be addressed by the OS vendor for a more thorough investigation.
Why do we see a sequence of "CPU reset: hard" followed by "CPU reset: soft" in the vmware.log when a VM performs a soft reboot (e.g. via init 6)?