VM's Reboot When Live Migrating

[Josh237]

Hello All,
I hope you can help me as this is driving me crazy and I have not really found anything that helped me to fix my issue.

I have 2 Nodes in a Cluster and when doing a live migration from node1 to node2 I notice that once it migrates it is also rebooting the VM.
If I then Live Migrate from Node2 to Node1 everything works fine and I never lose connection and no reboot happens.
So it seems that only from Node1 to node2 does this happen.

Can someone please help me before I go crazy!

Thanks

 

[sterzy]

Hi,

would you mind providing the VM and storage configuration as well as some information about the hardware of your nodes (CPU type etc.)?

 

[Josh237]

Node1-
CPU(s) 32 x Intel(R) Xeon(R) Silver 4108 CPU @ 1.80GHz (2 Sockets)
Kernel Version Linux 5.15.35-2-pve #1 SMP PVE 5.15.35-5 (Wed, 08 Jun 2022 15:02:51 +0200)
PVE Manager Version pve-manager/7.2-4/ca9d43cc

Node2-
CPU(s) 40 x Intel(R) Xeon(R) CPU E5-2650L v2 @ 1.70GHz (2 Sockets)
Kernel Version Linux 5.15.35-2-pve #1 SMP PVE 5.15.35-5 (Wed, 08 Jun 2022 15:02:51 +0200)
PVE Manager Version pve-manager/7.2-4/ca9d43cc

Storage is Shared storage to a Synology NAS - NFS

 

[sterzy]

Thank you, however, please also provide the VM configuration otherwise it is difficult to say what your problem may be.

 

[Supme]

After upgrading proxmox from 6.4 to 7.2, I also ran into this problem.

host with cpu Xeon Gold -> host with CPU Xeon e5-2650 after successful CPU migration 100% (Linux continues to hang, Windows after a while goes to reboot in the blue screen)

host with cpu Xeon e5-2650 -> host with cpu Xeon Gold normal migration

host with Xeon Gold cpu -> host with Xeon Gold cpu normal migration

host with Xeon X5660 -> host with Xeon e5-2650 normal migration

I use default CPU type (kvm64) and machine type i440fx

 

[LnxBil]

host with cpu Xeon e5-2650 -> host with cpu Xeon Gold normal migration

host with Xeon Gold cpu -> host with Xeon Gold cpu normal migration

host with Xeon X5660 -> host with Xeon e5-2650 normal migration

Does this mean, that the migration from an older cpu generation to a newer one always works? That logic is sound.

 

[Supme]

Does this mean, that the migration from an older cpu generation to a newer one always works? That logic is sound.

Before upgrading to Proxmox 7.2 ( <= 6.4), migration was going on without problems

 

[sterzy]

Does this mean, that the migration from an older cpu generation to a newer one always works? That logic is sound.

Generally migrating from older CPUs to newer ones should work. Depending on the configuration might still arise. The problem here does likely stem from different CPU feature flags [1], but to say anything conclusive the VM configurations would be helpful.

[1]: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_cpu_type

 

[Supme]

agent: 1,type=virtio
balloon: 0
boot: cd
bootdisk: scsi0
cores: 4
cpu: kvm64
ide2: none,media=cdrom
machine: pc-i440fx-5.1
memory: 4096
name: test-vdi
net0: virtio=4E:7B:F4:CB:4D:09,bridge=vmbr1,tag=1530
numa: 0
ostype: win10
scsi0: fuji2T:vm-126-disk-0,cache=none,discard=on,size=52G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=c4740265-706e-409a-a1e9-0bcf947beeb8
sockets: 1
vmgenid: e1974db3-ee7a-46ce-babd-246a52b721b4

 

[Josh237]

I hope this is what you mean but if you need something else just let me know. Thanks

 

[Supme]

flags in VM on host Xeon E5


flags in VM on host Xeon Gold