Proxmox VE 4.0 2-node cluster: cannot migrate online

I have found this (sorry, french): http://forums.fedora-fr.org/viewtopic.php?id=56347
It suggests that I should need "kvm-intel" module, and it seems that it is true (I have some Intel CPUs), as it is not present on pve02-ivr:

pve01-ivr:
Code:
root@pve01-ivr:~#  lsmod | grep kvm
kvm_intel             163840  100 
kvm                   503808  1 kvm_intel
root@pve01-ivr:~#

pve02-ivr:
Code:
root@pve02-ivr:~# lsmod | grep kvm
kvm                   503808  0 
root@pve02-ivr:~#

Any clue why it's not present ? :-)


I cannot insert it:
Code:
root@pve02-ivr:~# modprobe kvm-intel
modprobe: ERROR: could not insert 'kvm_intel': Operation not supported
root@pve02-ivr:~#
 
Well well well, seems that I have to check again my BIOS. I suspect some wrong parameters on the second node regarding virtualisation...

OK, that was it. Sorry for that :-)


Now:
- Offline migration works, and I can start the VM on the second node.
- Online migration still fails:

Code:
Nov 02 18:39:47 starting migration of VM 119 to node 'pve02-ivr' (172.16.43.2)
Nov 02 18:39:47 copying disk images
Nov 02 18:39:47 starting VM 119 on remote node 'pve02-ivr'
Nov 02 18:39:50 starting ssh migration tunnel
Nov 02 18:39:51 starting online/live migration on localhost:60000
Nov 02 18:39:51 migrate_set_speed: 8589934592
Nov 02 18:39:51 migrate_set_downtime: 0.1
Nov 02 18:39:53 ERROR: online migrate failure - aborting
Nov 02 18:39:53 aborting phase 2 - cleanup resources
Nov 02 18:39:53 migrate_cancel
Nov 02 18:39:54 ERROR: migration finished with problems (duration 00:00:07)
TASK ERROR: migration problems


However, the VM that I migrated offline to node 2 is now all good with going back (online) to node 1, and back again (online) to node 2.
I am afraid that I should poweroff/on again all the VMs :(
 
Last edited:
However, the VM that I migrated offline to node 2 is now all good with going back (online) to node 1, and back again (online) to node 2.
I am afraid that I should poweroff/on again all the VMs :(

Well... for a VM I was not able to migrate online, I had to shutdown/start it again, and after that, migration went fine...
Not very happy about that, but anyway, if it has to be done, I'll do it :-)

Any clue why a shutdown/start seems required?