Proxmox 3.0 & migration online

[ded_Pihto]

Configuration:
2 proxmox at cluster mode P1 & P2. Storage for virtual disk - NFS.

VM: qm config 220
bootdisk: ide0
cores: 1
ide0: nfs:220/vm-220-disk-1.qcow2,format=qcow2,size=32G
memory: 512
name: 123
net0: rtl8139=BE:72:1C:02:6F:8B,bridge=vmbr0
ostype: wxp
scsihw: virtio-scsi-pci
sockets: 1

I want migrate vm#220 from P1 to P2 online, VM status - working
and result - parsing(!!!) error

> qm migrate 220 P2 --online
Jul 11 10:01:05 starting migration of VM 220 to node 'P2' (192.168.1.2)
Jul 11 10:01:05 copying disk images
Jul 11 10:01:05 starting VM 220 on remote node 'P2'
Jul 11 10:01:10 Unknown option: machine
Jul 11 10:01:10 400 unable to parse option
Jul 11 10:01:10 qm start <vmid> [OPTIONS]
Jul 11 10:01:10 ERROR: online migrate failure - command '/usr/bin/ssh -o 'BatchMode=yes' root@192.168.1.2 qm start 220 --stateuri tcp --skiplock --migratedfrom P2 --machine pc-i440fx-1.4' failed: exit code 9
Jul 11 10:01:10 aborting phase 2 - cleanup resources
Jul 11 10:01:10 migrate_cancel
Jul 11 10:01:14 ERROR: migration finished with problems (duration 00:00:13)
migration problems

Migration ok when VM status are stopped

 

[vargabesz]

I have the same issue!
It happens when I try to migrate a machine from a host running this version:

pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
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.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-20
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1


to this version:
pve-manager: 3.0-20 (pve-manager/3.0/0428106c)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
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.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-15
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-6
vncterm: 1.1-3
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-12
ksm-control-daemon: 1.1-1


I know I should by running the same versions on all hosts, but I need to do a maintenance on the newer version server before I can upgrade the rest! I need to migrate the guests off there first..

Where can I remove that option from the script? (--machine pc-i440fx-1.4)

 

[spirit]

seem to be a bug, the --machine pc-i440fx-1.4 has been introduce for snapshot rollback only, and not migration.

Can you post your vm config file ?

"/etc/pve/qemu-server/<VMID>.conf"

 

[dietmar]

seem to be a bug, the --machine pc-i440fx-1.4 has been introduce for snapshot rollback only, and not migration.

Really? I thought we use it for migration to make sure we do not change the machine.

 

[dietmar]

I know I should by running the same versions on all hosts, but I need to do a maintenance on the newer version server before I can upgrade the rest! I need to migrate the guests off there first..

You simply can't migrate a newer version to an older one.

 

[dietmar]

Well, you can do an offline migration.

 

[ded_Pihto]

Thank's. I solved this trouble too - aptitude update && aptitude fuul-upgrade on all host.
IMHO Proxmox documentation must have text some as " You must migrate from\to same version of Proxmox " )))

P.S. May be I can't edit\change internal script ( same as "qm migrate" )..

 

[spirit]

Really? I thought we use it for migration to make sure we do not change the machine.

Oh, yes, you are right, I miss that. It's works fine on my cluster.

 

[vargabesz]

Okay, thank you for replying!