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
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
Hi all,
I would also suggest adding ploop support to openvz as part of the
roadmap since ploop will give real live migration to CT's, improve
backup performance, add snapshot feature, and add support for thin
provisioned CT's.
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
I would also suggest adding ploop support to openvz as part of the roadmap
since ploop will give real live migration to CT's, improve backup performance,
add snapshot feature, and add support for thin provisioned CT's.
I will not add that until it is 100% sure that OpenVZ team will support
I will not add that until it is 100% sure that OpenVZ team will support
that for
newer 3.X kernels.
Where do you get this information? I have not seeing anything on openvz.org
indicating ploop should not be supported on 3.1x kernels.
There is no information so far (that is why I do not
