- CheckMates
- :
- Products
- :
- Developers
- :
- API / CLI Discussion
- :
- Re: Check_Point_R80.20 error : couldn't find kerne...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Check_Point_R80.20 error : couldn't find kernel image : Linux
Hello,
I'm trying to install checkpoint R80.20 (standalone) on a VM (for testing purpose) on ESXi, but i'm having the following error
Error : couldn't find kernel image : Linux
As if the image is not bootable!
The file i'm using is : Check_Point_R80.20_T101_Security_Gateway.iso
Any suggestions to resolve this problem?
Thanks in advance.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is the correct image and you should be able to start from it - did you check size and hashes ?
File Name | Check_Point_R80.20_T101_Security_Gateway.iso |
Build Number | |
MD5 | d0f1a973dd30fd4f4d58c36bd18e0b59 |
SHA1 | 1292d82789df6fd3eaf491b1d1cb1d65e4a7bc8a |
Size | 3248.40 MB |
Date Published | 2018-09-25 |
Support for R80.20 ends September 2022 - why not install a current version like R81 or at least R80.40 ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you configure correct Guest OS ?
Optimal virtual hardware presentation can be achieved when manually building a Virtual Machine running Check Point software by defining the Guest operating system (Guest OS Version) as :
Check Point operating systems running :
- Kernel versions 2.6 : "RedHat Enterprise Linux version 5 (64-bit)"
- Kernel versions 3.10 : "RedHat Enterprise Linux version 7 (64-bit)"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The "Guest OS" option in VMware VMs just affects the initial hardware when building the VM and which VMware Tools image it offers when you tell it to install Tools. It has no other impact on the VM once it is built.
It sounds like the installation didn't actually work. My bet is ESXi is giving the guest UEFI, but R80.20 needs BIOS instead.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It was BIOS and it didn't work.
Is the file "Check_Point_R80.20_T101_Security_Gateway.iso" contains the OS? : or it should have Gaia in the name ?
I'm not sure if the file contains the OS because when I downloaded another version R80.10 for evaluation...the file name containes gaia!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We tested with RedHat Enterprise Linux version 5 (64-bit) and RedHat Enterprise Linux version 7 (64-bit) but we have the same error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If sk74400: "No hard drives have been found" warning (ESX / ESXi ) did not help, ask TAC !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is the correct image and you should be able to start from it - did you check size and hashes ?
File Name | Check_Point_R80.20_T101_Security_Gateway.iso |
Build Number | |
MD5 | d0f1a973dd30fd4f4d58c36bd18e0b59 |
SHA1 | 1292d82789df6fd3eaf491b1d1cb1d65e4a7bc8a |
Size | 3248.40 MB |
Date Published | 2018-09-25 |
Support for R80.20 ends September 2022 - why not install a current version like R81 or at least R80.40 ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, yes you are right, comparing the md5 and hashes were different.
We downloaded the file again and it's booting this time but we are facing another problem that it doesn't find the hard drives : "No hard drives have been found" ESXi
We have tested the following solutions, we still have the same issue:
Solution 1 : Change SCSI controller type de "VMware Paravirtual" to "LSI Logic Parallel" or " LSI Logic SAS".
Solution 2 : Create the VM with "Red hat Enterprise Linux 5 (64-bit).
Do you have any idea how to solve this issue?
Thanks!
