Hi, Try from the command line:
qm migrate <vmid> <to node> --online Gerald On 2016-05-11 12:20 PM, Albert Dengg wrote:
hi, i just upgrade a pve cluster to pve 4.2 (enterprise repo), but i have the problem that i cannot do any online migrations since the upgrade. pve versions (this node has alerady rebooted after the upgrade): [dengg@pve1:~]> pveversion -v proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve) pve-manager: 4.2-2 (running version: 4.2-2/725d76f0) pve-kernel-2.6.32-37-pve: 2.6.32-150 pve-kernel-4.4.6-1-pve: 4.4.6-48 pve-kernel-4.2.6-1-pve: 4.2.6-36 pve-kernel-2.6.32-32-pve: 2.6.32-136 pve-kernel-2.6.32-43-pve: 2.6.32-166 pve-kernel-4.2.8-1-pve: 4.2.8-41 pve-kernel-2.6.32-39-pve: 2.6.32-157 pve-kernel-3.10.0-11-pve: 3.10.0-36 pve-kernel-2.6.32-34-pve: 2.6.32-140 pve-kernel-4.2.2-1-pve: 4.2.2-16 pve-kernel-2.6.32-40-pve: 2.6.32-160 pve-kernel-3.10.0-13-pve: 3.10.0-38 pve-kernel-2.6.32-41-pve: 2.6.32-164 pve-kernel-4.2.3-2-pve: 4.2.3-22 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 1.0-1 pve-cluster: 4.0-39 qemu-server: 4.0-72 pve-firmware: 1.1-8 libpve-common-perl: 4.0-59 libpve-access-control: 4.0-16 libpve-storage-perl: 4.0-50 pve-libspice-server1: 0.12.5-2 vncterm: 1.2-1 pve-qemu-kvm: 2.5-14 pve-container: 1.0-62 pve-firewall: 2.0-25 pve-ha-manager: 1.0-28 ksm-control-daemon: 1.2-1 glusterfs-client: 3.5.2-2+deb8u1 lxc-pve: 1.1.5-7 lxcfs: 2.0.0-pve2 cgmanager: 0.39-pve1 criu: 1.6.0-1 fence-agents-pve: 4.0.20-1 openvswitch-switch: 2.3.2-3 (yes, i should cleanup old kernel versions...) steps i took sofar: * migrated all vm's of one node * upgraded this node * rebooted it * tried to migrate vms back to this host to upgrade another one since there was a thread on the mailling list about migration problems that where fixed with newer qemu-server/pve-qemu-kvm version, i then upgraded the other two nodes (disabeling HA first). i still cannot online migrate, even a vm that has been booted on the fully upgraded node. unfortunatly the error message i get is not really informative: ERROR: online migration failure - aborting am i running into some known problem here or is this a new issue? thx regards, albert ps: rebooting the remaining nodes without migrating the VMs off them would be really inconvinient... _______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
