The real problem is that every time I stop a VM, that VM is destroyed, and is created again when I start it, If I do the same thing via the XCP-ng, it works as expected, XCP stops and starts the VM properly, why is cloudstack destroying and recreating? I already opened an issue on github, but this behavior is not correct I think. This destroy and recreate everytime you stop/start a machine, change the UUID.
On Wed, Nov 22, 2023 at 6:05 PM Nux <n...@li.nux.ro> wrote: > Hi, > > It seems like a serious enough problem , I'd open a guthyb issue > explaining it and hopefully something can be done about it. > > > > On 22 November 2023 17:46:04 CET, Francisco Arencibia Quesada < > arencibia.franci...@gmail.com> wrote: > >Hello everyone! > > > >I'm really hoping to find an answer here, since I can't find anything on > >the internet regarding my problem. So, here's the deal: > > > >I'm using cloudstack as an orchestrator for XenServer. I noticed that each > >time a Windows VM shuts down, when it starts up again it has a different > >SMBIOS UUID. This causes problems for a specific application, Veeam Agent > >for Windows. Veeam Agent recognises the machine from its SMBIOS UUID only, > >so each time an SMBIOS UUID is reset, Veeam Agents think its a different > >machine and delete the entire backup chain, then creating a new one. Is > >there any way I can make my VMs SMBIOS UUID persistent/permanent/sticky? > >Any help would be appreciated. > > > >Thanks :) > > > >-- > >*Francisco Arencibia Quesada.* > >*DevOps Engineer* > -- *Francisco Arencibia Quesada.* *DevOps Engineer*
