#1 Global Leader in Data Resilience

Fixing Restore Failures Due to QEMU Machine Version

KB ID: 4773
Product: Veeam Backup & Replication | 12.3.2
Published: 2025-09-23
Last Modified: 2025-09-29
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

When attempting to restore a VM with a QEMU version lower than 10 and disks in QCOW2 format to a Proxmox VE v9 node, the following error occurs:

16.09.2025 10:25:28 Error    Linux-8.0 : Failed to reach the hypervisor. Error output: storage for 'local-LVM:vm-42-disk-1.qcow2' is configured for snapshots as a volume chain - this requires QEMU machine version >= 10.0. See https://pve.proxmox.com/wiki/QEMU_Machine_Version_Upgrade
Restore Session window showing a failed restore for "Linux-8.0." An error message reads: "Failed to reach the hypervisor. Error output: storage for 'local-LV...'" Other steps are marked as successful or completed.

Cause

This occurs when the restore destination storage has the setting "Allow Snapshots as Volume-Chain" enabled, causing the storage to require VMs on that storage to be QEMU version 10.
Edit LVM settings window showing "Allow Snapshots as Volume-Chain" is checked.

Solution

To workaround this issue, consider one of the following options:

  • Restore to another storage that has Allow Snapshots as Volume-Chain disabled.
  • Restore the disk as RAW.
    • After the restore, if needed, convert the disk back to QCOW format manually inside Proxmox.
      See https://pve.proxmox.com/wiki/Storage_Migration.
    • Consider your use case before choosing to restore to RAW format.
      While conversion to QCOW2 is possible using the Move Disk function, it may require updating the VM's QEMU version. This can cause compatibility issues. Therefore, disk format conversion should be done with caution.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.