LXC and Live Migration

[starnetwork]

Hi,
there is any way or configuration that LXC can do Live Migration?

 

[starnetwork]

here it's look like it's supported: https://stgraber.org/2016/04/25/lxd-2-0-live-migration-912/

 

[wolfgang]

Hi,

the link you post use criu.
Criu only work if you have no network, socket,...
In other words criu is not working for a normal container like we provide.

 

[starnetwork]

Thanks wolfgang for that info,
any other Idea / Solution in the foreseeable future?

 

[tom]

Thanks wolfgang for that info,
any other Idea / Solution in the foreseeable future?

Use "restart mode", if you really need live migration, use QEMU.

 

[starnetwork]

the restart mode checkbox not enabled to me, what should I change so it will work?

 

[wolfgang]

Can you send the output of

pveversion -v

 

[starnetwork]

sure:

root@server1:~# pveversion -v
proxmox-ve: 5.0-16 (running kernel: 4.10.17-1-pve)
pve-manager: 5.0-23 (running version: 5.0-23/af4267bf)
pve-kernel-4.10.11-1-pve: 4.10.11-9
pve-kernel-4.10.17-1-pve: 4.10.17-16
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-14
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-5
libpve-storage-perl: 5.0-12
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-2
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve2
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

 

[wolfgang]

When a Container is running you can check the checkbox "Restart Mode" which you see when you see in the migration Window.
Then the CT will shutdown -> then migrate -> on the target node it will automatically started.

 

[starnetwork]

I want minimum downtime in migrate, so this is not the optimal solution
no any way to migrate -> shutdown -> sync delta data -> start on target node?

 

[tom]

I want minimum downtime in migrate, so this is not the optimal solution
no any way to migrate -> shutdown -> sync delta data -> start on target node?

This works if you use the new replication and ZFS, see the demo, migration of a container (Migration starts on min 1:30):

https://www.proxmox.com/en/training/video-tutorials/item/what-s-new-in-proxmox-ve-5-0