Online migration failure - no useful info?

D

dswartz

Renowned Member
Dec 13, 2010
286
9
83
I have a running ubuntu 12.04 guest on proxmox2. I am trying to migrate it to proxmox1. It has no local resources or anything. I fire up the migrate (same results from cli as gui) and see this:

root@proxmox2:/var/log# qm migrate 100 proxmox1 --online
Apr 04 09:49:12 starting migration of VM 100 to node 'proxmox1' (10.0.0.8)
Apr 04 09:49:12 copying disk images
Apr 04 09:49:12 starting VM 100 on remote node 'proxmox1'
Apr 04 09:49:13 starting migration tunnel
Apr 04 09:49:13 starting online/live migration on port 60000
Apr 04 09:49:13 migrate_set_speed: 8589934592
Apr 04 09:49:13 migrate_set_downtime: 0.1
Apr 04 09:49:15 ERROR: online migrate failure - aborting
Apr 04 09:49:15 aborting phase 2 - cleanup resources
Apr 04 09:49:15 migrate_cancel
Apr 04 09:49:16 ERROR: migration finished with problems (duration 00:00:04)
migration problems

Any ideas where I should start looking for info? /var/log/syslog and /var/log/daemon have nothing helpful :(

p.s. I can migrate other guests just fine...
 
pls provide more info, e.g.

- qm config 100
- pveversion -v from both hosts
 
On proxmox2:

root@proxmox2:~# qm config 100
boot: c
bootdisk: virtio0
cores: 1
memory: 4096
name: hyper1
net0: virtio=AE:5B:11:94:32:F2,bridge=vmbr0
ostype: l26
sockets: 1
virtio0: San:100/vm-100-disk-1.raw,size=32G


root@proxmox2:~# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-93
pve-kernel-2.6.32-19-pve: 2.6.32-93
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1


On proxmox1:

pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-93
pve-kernel-2.6.32-19-pve: 2.6.32-93
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1
 
Nothing useful, I'm afraid. I ended up deleting the "sick" VM. Very odd... Be nice to know where (if anywhere) useful reason(s) for the failure were logged or some kind of verbose migration mode. Oh well...
 
You must log in or register to reply here.
Top Bottom