[pve-devel] Dedicated Migration Network #1177 v2

[Thomas Lamprecht]

On 11/16/2016 08:39 PM, Phil Kauffman wrote:
> I have done some light testing of this and it doesn't seem to work 
> quite right yet.
>
> Things I have done.
> - dist-upgrade on both machines and reboot.
> - able to ssh to and from both machines on alternate network without a 
> password
> - Migration works when VM is off or one does not set 
> 'type=secure|insecure'
>
>
> ### Migration hangs:
>
> root at bravo-vmnode2:~# cat /etc/pve/datacenter.cfg
> migration: type=secure,network=192.168.2.0/24
>
> Nov 16 13:36:08 use dedicated network address for sending migration 
> traffic (192.168.2.162)

> Nov 16 13:36:08 starting migration of VM 118 to node 'bravo-vmnode1' 
> (192.168.2.162)
> Nov 16 13:36:08 copying disk images
> Nov 16 13:36:08 starting VM 118 on remote node 'bravo-vmnode1'
> Nov 16 13:36:10 start remote tunnel
> Nov 16 13:36:11 starting online/live migration on 
> unix:/run/qemu-server/118.migrate
> Nov 16 13:36:11 migrate_set_speed: 8589934592
> Nov 16 13:36:11 migrate_set_downtime: 0.1
> Nov 16 13:36:11 set migration_caps
> Nov 16 13:36:11 set cachesize: 53687091
> Nov 16 13:36:11 start migrate command to 
> unix:/run/qemu-server/118.migrate
> Nov 16 13:36:13 migration status: active (transferred 2360760, 
> remaining 543330304), total 546119680)
> Nov 16 13:36:13 migration xbzrle cachesize: 33554432 transferred 0 
> pages 0 cachemiss 0 overflow 0
>
>
> This will hang until you stop it.

Does this trigger always?

This seems not directly related to the migration network changes,
as the API call _can_ already connect to the other node over the 
specified network.
Else it would not output like:

  > Nov 17 11:12:40 # /usr/bin/ssh -o 'BatchMode=yes' 
root at fd0f:38:500:15::3 /bin/true
  > Nov 17 11:12:40 Host key verification failed.

And if he can connect he does exactly the same things as on the other 
network.

Can you try migration type 'insecure' also?

Seems like a problem with your other network? Not quite sure, that seems 
strange to me.

>
>
> ### Migration succeeds, but parse error on /etc/pve/datacenter.cfg
>
> root at bravo-vmnode2:~# cat /etc/pve/datacenter.cfg
> migration: network=192.168.2.0/24

You're using a wrong format here, if the migration property gets set the 
type needs always to be set too.

>
>
> parse error in '/etc/pve/datacenter.cfg' - 'migration': invalid format 
> - format error
> migration.type: property is missing and it is not optional
>
> Nov 16 13:29:53 starting migration of VM 118 to node 'bravo-vmnode2' 
> (10.135.164.164)
> Nov 16 13:29:53 copying disk images
> Nov 16 13:29:53 starting VM 118 on remote node 'bravo-vmnode2'
> parse error in '/etc/pve/datacenter.cfg' - 'migration': invalid format 
> - format error
> migration.type: property is missing and it is not optional
>
> Nov 16 13:29:55 start remote tunnel
> Nov 16 13:29:56 starting online/live migration on 
> unix:/run/qemu-server/118.migrate
> Nov 16 13:29:56 migrate_set_speed: 8589934592
> Nov 16 13:29:56 migrate_set_downtime: 0.1
> Nov 16 13:29:56 set migration_caps
> Nov 16 13:29:56 set cachesize: 53687091
> Nov 16 13:29:56 start migrate command to 
> unix:/run/qemu-server/118.migrate
> Nov 16 13:29:58 migration speed: 256.00 MB/s - downtime 22 ms
> Nov 16 13:29:58 migration status: completed
> Nov 16 13:30:01 migration finished successfully (duration 00:00:08)
> TASK OK
>
>
>