Hi Alireza
You can create similar compute offering with host tags (of hosts in a
cluster to start VM) and change the compute offering for the VM to the new
one.
- Suresh
On Tue, Apr 23, 2019 at 2:49 PM Alireza Eskandari
wrote:
> Hi guys,
> I face with a problem in old migration of VMs between 2 cluster.
> If you stop a VM in 1st cluster, then you try to start it on a host in 2nd
> cluster, you will get "The specified key, name, or identifier already
> exists." error from VMWare.
> I have opened an issue in CloudStack github about it:
> https://github.com/apache/cloudstack/issues/3285
> I'm looking for a workaround. How can I prevent CloudStack to start VM in
> other clusters?
> Regards
>
