SMBIOS UUID needs to be sticky when stopping and starting a VM

ISSUE TYPE

Bug Report
COMPONENT NAME

XenServer Integration

CLOUDSTACK VERSION

4.18.1.0

CONFIGURATION

VMs on XCP-ng

OS / ENVIRONMENT

CloudStack on Linux, managing XCP-ng hosts

SUMMARY

When using CloudStack with XCP-ng as the orchestrator, each time a Windows VM shuts down, it receives a different SMBIOS UUID. This causes issues with Veeam Agent for Windows, as it recognizes machines based on their SMBIOS UUID. As a result, each time the UUID changes, Veeam Agent treats it as a new machine and deletes the entire backup chain, creating a new one. I'm seeking a solution to make the VMs' SMBIOS UUIDs persistent or permanent.

STEPS TO REPRODUCE

Set up a Windows VM in CloudStack using XenServer/XCP-ng.
Type in cmd: wmic bios get serialnumber
Observe the SMBIOS UUID change after each shutdown and start-up of the VM.

EXPECTED RESULTS

The SMBIOS UUID of the Windows VMs should remain constant when stopping and starting a machine.

ACTUAL RESULTS

Each stop and start of the VM results in a change of the SMBIOS UUID, leading to issues with Veeam Agent recognizing the VM as the same machine.

从 VM 停止和启动期间使用的 XenServer Integration 路径开始，并在通过 XCP-ng 管理的 Windows VM 上复现 UUID 变化。在该周期前后使用 `wmic bios get serialnumber`；当 SMBIOS UUID 保持不变且 Veeam Agent 继续将该 VM 识别为同一台机器时，即表示完成。

由索引模型根据 Issue 内容生成。