Live migration of VM network issue

[MeyrNL]

Hi all,

Since the upgrade to version 3.4 I am experiencing serious problems with the (live) migration functionality of my VMs to hypervisors in the same cluster.
On the moment of the hypervisor switch-over of the VM, the network becomes unavailable and is not replying on any ICMP packets. After suspending/restoring the VM the network of the VM comes back alive.

It sounds to me that this is related to R-ARP packet not being send correctly. Are others experiencing the same? Already a solution for this?

Thanks in advance,

Regards,
Stephan

----
:~# pveversion -v
proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-37-pve)
pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-37-pve: 2.6.32-147
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.3-20
pve-firmware: 1.1-3
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-31
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-12
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

 

[MeyrNL]

Update on this: reinstalled 3 hypervisors with version 3.3 (a06c9f73) and the problem does NOT exists between those reinstalled hypervisors. So it is definitely related to the latest release, so please check the last release.

 

[fireon]

Same problem.

 

[MeyrNL]

I did several tests by changing the options in Linux bridges bridge_stp off and bridge_fd 0, but still not works. TCP dump shows the VM sends out an ARP correctly, but simply doesn't come through. Now have do to a arping after migration, even this was not before using version 3.4.

 

[MeyrNL]

Is there none of Proxmox who can help us with this issue?

 

[udo]

Is there none of Proxmox who can help us with this issue?

Hi,
is it kernel related? EG. does it work with pve3.4 and the kernel from 3.3?

Udo

 

[MeyrNL]

Hi Udo,

Thank you for your reply.

I've tried with the precursor kernels of 2.6 and 3.10, and unfortunately not working.
I am not able to downgrade, because then I have to reboot all VM's of my customers (>150).

Kind regards,
MeyRNL

 

[mir]

Have you tried using kernel 2.6.32-34-pve on 3.4?
I had issues with 2.6.32-37-pve and infiniband. reverting to 2.6.32-34-pve on 3.4 solved my issues.

 

[spirit]

I'm running kernel 3.10 on proxmox 3.4, no problem here. (I have done around 400 live migration without network error)

Can't tell for 2.6.32 kernel.