When i do online migrations with vz containers... everything works as expected.... files get copied over, but the vm is not online. When its done transferring its stopped.
How can i migrate vz while keeping them online, no downtime?
The only time Ive seen that happen is if you try to migrate VMs/CTs between nodes at different patch levels. If this applies to you - you should only try to migrate between identical nodes (ideally this would mean "fully updated in the stable branch")
a log file of any of these problematic migrations might help diagnose the problem (you can access logs of recent tasks by doubleclicking the task in the lower section of the proxmox GUI)
Feb 06 13:18:42 starting migration of CT 1050 to node 'proxmox2' (**.**.**.**) Feb 06 13:18:42 container is running - using online migration Feb 06 13:18:42 starting rsync phase 1 Feb 06 13:18:42 # /usr/bin/rsync -aHAX --delete --numeric-ids --sparse /var/lib/vz/private/1050 root@**.**.**.**:/var/lib/vz/private Feb 06 13:18:56 start live migration - suspending container Feb 06 13:18:56 dump container state Feb 06 13:18:57 copy dump file to target node Feb 06 13:18:57 starting rsync (2nd pass) Feb 06 13:18:57 # /usr/bin/rsync -aHAX --delete --numeric-ids /var/lib/vz/private/1050 root@**.**.**.**:/var/lib/vz/private Feb 06 13:18:59 dump 2nd level quota Feb 06 13:18:59 copy 2nd level quota to target node Feb 06 13:19:00 initialize container on remote node 'proxmox2' Feb 06 13:19:00 initializing remote quota Feb 06 13:19:01 turn on remote quota Feb 06 13:19:01 load 2nd level quota Feb 06 13:19:01 starting container on remote node 'proxmox2' Feb 06 13:19:01 restore container state Feb 06 13:19:06 removing container files on local node Feb 06 13:19:07 start final cleanup Feb 06 13:19:07 migration finished successfuly (duration 00:00:25) TASK OK
i would think if an automated process suspends the container... when its done should undo suspending of the vm? let me know if this help.
thanks for your help so far its greatly appreciated.
yes it normally does. However your log looks 100% identical to successful migrations over here. Aparently the unsuspending step merely does not output a line saying so.
Sadly that also means that the log does not help diagnose your problem.
I can tell you that your installation is not up to date, and Im afraid thats my last angle, maybe someone else has experienced this before?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
