Gary,

There are some global settings you can enable/disable to prevent certain VM
(and storage) movements.

migrate.vm.across.clusters - indicates whether the VM can be migrated to
different cluster if no host is found in same cluster
enable.storage.migration - Enable/disable storage migration across primary
storage
enable.ha.storage.migration - Enable/disable storage migration across
primary storage during HA

-Si

On Tue, May 16, 2023 at 8:13 AM Gary Dixon <gary.di...@quadris.co.uk.invalid>
wrote:

> Hi everyone
>
>
>
> Other than disabling a Pod – is there a way to prevent live migration of
> VM’s between Pods in ACS ?
>
>
>
> We are on version 4.15.2 with Ubuntu 20.04 KVM hosts.  Each Pod contains a
> single cluster of Homogenous hosts – however there are only slight
> differences between the CPU’s on the physical hosts in each Cluster. We
> have the guest.cpu.mode set to host-passthrough but have noticed serious
> issues when a VM is live migrated between specific Pods (usually if a VM is
> started on a cluster with the slightly better CPU’s and then live migrated
> to an older Pod)
>
>
>
> We have tried setting the guest.cpu.mode to host-passthrough with specific
> CPU features using the “guest.cpu.features=” and then setting all of the
> host’s CPU flags shown from the output of the lscpu command in a space
> separated list as instructed from ACS documentation – but we then are
> unable to even start a VM – insufficient resources error, - if we remove
> the guest.cpu.features from the agent.properties – then we can start a VM
> again.
>
>
>
> It would be good if we had an option or a setting to just not allow live
> migration of VM’s between pods and therefore can only perform a ‘cold’
> migration if we wish to move a VM to another Pod.
>
>
>
> Any thoughts on this ?
>
>
>
> BR
>
>
>
> Gary
>
>
>
>
> Gary Dixon​
> Senior Technical Consultant
> T:  +44 161 537 4990
> E:  *v* <+44%207989717661>ms@quadris‑support.com
> W: www.quadris.co.uk
> The information contained in this e-mail from Quadris may be confidential
> and privileged for the private use of the named recipient.  The contents of
> this e-mail may not necessarily represent the official views of Quadris.
> If you have received this information in error you must not copy,
> distribute or take any action or reliance on its contents.  Please destroy
> any hard copies and delete this message.
>

Reply via email to