arencibiafrancisco opened a new issue, #8261:
URL: https://github.com/apache/cloudstack/issues/8261

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   ISSUE TYPE
   <!-- Pick one below and delete the rest -->
   Bug Report
   COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   XenServer Integration
   
   CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   4.18.1.0
   
   CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   VMs on XCP-ng
   
   OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   CloudStack on Linux, managing XCP-ng hosts
   
   SUMMARY
   <!-- Explain the problem/feature briefly -->
   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
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal 
test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   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.
   <!-- Paste example playbooks or commands between quotes below -->
   EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   The SMBIOS UUID of the Windows VMs should remain constant when stopping and 
starting a machine.
   
   ACTUAL RESULTS
   <!-- What actually happened? -->
   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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to