R82.10 ISO Install fails on VMWare Vcenter 7

[Robert_CCSM_E]

Has anyone run across this?  Trying to install R82.10 in VMWare vCenter 7 vm with 8cpu's, 32gb memory, and 1TB of space. It goes through info that you enter, I left the default partition values in place, and then let it run. During the "Installing Packages" at 87% it craps out with a bunch of python scripts gibberish:

 

Has anyone seen this and know how to get around this?  I've tried installing the VM stating the client os is Redhat Linux 7 (64bit) and Redhat Linux 8 (64bit) and both fail at the same place.  Is it possibly a bad ISO file or is there a VM setting that is set wrong or missed?

Thanks.

[the_rock]

Hey,

Not sure if this might be related, but worth checking.

https://community.checkpoint.com/t5/CloudMates-General/Installing-R82-10-on-Promox/m-p/266159#M635

[Don_Paterson]

I have not seen that.

According to the published documentation Check Point do not officially support of R82.10 on any virtual platforms (private cloud) at this point in time.

The Release Notes say nothing really and point to the HCL, which shows no support: 

https://www.checkpoint.com/support-services/hcl/#virtual-machines 

Although CloudGuard does offer R82.10 in the public cloud platforms/marketplace (Azure etc.)

I upgraded an R82 JHFA 33 Hyper-V based lab SMS VM to R82.10 (via CPUSE) and that worked.

I guess you could try an R82 install and see how that goes and then CPUSE upgrade or clean install. Just a thought.

[Amir_Senn]

Choosing Red Hat 7/8 is meaningless, this is just pre-defined set of defaults.

My guess is that it could be driver related - check definitions for network adapters, SCSI controller and such.

Also, are you using BIOS or EFI? BIOS might go smoother but default for RHEL is EFI

[saitoh]

I have never encountered the same problem, but I suggest changing firmware to legacy BIOS, if it is set to EFI or something.

R82, UEFI BIOS is not supported on Open Servers and Virtual Machines (load from the legacy BIOS only).

https://support.checkpoint.com/results/sk/sk168335

The same thing might go along with R82.10, I surmise.

[Robert_CCSM_E · Accepted solution]

Well it seems I had to take the long way around.  I installed an R81.20, installed JHF 122 on it, and then did the upgrade to R82.10 and then was able to import my original R82 MDS export into it and everything is running just fine now.  Strange that I couldnt install R82.10 originally and that I had to jump through hoops to get it working.

What's really strange is I have another VMWare server exactly like it and R82.10 installed just fine in a VM.

Maybe it was a resource issue on the first server that may have caused it.

But everything is working like a champ now.

Thanks.

[the_rock]

Thanks for the update, Robert. Glad you got it going.