Re: [pve-devel] Latest upgrade in enterprise repro
On Fri, 2 Dec 2016 17:08:40 +0100 (CET) Dietmar Maurer wrote: > > Udo report same problem on forum > > > > https://forum.proxmox.com/threads/live-migration-between-4-3-71-4-3-72.30757/ > > > > yes, I see. > Come to think of it. Are we facing the same unsolved issue concerting the failure to make online snapshots? -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -- /usr/games/fortune -es says: A chronic disposition to inquiry deprives domestic felines of vital qualities. pgpSX40Cq0boC.pgp Description: OpenPGP digital signature ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Latest upgrade in enterprise repro
> Udo report same problem on forum > > https://forum.proxmox.com/threads/live-migration-between-4-3-71-4-3-72.30757/ yes, I see. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Latest upgrade in enterprise repro
Udo report same problem on forum https://forum.proxmox.com/threads/live-migration-between-4-3-71-4-3-72.30757/ - Mail original - De: "Dominik Csapak" À: "pve-devel" Envoyé: Vendredi 2 Décembre 2016 12:52:28 Objet: Re: [pve-devel] Latest upgrade in enterprise repro On 12/01/2016 10:51 PM, Michael Rasmussen wrote: > Hi all, > > I am sorry but I have to say that the latest upgrade in enterprise repo > is a disaster. Migration after upgrade is not possible and migration > before upgrade is not possible either! To not be able to migrate > after upgrade was expected but not been able to migrate before > upgrade was certainly a big surprise. This means upgrading is > impossible without downtime. I did expect to see a big warning poster > on the forum. > > Log from migrate before upgrade: > With: migration_unsecure: 1 > Dec 01 22:35:52 starting migration of VM 156 to node 'esx1' (10.0.0.1) > Dec 01 22:35:52 copying disk images > Dec 01 22:35:52 starting VM 156 on remote node 'esx1' > Dec 01 22:35:55 starting online/live migration on tcp:localhost:60001 > Dec 01 22:35:55 migrate_set_speed: 8589934592 > Dec 01 22:35:55 migrate_set_downtime: 0.1 > Dec 01 22:35:55 set migration_caps > Dec 01 22:35:55 set cachesize: 107374182 > Dec 01 22:35:55 spice client_migrate_info > Dec 01 22:35:55 start migrate command to tcp:localhost:60001 > Dec 01 22:35:57 migration status error: failed > Dec 01 22:35:57 ERROR: online migrate failure - aborting > Dec 01 22:35:57 aborting phase 2 - cleanup resources > Dec 01 22:35:57 migrate_cancel > Dec 01 22:35:58 ERROR: migration finished with problems (duration 00:00:06) > TASK ERROR: migration problems > Without migration_unsecure > # qm migrate 156 esx1 --online > Dec 01 22:42:27 starting migration of VM 156 to node 'esx1' (10.0.0.1) > Dec 01 22:42:27 copying disk images > Dec 01 22:42:27 starting VM 156 on remote node 'esx1' > Dec 01 22:42:30 start remote tunnel > Dec 01 22:42:31 starting online/live migration on > unix:/run/qemu-server/156.migrate > Dec 01 22:42:31 migrate_set_speed: 8589934592 > Dec 01 22:42:31 migrate_set_downtime: 0.1 > Dec 01 22:42:31 set migration_caps > Dec 01 22:42:31 set cachesize: 107374182 > Dec 01 22:42:31 spice client_migrate_info > Dec 01 22:42:31 start migrate command to unix:/run/qemu-server/156.migrate > Dec 01 22:42:33 migration status: active (transferred 625774775, remaining > 313741312), total 1208827904) > Dec 01 22:42:33 migration xbzrle cachesize: 67108864 transferred 0 pages 0 > cachemiss 0 overflow 0 > Dec 01 22:42:35 migration speed: 256.00 MB/s - downtime 48 ms > Dec 01 22:42:35 migration status: completed > Dec 01 22:42:37 ERROR: VM 156 not running > Dec 01 22:42:37 ERROR: command '/usr/bin/ssh -o 'BatchMode=yes' root@10.0.0.1 > qm resume 156 --skiplock --nocheck' failed: exit code 2 > Dec 01 22:42:37 Waiting for spice server migration > Dec 01 22:42:39 ERROR: migration finished with problems (duration 00:00:12) > migration problems > > Migration succeeded but was not able to start the VM on the other node. > from which version did you upgrade? which version were the source and the target node? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] Latest upgrade in enterprise repro
On 12/01/2016 10:51 PM, Michael Rasmussen wrote: Hi all, I am sorry but I have to say that the latest upgrade in enterprise repo is a disaster. Migration after upgrade is not possible and migration before upgrade is not possible either! To not be able to migrate after upgrade was expected but not been able to migrate before upgrade was certainly a big surprise. This means upgrading is impossible without downtime. I did expect to see a big warning poster on the forum. Log from migrate before upgrade: With: migration_unsecure: 1 Dec 01 22:35:52 starting migration of VM 156 to node 'esx1' (10.0.0.1) Dec 01 22:35:52 copying disk images Dec 01 22:35:52 starting VM 156 on remote node 'esx1' Dec 01 22:35:55 starting online/live migration on tcp:localhost:60001 Dec 01 22:35:55 migrate_set_speed: 8589934592 Dec 01 22:35:55 migrate_set_downtime: 0.1 Dec 01 22:35:55 set migration_caps Dec 01 22:35:55 set cachesize: 107374182 Dec 01 22:35:55 spice client_migrate_info Dec 01 22:35:55 start migrate command to tcp:localhost:60001 Dec 01 22:35:57 migration status error: failed Dec 01 22:35:57 ERROR: online migrate failure - aborting Dec 01 22:35:57 aborting phase 2 - cleanup resources Dec 01 22:35:57 migrate_cancel Dec 01 22:35:58 ERROR: migration finished with problems (duration 00:00:06) TASK ERROR: migration problems Without migration_unsecure # qm migrate 156 esx1 --online Dec 01 22:42:27 starting migration of VM 156 to node 'esx1' (10.0.0.1) Dec 01 22:42:27 copying disk images Dec 01 22:42:27 starting VM 156 on remote node 'esx1' Dec 01 22:42:30 start remote tunnel Dec 01 22:42:31 starting online/live migration on unix:/run/qemu-server/156.migrate Dec 01 22:42:31 migrate_set_speed: 8589934592 Dec 01 22:42:31 migrate_set_downtime: 0.1 Dec 01 22:42:31 set migration_caps Dec 01 22:42:31 set cachesize: 107374182 Dec 01 22:42:31 spice client_migrate_info Dec 01 22:42:31 start migrate command to unix:/run/qemu-server/156.migrate Dec 01 22:42:33 migration status: active (transferred 625774775, remaining 313741312), total 1208827904) Dec 01 22:42:33 migration xbzrle cachesize: 67108864 transferred 0 pages 0 cachemiss 0 overflow 0 Dec 01 22:42:35 migration speed: 256.00 MB/s - downtime 48 ms Dec 01 22:42:35 migration status: completed Dec 01 22:42:37 ERROR: VM 156 not running Dec 01 22:42:37 ERROR: command '/usr/bin/ssh -o 'BatchMode=yes' root@10.0.0.1 qm resume 156 --skiplock --nocheck' failed: exit code 2 Dec 01 22:42:37 Waiting for spice server migration Dec 01 22:42:39 ERROR: migration finished with problems (duration 00:00:12) migration problems Migration succeeded but was not able to start the VM on the other node. from which version did you upgrade? which version were the source and the target node? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
[pve-devel] Latest upgrade in enterprise repro
Hi all, I am sorry but I have to say that the latest upgrade in enterprise repo is a disaster. Migration after upgrade is not possible and migration before upgrade is not possible either! To not be able to migrate after upgrade was expected but not been able to migrate before upgrade was certainly a big surprise. This means upgrading is impossible without downtime. I did expect to see a big warning poster on the forum. Log from migrate before upgrade: With: migration_unsecure: 1 Dec 01 22:35:52 starting migration of VM 156 to node 'esx1' (10.0.0.1) Dec 01 22:35:52 copying disk images Dec 01 22:35:52 starting VM 156 on remote node 'esx1' Dec 01 22:35:55 starting online/live migration on tcp:localhost:60001 Dec 01 22:35:55 migrate_set_speed: 8589934592 Dec 01 22:35:55 migrate_set_downtime: 0.1 Dec 01 22:35:55 set migration_caps Dec 01 22:35:55 set cachesize: 107374182 Dec 01 22:35:55 spice client_migrate_info Dec 01 22:35:55 start migrate command to tcp:localhost:60001 Dec 01 22:35:57 migration status error: failed Dec 01 22:35:57 ERROR: online migrate failure - aborting Dec 01 22:35:57 aborting phase 2 - cleanup resources Dec 01 22:35:57 migrate_cancel Dec 01 22:35:58 ERROR: migration finished with problems (duration 00:00:06) TASK ERROR: migration problems Without migration_unsecure # qm migrate 156 esx1 --online Dec 01 22:42:27 starting migration of VM 156 to node 'esx1' (10.0.0.1) Dec 01 22:42:27 copying disk images Dec 01 22:42:27 starting VM 156 on remote node 'esx1' Dec 01 22:42:30 start remote tunnel Dec 01 22:42:31 starting online/live migration on unix:/run/qemu-server/156.migrate Dec 01 22:42:31 migrate_set_speed: 8589934592 Dec 01 22:42:31 migrate_set_downtime: 0.1 Dec 01 22:42:31 set migration_caps Dec 01 22:42:31 set cachesize: 107374182 Dec 01 22:42:31 spice client_migrate_info Dec 01 22:42:31 start migrate command to unix:/run/qemu-server/156.migrate Dec 01 22:42:33 migration status: active (transferred 625774775, remaining 313741312), total 1208827904) Dec 01 22:42:33 migration xbzrle cachesize: 67108864 transferred 0 pages 0 cachemiss 0 overflow 0 Dec 01 22:42:35 migration speed: 256.00 MB/s - downtime 48 ms Dec 01 22:42:35 migration status: completed Dec 01 22:42:37 ERROR: VM 156 not running Dec 01 22:42:37 ERROR: command '/usr/bin/ssh -o 'BatchMode=yes' root@10.0.0.1 qm resume 156 --skiplock --nocheck' failed: exit code 2 Dec 01 22:42:37 Waiting for spice server migration Dec 01 22:42:39 ERROR: migration finished with problems (duration 00:00:12) migration problems Migration succeeded but was not able to start the VM on the other node. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -- /usr/games/fortune -es says: Q: What do you call 15 blondes in a circle? A: A dope ring. Q: Why do blondes put their hair in ponytails? A: To cover up the valve stem. pgpRN1_KwQ48u.pgp Description: OpenPGP digital signature ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
