@dinhngtu Thanks and good point. After my previous post I did stumble across some info (can't find the links) that suggested something similar. If I'm remembering correctly, the basic idea was the flash/NVRAM memory on the motherboard, which stores boot entries, is limited. If it's full, it's possible / may be necessary to do some cleanup using the bios itself or utilities available for Linux (efibootmgr) and Windows (bcdedit). I've not tried this myself as our install is working properly, but perhaps that can help someone else in the event they stumble across this particular issue.

@olivierlambert said in Same CPU XEON 4309Y but migration failed because some CPU features missing !: It could be microcode update and BIOS update making that change. Since they are not in the same pool, this can be expected. Indeed, migrate to the more recent, upgrade the old one/reboot and that should do the trick. Yes, the BIOS/microcode differences do sometimes change the CPU mask. They need to be identical in many cases on all hosts within a pool.

@stormi Thanks for your answer. I'll give a try later, bypassing the PFBlocker module of the router. Github is not currently on any blacklist, but I block Digital Ocean and some others who host many attackers.

@Danp Yes I did that and it looks good now.

Hi, You can use the warm migration in your case, yes To me, that's one of the use case where it's safer than a live/hot one.

@KPS This is an internal ticket. But I'm not against having a public issue as well