Live migration not working after removing Network from boot order

[Attilas]

PVE 3.1-21. Dual Proxmox server with LVM Freenas iSCSI Shared Storage.

I have noticed that after chaging boot order from Network to None it made live migration impossible. This behavior was present on all my VMs. It is easily reproductible on my cluster with this procedure.

1) Create new VM with Windows XP OS, No media, 1G HD (On shared storage), All other default
2) Start VM (Will loop on boot sequence)
3) Up to now everything is fine, can live migrate VM between hosts.
4) Go into Option, edit boot order and set boot device 3 from Network to None.
5) Now migration is unable to complete with the following error

[COLOR=#000000][FONT=tahoma]Dec 28 10:26:55 starting migration of VM 106 to node 'proxmox1' (192.168.1.70)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Dec 28 10:26:55 copying disk images[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Dec 28 10:26:55 starting VM 106 on remote node 'proxmox1'[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Dec 28 10:26:57 starting ssh migration tunnel[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Dec 28 10:26:57 starting online/live migration on localhost:60000[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Dec 28 10:26:57 migrate_set_speed: 8589934592[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Dec 28 10:26:57 migrate_set_downtime: 0.1[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Dec 28 10:26:59 ERROR: online migrate failure - aborting[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Dec 28 10:26:59 aborting phase 2 - cleanup resources[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Dec 28 10:26:59 migrate_cancel[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Dec 28 10:27:00 ERROR: migration finished with problems (duration 00:00:05)[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]TASK ERROR: migration problems[/FONT][/COLOR]

Two way I found to correct the problem:

1) Put back Network as boot device 3
2) Stop and reboot this VM.

Is this reproductible on someone else cluster ?

Thanks

 

[spirit]

Hi,

This is because when you can boot order, it's not applied yet to current running qemu. (you need to stop/start the vm).

And when you are doing a live migration, the target vm start with new boot parameters.

Both source and target need to be started with same running configuration, or it'll hang.

 

[Attilas]

Thank you very much for the information.