SRX devices may experience an automatic reboot and subsequently become stuck in a boot loop. This issue primarily affects virtualized SRX platforms and is related to TPM (Trusted Platform Module) communication failures.

Junos VM becomes unresponsive.

QEMU core dumps may be generated.

Device cannot be reached; operational commands fail until a cold reboot is performed.

Logs may show TPM-related Input/Output or timeout errors.

Command show system core-dumps can provide details of the generated core dumps.

Logs may include entries such as:

%SYSLOG-5-SYSTEM_ABNORMAL_SHUTDOWN: System abnormally shut down eventd[22904]: SYSTEM_ABNORMAL_SHUTDOWN: System abnormally shut down eventd[22904]: SYSTEM_OPERATIONAL: System is operational

An issue with communication to the TPM (Trusted Platform Module) can trigger an internal QEMU (Quick Emulator) assertion. When this occurs:

• Junos OS becomes unresponsive.
• Traffic is interrupted.
• All services running through the affected SRX device are impacted.

The issue has been resolved in the following Junos versions:

• 23.4R2-S7
• 24.4R2-S2
• 25.2R2
• 25.4R1
• 25.4R2
• 26.1R1 and later