[PVE-User] VM migration from k3.10 to k2.6.32 OK but migrated VM hung

[Eneko Lacunza]

I realized that there were newer 3.10 kernels so I just updated NODE4 . 
Same problem.

It would be nice to have a proxmox-ve-3.10 package.

NODE4 updated:
# pveversion -v
proxmox-ve-2.6.32: 3.4-160 (running kernel: 3.10.0-11-pve)
pve-manager: 3.4-9 (running version: 3.4-9/4b51d87a)
pve-kernel-2.6.32-40-pve: 2.6.32-160
pve-kernel-3.10.0-4-pve: 3.10.0-17
pve-kernel-2.6.32-39-pve: 2.6.32-157
pve-kernel-3.10.0-11-pve: 3.10.0-36
pve-kernel-2.6.32-37-pve: 2.6.32-150
pve-kernel-2.6.32-34-pve: 2.6.32-140
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-3
pve-cluster: 3.0-18
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
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.2-11
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

El 19/08/15 a las 13:01, Eneko Lacunza escribió:
> Hi all,
>
> We have a cluster of 4 proxmox nodes, all have 2 ceph osds and VMs 
> running on them.
> Node kernel version and uptodate status is: (version detail bellow).
>
> - node1: 2.6.32 kernel, 2 month behind versions
> - node2: 2.6.32 kernel, 2 month behind versions
> - node3: 2.6.32 kernel, up to date versions
> - node4: 3.10 kernel, 2 month behind versions
>
> I have noticed that migration from node4 to any other node (3.10 to 
> 2.6.32) ends with OK, but the VM is hung, no console nor network 
> reply. Migration from 2.6.32 to 3.10 kernel works ok, as does 2.6.32 
> to 2.6.32 .
>
> Is this a known bug?
>
> I've tried with default kvm64 processor, 256MB and 4 GB RAM, and 1 and 
> 2 cores. Guests Centos with 2.6.32 kernel and Debian 8.
>
> Thanks
> Eneko
>
> NODE1
> # pveversion -v
> proxmox-ve-2.6.32: 3.4-156 (running kernel: 2.6.32-39-pve)
> pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
> pve-kernel-2.6.32-32-pve: 2.6.32-136
> pve-kernel-2.6.32-39-pve: 2.6.32-156
> pve-kernel-2.6.32-37-pve: 2.6.32-150
> pve-kernel-2.6.32-34-pve: 2.6.32-140
> 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-17
> qemu-server: 3.4-6
> pve-firmware: 1.1-4
> libpve-common-perl: 3.0-24
> libpve-access-control: 3.0-16
> libpve-storage-perl: 3.0-33
> 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.2-10
> ksm-control-daemon: 1.1-1
> glusterfs-client: 3.5.2-1
>
> NODE2
> # pveversion -v
> proxmox-ve-2.6.32: 3.4-156 (running kernel: 2.6.32-39-pve)
> pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
> pve-kernel-2.6.32-32-pve: 2.6.32-136
> pve-kernel-2.6.32-39-pve: 2.6.32-156
> pve-kernel-2.6.32-37-pve: 2.6.32-150
> 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-17
> qemu-server: 3.4-6
> pve-firmware: 1.1-4
> libpve-common-perl: 3.0-24
> libpve-access-control: 3.0-16
> libpve-storage-perl: 3.0-33
> 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.2-10
> ksm-control-daemon: 1.1-1
> glusterfs-client: 3.5.2-1
>
> NODE3
> # pveversion -v
> proxmox-ve-2.6.32: 3.4-160 (running kernel: 2.6.32-40-pve)
> pve-manager: 3.4-9 (running version: 3.4-9/4b51d87a)
> pve-kernel-2.6.32-40-pve: 2.6.32-160
> pve-kernel-2.6.32-32-pve: 2.6.32-136
> pve-kernel-2.6.32-39-pve: 2.6.32-157
> 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-3
> pve-cluster: 3.0-18
> qemu-server: 3.4-6
> pve-firmware: 1.1-4
> libpve-common-perl: 3.0-24
> libpve-access-control: 3.0-16
> libpve-storage-perl: 3.0-33
> 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.2-11
> ksm-control-daemon: 1.1-1
> glusterfs-client: 3.5.2-1
>
> NODE4:
> # pveversion -v
> proxmox-ve-2.6.32: 3.4-156 (running kernel: 3.10.0-4-pve)
> pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
> pve-kernel-3.10.0-4-pve: 3.10.0-17
> pve-kernel-2.6.32-39-pve: 2.6.32-156
> pve-kernel-2.6.32-37-pve: 2.6.32-150
> pve-kernel-2.6.32-34-pve: 2.6.32-140
> 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-17
> qemu-server: 3.4-6
> pve-firmware: 1.1-4
> libpve-common-perl: 3.0-24
> libpve-access-control: 3.0-16
> libpve-storage-perl: 3.0-33
> 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.2-10
> ksm-control-daemon: 1.1-1
> glusterfs-client: 3.5.2-1
>
>
>


-- 
Zuzendari Teknikoa / Director Técnico
Binovo IT Human Project, S.L.
Telf. 943575997
       943493611
Astigarraga bidea 2, planta 6 dcha., ofi. 3-2; 20180 Oiartzun (Gipuzkoa)
www.binovo.es