vzmigrate/pvectl migrate openvz containers

[pjotter]

Hi,

When using OpenVZ containers, I seem to be unable to migrate a container from one HWN to another, neither using vzmigrate (config file already there), nor pvectl migrate (no shared storage).
This seems to be a severe limitation. vzmigrate in "pure" state has no trouble migrating into blue skies, even live, without any form of shared storage. A working SSH connection and a similar architecture is all it takes.

How can I (live) migrate containers without shared storage using Proxmox?

 

[tom]

Container live migration work out of box here, using local storage and also on NFS.

HowTo: just click on the container and select 'migrate', tick the online flag.

If it does not work on your side, post details and error logs.

 

[drott]

Container live migration work out of box here, using local storage and also on NFS.

HowTo: just click on the container and select 'migrate', tick the online flag.

If it does not work on your side, post details and error logs.

I think what is being asking is an earlier question I had asked about migration between hardware nodes with no shared storage, no cluster just a shared network connection. It cannot be done since there is no provision in the giu to add ip address and ssh info if needed.

Command vzmigrate works fine btw HN. If all else fails just make the backup to local storage the cts are on. Either ssh or scp file to the other hn. Then use the force option to restore over an existing ct on the other hn. I had a joomla ct that was misbehaving after upgrade to 2.3 but that was not told to any one for about three weeks after all boxes were updated. Couple weeks later the most current release came outcame out. To test bosted the ct back over via scp to parent and a restore and it seems ok.

 

[pjotter]

@tom
There is no error log, just the messages I told, followed by a refusal to act. From vzmigrate that was to be expected, from pvectl migrate this seems weird.

@drott
Partly, yes. I can trigger imports from OpenVZ to Proxmox by initiating a vzmigrate on the OpenVZ HWN. The reverse seems to be impossible for the given reasons.

On further investigation, this is also the case between HWN's in a single Proxmox cluster. The reason for this seems to be storage defined to be used explicitly for a single HWN. (Which IMHO is the very definition of "local storage"). When I remove such storage definitions and replace them with a single unshared map, identical for all HWN's, things work as expected.

Which implicates that migrating from a Proxmox HWN to a non Proxmox OpenVZ HWN will never work, neither will relocation from one "one node storage" to another "one node storage".

I don't understand the reason for such a limitation. Can someone enlighten, confirm and/or refute this?