Aborting migration of VM

[bohansen]

Hi,

I am trying 1.6 and have upgrade 1 of 2 servers. It all seems fine and I want to move the VMs to the other server to upgrade the second server. I tried online migration, but that is not possible from a 2.6.18 to 2.6.32 kernel? Any way, the migration process seems to stall and when I pressed abort I now got the same VM listed on both servers. I know I did something I probably shouldn't but duplicate entries is not very good. It would be nice if online migration would just not start at all if you try to migrate between incompatible kvm versions?

Best regards,
Bo

 

[dietmar]

I know I did something I probably shouldn't but duplicate entries is not very good. It would be nice if online migration would just not start at all if you try to migrate between incompatible kvm versions?

Yes, maybe be should restrict that. But the more correct solutions is that KVM aborts migrations when it detects incompatibilities.

 

[m.ardito]

Interesting. What should one check to prevent migration incompatibilities? is there a sort of checklist?

Marco

 

[dietmar]

Interesting. What should one check to prevent migration incompatibilities? is there a sort of checklist?

I guess best is to use same kernel versions. But I don't want to force that now.