- Products
- Learn
- Local User Groups
- Partners
- More
Step Into the Future of
AI-Powered Cyber Security
The State of Ransomware Q1 2026
Key Trends and Their Impact
AI Security Masters E8:
Claude Mythos: New Era in Cyber Security
Blueprint Architecture for Securing
The AI Factory & AI Data Center
Call For Papers
Your Expertise. Our Stage
CheckMates Go:
CheckMates Fest
Hi engineers,
I saw the recommended guest OS version changes from RHEL7(R81.20) to 8(R82), and am wondering how to switch it.
VMware ESXi hosts my VMs.
I think of the step-by-step procedure below:
1. turn off VM after upgrading.
2. switch guest OS to RHEL8
3. power VM and check the status.
Is this a supported way to do so?
Since it is hard to make sure everything is alright after upgrading, I would be appreciating it if there is a supported way by CheckPoint, written in SK if possible.
As a side note, CPUSE upgrade is only option due to several reasons, mainly paperwork affairs.
Thanks in advance.
Saitoh
Your procedure is good, shutting down the VM and changing the setting after the upgrade will work. I think probably most of the time no one changes that and it doesn't cause problems, but if you are going to do it then that way is good.
Sounds right to me as well.
Your procedure is good, shutting down the VM and changing the setting after the upgrade will work. I think probably most of the time no one changes that and it doesn't cause problems, but if you are going to do it then that way is good.
Sounds right to me as well.
Just be aware that only one upgrade is allowed (supported) in VMs, as per the release notes.
|
Notes:
|
Hi @Don_Paterson ,
I actually did not know this.
Without your help, I would have worst time when getting on upgrading at our customer's site.
You saved my life!!
Saitoh
Yea, Don made an excellent point, something to keep in mind, for sure.
Note that the guest OS setting in hypervisors is really just a preset for the hardware configuration. That is, when building a new VM, it sets how many cores, how much RAM, which boot ROM the new VM is set to use, and so on. It doesn't change anything about how the VM runs.
100% what Bob wrote.
After creating the VM there's no reason to touch this at all.
I always find doing migrate export and then import on brand new server works real well.
I am not familiar with VMs, and was wondering to what a Guest OS choice make difference.
Is it like, the options of hardware settings (such as the type of vNICs) are given based on Guest OS, and
it does not actually matter since Guest OS does not change hardware settings?
Saitoh
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 26 | |
| 13 | |
| 11 | |
| 10 | |
| 7 | |
| 7 | |
| 6 | |
| 6 | |
| 6 | |
| 6 |
Wed 13 May 2026 @ 11:00 AM (EDT)
TechTalk: The State of Ransomware Q1 2026: Key Trends and Their ImpactThu 14 May 2026 @ 07:00 PM (EEST)
Under the Hood: Presentando Check Point Cloud Firewall como ServicioFri 29 May 2026 @ 09:00 AM (EDT)
Caracas: Executive Breakfast: Innovación en Ciberseguridad – IA y Threat IntelligenceAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY