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.

Beginne mit dem XenServer Integration-Pfad, der beim Stoppen und Starten der VM verwendet wird, und reproduziere die UUID-Änderung auf einer über XCP-ng verwalteten Windows-VM. Verwende `wmic bios get serialnumber` vor und nach dem Zyklus; als erledigt gilt die Aufgabe, wenn die SMBIOS-UUID konstant bleibt und der Veeam Agent die VM weiterhin als dieselbe Maschine erkennt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.