Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /homepages/13/d467848118/htdocs/templates/cleanout/vertex/responsive/responsive_mobile_menu.php on line 158
Simplest solution is to temporarily disable HA. Below command will globally disable HA for the cluster/pool. Run it from any of the hosts in the pool.
ha-cfg ha-disable
The root cause of your issue is likely related to using default settings. By default, (on a new installation), ALL VMs are treated as having HA enabled if HA is enabled for the pool. This behavior is controlled by the setting GLOBAL_VM_HA which is set to 1 on a new installtion. If you require more control over which VMs have HA enabled, you should set this to 0
ha-cfg set global_vm_ha 0
Once this has been set to 0, you will be required to individually set HA per VM using
ha-cfg set-vm-ha <vm-name> true|false
Alternatively, you can individually set HA per VM from within XenCEnter or XCP-ngcenter, assuming you have exposed the custom parameter "ha-lizard-enabled"