Can you configure a *new* cluster and migrate the engine to that? You
should be able to import your existing storage domains and logical
networks under the new cluster which can then be used as a migration
target for any running VMs. Your other option would be to build a new
engine using 4.0 and then restore your 3.6 backup.
On 03/07/2017 04:32 PM, Chris Adams wrote:
Once upon a time, Chris Adams <cma(a)cmadams.net> said:
> However, now I'm back into the catch-22 of 3.6.7+hosted engine: the
> cluster compatibility level can't be raised while there's a running VM,
> and that includes the hosted engine.
I'm still stuck on this - anybody have any solution? Because of this, I
can't upgrade my cluster.