@olivierlambert The idea is to block the VM and exclusion disks even by root itself, and make it possible only via command line in the console. That's why I started the post by mentioning the command...
We dream of the day when MFA authentication will be required to delete a VM...

@DustinB Thanks for the quick answer, but the problem is "how to protect the DISKS from accidental exclusion". The VM protection is ok, but if you go to the disks tab you can delete de disk, that is worst that delete a VM...

Hello everyone!

We want to protect some VMs and associated disks from being deleted (acidental or proposal). The command below protects the VM from being deleted but not the associated disks:

xe vm-param-set uuid=<UUID_OF_THE_VM> blocked-operations:destroy=true

What parameter is missing to be included?

Thanks!!

@olivierlambert Thanks for the quick response, Oliver. We will update both hosts soon and test the export/import again. We'll be maintain you informed.

Hello!
We have 02 XCPs-NG 8.3 Servers separated, not in a pool.
We created a VM in XCP-1, then exported the VM with xe vm-export, and when we import the VM to the other host with xe vm-import we get the error "The import failed because this export has been created by a different (incompatible) product version".
There's updates to apply in both servers, maybe this is the problem?
Thanks!

XCP-1 Build Date Feb 11, 2025 3:05:31 PM (rejecting the import)
Version: XCP-ng 8.3
DBV: 0.0.1

XCP-2 Build Date May 13, 2025 8:56:20 AM (xe vm-export)
Version: XCP-ng 8.3
DBV: 0.0.1

@astrugatch we did the opposite:

1. Converted the VM from Vmware with OVFTool in .OVA format
2. Converted the .OVA file in .OVF file
3. Then.. imported the OVF file in XCP with XCP-NG Center

@astrugatch @olivierlambert We recently converted a VM from Vmware with OVFtool. Did you tried to re-run the ovftool command to convert OVA in OVF? I get the same error as you and solved when we converted the OVA in OVF, then imported without any error with XCP-NG Center.