1/4
Sangfor aSV veeam plugin, common worker issue

LilPeek Lv1  Posted 2026-Sep-08 00:07

Hello,
we are currently running SCP and HCI with the latest patch for 6.11.3 so it is compatible with Veeam 13.1 and we can use the Sangfor aSV plugin recently released.

We correctly setup the plugin, we then tried deploying the common worker VMs, but the task fails with "failed to upload worker image".

On the scp side the "Create new image" gets stuck at 60%.
On the HCI the process ends successfully and a generic VirtualMachine is created which HCI tries to turn off, but just can't.

The vm stays in a kernel panic state.

Humayun Ahmed has solved this question and earned 20 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

https://helpcenter.veeam.com/doc ... html?utm&ver=13

our platform combination is supported: HCI 6.11.3, SCP 6.11.3 + col01, and Veeam 13.1.0.411+ / aSV plugin are the documented combination.

https://community.sangfor.com/fo ... p;tid=12265&utm
Is this answer helpful?
Humayun Ahmed Lv4  Posted 2026-Sep-08 18:24
  
https://helpcenter.veeam.com/doc ... html?utm&ver=13

our platform combination is supported: HCI 6.11.3, SCP 6.11.3 + col01, and Veeam 13.1.0.411+ / aSV plugin are the documented combination.

https://community.sangfor.com/fo ... p;tid=12265&utm
Prosi Lv4  Posted 2026-Sep-09 12:04
  
Hello,

Recommendation
- Delete the failed worker VM: Do not use a VM that has already experienced a *kernel panic*. Ensure no image upload or creation tasks are still running before retrying.
- Check the new image creation process in SCP: Note the task ID and error details/logs in SCP when the process stalls. Do not rely solely on the final status shown in HCI.
- Check worker image compatibility: SCP/HCI 6.11.3 + Veeam 13.1 worker image. A *kernel panic* indicates that the image was successfully created or partially transferred, but the deployed VM failed to boot normally.
- Check the configuration of the deployed VM.
- Do not simply increase the timeout value as the primary solution.

Symptoms:
SCP Create Image → stalls at 60% → HCI creates VM → VM experiences *kernel panic* → HCI fails to shut down → Veeam reports worker image upload failure (*Failed to upload worker image*).

Prioritize the worker image deployment process over the Veeam job configuration.
Newbie098773 Lv1  Posted 2026-Oct-10 01:51
  
Please check woker VM vCPU config, Veeam worker only support haswell type vCPU.

Also all worker develop must auto, do not power on or off worker manually.

I Can Help:

Change

Board Leaders

George ...

Weekly Sharers

George ...

Weekly Questioners