[pve-devel] Live migration should check for host compatibility?

[Daniel Hunsaker]

There's a discussion floating around on the list of a new CPU type which
includes all the CPU flags supported on all nodes in a cluster.  It's
similar to 'host', obviously, but would ensure that migrations would always
succeed by ensuring that only the flags available on *all* nodes are active
in the VCPU.

This won't solve the problem you're describing, and the values would need
to be renegotiated when new nodes join a cluster, potentially meaning
migrations to nodes added after VM start would fail similarly.  My reason
for mentioning this proposed option is to point out that it would also need
a way to handle this same scenario, and this approach makes as much sense
as any other.

On Sat, Mar 21, 2015, 00:03 Waschbüsch IT-Services GmbH <
service at waschbuesch.it> wrote:

> Hi all,
>
> Martin has kindly redirected me to the list as the appropriate place to
> ask / discuss this:
>
> I noticed that, even though a kvm guest is set to CPU type 'host', the
> live migration feature does not check for compatibility with the
> destination host.
> E.g. Moving from a Opteron 6366 to an Intel Xeon E5420 is going to cause
> the migrated VM to choke and die due to lots of CPU features no longer
> being there.
>
> That in itself is not surprising, but my suggestion would be to at least
> have a warning popup when choosing to migrate a kvm which is set to CPU
> type 'host'?
>
> Best,
>
> Martin
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20150321/c3716dbe/attachment.htm>