Still migration problems

Antonino89

Member
Jul 13, 2017
76
1
6
35
Hi Guys,

i'm still trying to figure out why i can't migrate CT from one server to another.

VMs migrate perfectly:

2017-08-23 11:28:53 starting migration of VM 100 to node 'Server3' (192.168.100.13)
2017-08-23 11:28:53 copying disk images
2017-08-23 11:28:53 starting VM 100 on remote node 'Server3'
2017-08-23 11:28:56 start remote tunnel
2017-08-23 11:28:57 starting online/live migration on unix:/run/qemu-server/100.migrate
2017-08-23 11:28:57 migrate_set_speed: 8589934592
2017-08-23 11:28:57 migrate_set_downtime: 0.1
2017-08-23 11:28:57 set migration_caps
2017-08-23 11:28:57 set cachesize: 53687091
2017-08-23 11:28:57 start migrate command to unix:/run/qemu-server/100.migrate
2017-08-23 11:28:59 migration status: active (transferred 472881757, remaining 64798720), total 554508288)
2017-08-23 11:28:59 migration xbzrle cachesize: 33554432 transferred 0 pages 0 cachemiss 0 overflow 0
2017-08-23 11:29:01 migration speed: 128.00 MB/s - downtime 29 ms
2017-08-23 11:29:01 migration status: completed
2017-08-23 11:29:02 # /usr/bin/ssh -o 'BatchMode=yes' -o 'HostKeyAlias=Server3' root@192.168.100.13 pvesr set-state 100 \''{}'\'
2017-08-23 11:29:06 migration finished successfully (duration 00:00:13)
TASK OK


But containers do not:

Task viewer: CT 103 - Migrate

OutputStatus

Stop
2017-08-23 11:30:19 shutdown CT 103
2017-08-23 11:30:19 # lxc-stop -n 103 --timeout 180
2017-08-23 11:30:27 # lxc-wait -n 103 -t 5 -s STOPPED
2017-08-23 11:30:29 starting migration of CT 103 to node 'Server2' (192.168.100.12)
2017-08-23 11:30:29 volume 'LVM1:vm-103-disk-1' is on shared storage 'LVM1'
2017-08-23 11:30:29 # /usr/bin/ssh -o 'BatchMode=yes' -o 'HostKeyAlias=Server2' root@192.168.100.12 pvesr set-state 103 \''{}'\'
2017-08-23 11:30:30 start final cleanup
2017-08-23 11:30:31 start container on target node
2017-08-23 11:30:31 # /usr/bin/ssh -o 'BatchMode=yes' -o 'HostKeyAlias=Server2' root@192.168.100.12 pct start 103
2017-08-23 11:30:37 command 'systemctl start lxc@103' failed: exit code 1
2017-08-23 11:30:37 Job for lxc@103.service failed because the control process exited with error code.
2017-08-23 11:30:37 See "systemctl status lxc@103.service" and "journalctl -xe" for details.
2017-08-23 11:30:37 ERROR: command '/usr/bin/ssh -o 'BatchMode=yes' -o 'HostKeyAlias=Server2' root@192.168.100.12 pct start 103' failed: exit code 255
2017-08-23 11:30:37 ERROR: migration finished with problems (duration 00:00:19)
TASK ERROR: migration problems

root@Server2:~# lxc-start -n 103 -F -l DEBUG -o /tmp/lxc-103.log

can't activate LV '/dev/lvm1/vm-103-disk-1': Failed to find logical volume "lvm1/vm-103-disk-1"

lxc-start: conf.c: run_buffer: 464 Script exited with status 5.

lxc-start: start.c: lxc_init: 450 Failed to run lxc.hook.pre-start for container "103".

lxc-start: start.c: __lxc_start: 1337 Failed to initialize container "103".

lxc-start: tools/lxc_start.c: main: 366 The container failed to start.

lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.

I also tried to check differences between CTs config files, but i can't see any significant things:

root@Server1:/var/lib/lxc# diff ./102/config ./103/config

2c2

< lxc.include = /usr/share/lxc/config/ubuntu.common.conf

---

> lxc.include = /usr/share/lxc/config/debian.common.conf

6c6

< lxc.utsname = UbuntuCT

---

> lxc.utsname = DebianCT

10c10

< lxc.rootfs = /var/lib/lxc/102/rootfs

---

> lxc.rootfs = /var/lib/lxc/103/rootfs

12,13c12,13

< lxc.network.veth.pair = veth102i0

< lxc.network.hwaddr = 1A:F4:98:F7:4C:C7

---

> lxc.network.veth.pair = veth103i0

> lxc.network.hwaddr = 3A:B0:22:D8:28:AE

15c15

< lxc.cgroup.cpuset.cpus = 1

---

> lxc.cgroup.cpuset.cpus = 0



Any idea, please? :)
 
2017-08-23 11:30:29 volume 'LVM1:vm-103-disk-1' is on shared storage 'LVM1'
Any idea, please? :)

You marked your (local?) LVM1 storage as shared, thus Proxmox VE doesn't triggers a offline storage migration – which makes sense for storages that are really shared.
Tick of the shared flag in Datacenter -> Storage for the LVM1 one and please try again :)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!