https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-EVE-NG-PNETLab/m-p/266167#M5653 <P>Phoneboy said it, exact same issue.</P> Mon, 29 Dec 2025 20:47:49 GMT the_rock 2025-12-29T20:47:49Z https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-EVE-NG-PNETLab/m-p/266165#M5651 <P>While creating a Check Point R82.10 template in EVE-NG/PNETLab, I encountered an issue where the installation process would crash during setup.</P><P>The problem was resolved by adding the following flag to the QEMU options: <STRONG>-cpu host</STRONG></P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Sem título.png" style="width: 999px;"><img src="https://community.checkpoint.com/t5/image/serverpage/image-id/32575iFC3FE209EEA16D25/image-size/large?v=v2&amp;px=999" role="button" title="Sem título.png" alt="Sem título.png" /></span></P><P>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.</P> Mon, 29 Dec 2025 19:28:53 GMT https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-EVE-NG-PNETLab/m-p/266165#M5651 fabionfsc 2025-12-29T19:28:53Z https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-EVE-NG-PNETLab/m-p/266166#M5652 <P>Exactly the same issue with Promox, it turns out <span class="lia-unicode-emoji" title=":slightly_smiling_face:">🙂</span>&nbsp;<BR /><A href="https://community.checkpoint.com/t5/CloudMates-General/Installing-R82-10-on-Promox/td-p/266159/jump-to/first-unread-message" target="_blank">https://community.checkpoint.com/t5/CloudMates-General/Installing-R82-10-on-Promox/td-p/266159/jump-to/first-unread-message</A>&nbsp;</P> <P>I assume any virtualization system that leverages QEMU will run into a similar issue.</P> Mon, 29 Dec 2025 20:07:14 GMT https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-EVE-NG-PNETLab/m-p/266166#M5652 PhoneBoy 2025-12-29T20:07:14Z https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-EVE-NG-PNETLab/m-p/266167#M5653 <P>Phoneboy said it, exact same issue.</P> Mon, 29 Dec 2025 20:47:49 GMT https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-EVE-NG-PNETLab/m-p/266167#M5653 the_rock 2025-12-29T20:47:49Z https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-EVE-NG-PNETLab/m-p/266168#M5654 <P>One of these days, I will try it on eve-ng and see if same issue comes up <span class="lia-unicode-emoji" title=":winking_face:">😉</span></P> Mon, 29 Dec 2025 21:17:10 GMT https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-EVE-NG-PNETLab/m-p/266168#M5654 the_rock 2025-12-29T21:17:10Z https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-EVE-NG-PNETLab/m-p/266169#M5655 <P>Yes, the concept is the same.</P><P>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.</P><P>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.</P> Mon, 29 Dec 2025 21:21:23 GMT https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-EVE-NG-PNETLab/m-p/266169#M5655 fabionfsc 2025-12-29T21:21:23Z https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-EVE-NG-PNETLab/m-p/266170#M5656 <P>Great to know!</P> Mon, 29 Dec 2025 22:10:18 GMT https://community.checkpoint.com/t5/Cloud-Firewall/Installing-R82-10-on-EVE-NG-PNETLab/m-p/266170#M5656 the_rock 2025-12-29T22:10:18Z