← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Veeam Software Appliance VMs Fail to Boot on AMD EPYC Processors Due to Kernel Panic

🔄 Updated 23h ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Veeam Software Appliance VMs fail to boot on some AMD EPYC processors.
  • Issue caused by Linux kernel's FIPS-mode jitterentropy test failure.
  • Affects Veeam Software Appliance version 13.1 and newer.
  • Mitigation involves redeploying or manual update management.

Veeam Software Appliance Boot Failures Identified

Veeam has alerted customers about an issue causing its Software Appliance virtual machines (VMs) to fail booting on hosts equipped with specific AMD EPYC processors. The Software Appliance VMs are pre-configured Linux-based systems designed to run Veeam Backup & Replication without manual dependency installation.

Root Cause: FIPS Mode Jitterentropy Test

The problem occurs because the underlying Linux kernel in the Veeam Software Appliance performs integrated health and cryptographic checks, including jitterentropy health tests in FIPS mode, during the early boot process. On certain AMD EPYC processors, such as the 7262, 7302, and 7F72, this test intermittently fails, leading to a kernel panic and preventing the VM from booting. This issue is inherent to the Linux kernel version used by the appliance.

Affected Versions and Error Messages

This boot failure impacts Veeam Software Appliance version 13.1 and all subsequent versions. Users encountering the problem will see a specific kernel panic error message: "Kernel panic - not syncing: jitterentropy: Initialization failed with host not compliant with requirements: 9".

Mitigation Strategies for Administrators

Veeam has provided several mitigation options. The primary recommendation is to redeploy the affected appliance to a Linux host utilizing a different processor type. If redeployment is not feasible, administrators are advised to disable automatic updates for the appliance. Instead, updates should be installed manually, with close monitoring during the reboot process. If a kernel panic occurs, the virtual machine must be powered off and then powered on again, as a guest operating system restart will not resolve the issue. Once successfully booted, the appliance is expected to operate without further errors.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 07

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Veeam has issued a warning regarding boot failures in its Software Appliance virtual machines when running on hosts with certain AMD EPYC processors. The issue stems from the Linux kernel's FIPS-mode jitterentropy health test failing during early boot, causing a kernel panic and preventing the VM from starting. This impacts Veeam Software Appliance version 13.1 and later, requiring administrators to either redeploy to different hardware or manually manage updates and reboots.