Live migration issue

F

Freman

New Member
May 15, 2012
4
0
1
Hi,

I get this strange issue when trying to livemigrate a server.

Aug 25 09:34:29 starting migration of VM 100 to node 'pvenode02' (10.0.1.101)
Aug 25 09:34:29 copying disk images
Aug 25 09:34:29 starting VM 100 on remote node 'pvenode02'
Aug 25 09:34:30 starting ssh migration tunnel
Aug 25 09:34:31 starting online/live migration on localhost:60000
Aug 25 09:34:31 migrate_set_speed: 8589934592
Aug 25 09:34:31 migrate_set_downtime: 0.1
Aug 25 09:34:33 migration status: active (transferred 104235657, remaining 4909830144), total 8598740992)
Aug 25 09:34:35 migration status: active (transferred 196525706, remaining 215404544), total 8598740992)
Aug 25 09:34:37 migration status: active (transferred 328291303, remaining 49512448), total 8598740992)
Aug 25 09:34:37 migration status: active (transferred 348803143, remaining 29696000), total 8598740992)
Aug 25 09:34:37 migration status: active (transferred 370128097, remaining 9846784), total 8598740992)
Aug 25 09:34:38 migration speed: 1170.29 MB/s - downtime 21 ms
Aug 25 09:34:38 migration status: completed
Aug 25 09:34:38 ERROR: VM 100 not running
Aug 25 09:34:38 ERROR: command '/usr/bin/ssh -o 'BatchMode=yes' root@10.0.1.101 qm resume 100 --skiplock' failed: exit code 2
Aug 25 09:34:41 ERROR: migration finished with problems (duration 00:00:12)
TASK ERROR: migration problems

The issue here is the resume.it transfers OK but it wont pickup automatically. I have to start the VM manually after migration
 
Two identical nods.
No special CPU setting. I use default CP

root@pvenode02:~# pveversion -v
proxmox-ve-2.6.32: 3.2-126 (running kernel: 2.6.32-29-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-29-pve: 2.6.32-126
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
root@pvenode02:~#

root@pvenode03:~# pveversion -v
proxmox-ve-2.6.32: 3.2-126 (running kernel: 2.6.32-29-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-29-pve: 2.6.32-126
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
root@pvenode03:~#
 
You must log in or register to reply here.
Top Bottom