[pve-devel] [PATCH 1/4] Add CT suspend/resume support via PVE2 API

Dietmar Maurer dietmar at proxmox.com
Sun Oct 5 14:23:04 CEST 2014


I don't really understand what you talk about. If you suspend to disk, you also need/should transfer that state when you migrate the VM. This is unrelated to online migration.
Sure, this can fails, but that should be handled by vzctl chkpnt/restore internally.

> I know I'd like to try it.  The potential issue is when migrating between nodes
> with different kernel versions/modules/configurations.  It would probably be
> useful to detect those cases (as best we can), and either issue a warning, or
> automatically switch to an offline migration, shutting down and starting up
> before and after migration, respectively.  If such detection isn't feasible, perhaps
> online migrations of CTs are something we shouldn't worry about.  We can only
> control the environment to a certain extent.
> On the other hand, a failed online migration ought to lead sysadmins to attempt
> offline migration before giving up, so maybe we just let the migration fail and let
> the sysadmin adapt their course of action accordingly.  Just some thoughts on it.


More information about the pve-devel mailing list