Installing R82.10 on EVE-NG/PNETLab

[fabionfsc]

While creating a Check Point R82.10 template in EVE-NG/PNETLab, I encountered an issue where the installation process would crash during setup.

The problem was resolved by adding the following flag to the QEMU options: -cpu host

Without this flag, QEMU does not expose the physical host CPU to the virtual machine and instead presents a generic (emulated) CPU. With R82.10, this causes compatibility issues, likely due to the newer Linux kernel, which appears to require a valid and fully supported processor feature set rather than the default emulated CPU provided by QEMU.

[PhoneBoy]

Exactly the same issue with Promox, it turns out 🙂 
https://community.checkpoint.com/t5/CloudMates-General/Installing-R82-10-on-Promox/td-p/266159/jump-... 

I assume any virtualization system that leverages QEMU will run into a similar issue.

[fabionfsc]

Yes, the concept is the same.

I remember that when the EA version of R82.10 was released, I tested it in PNETLab/EVE-NG and ran into this exact issue. At the time, the only way I managed to fix it was by using the -cpu host flag, since Palo Alto images in PNETLab/EVE-NG only work properly with that flag enabled.

Today I saw your mention that this exact behavior also occurs in Proxmox. That’s when I remembered that this CPU flag behavior exists in QEMU as well, which led me to create this topic to make it easier for others to find this information in the future.

[the_rock]

Great to know!

[the_rock]

Phoneboy said it, exact same issue.

[the_rock]

One of these days, I will try it on eve-ng and see if same issue comes up 😉