Table of Contents:
Check Point Gaia OS can be deployed (ISO image) over Hyper-V infrastructure in Windows Server:
Note: Refer to Check Point Hardware Compatibility List - go to tab "Virtual Machines".
Hyper-V provides software infrastructure and basic management tools to create and manage a virtualized server computing environment. Hyper-V in Windows Server 2012 R2 enables the creation of a virtualized server computing environment. You can use a virtualized computing environment to improve the efficiency of your computing resources by utilizing more of your hardware resources. This is possible because you use Hyper-V to create and manage virtual machines and their resources. Each virtual machine is a virtualized computer system that operates in an isolated execution environment. This allows you to run multiple operating systems simultaneously on one physical computer.
Supported Hyper-V versions
|Windows 2019 Server
|Windows 2016 Server
|Windows 2012 Server R2
|Windows 2012 Server
|Windows 2008 Server R2
|Windows 2008 Server
(*) Refer to Check Point Hardware Compatibility List - go to tab "Virtual Machines".
(**) R80.30 Management is supported only with Windows 2016 server.
(***) R80.40 and higher versions are supported on Windows 2019 server.
Drivers incorporated into Gaia OS
|Hyper-V vmbus driver
||Provides the infrastructure for other Hyper-V drivers to communicate with the hypervisor
||Provides Hyper-V integration services such as shutdown, time synchronization, heartbeat and Key-Value Pair Exchange
||Provides network performance improvements
||Increases performance when accessing storage (IDE and SCSI) devices
||Improves user experience by allowing mouse focus changes for a virtualized guest
||Provides a stable clock source running within the Hyper-V platform
- In a rare scenario. Hyper-V Time Synchronization doesn't correct the system clock in the virtual machine.
- For more details, refer to https://docs.microsoft.com/en-us/troubleshoot/windows-server/virtualization/virtual-machine-time-not-synced.
Hyper-V supports two types of network interfaces:
|Synthetic network interface
- Jumbo frames are supported
- VLAN tagging is supported
- VLAN trunking is supported from R80.40
- Live Migration is supported
- Static IP Injection is not supported
- vRSS (Virtual Receive Side Scaling) is not supported
- TCP Segmentation and Checksum Offloads is supported
|Emulated networks interfaces
- VLAN trunking is not supported
- NOTE: It is recommended to use a synthetic network interface.
- When setting up the machine, it is recommended to assign it with a static MAC address. This should ensure that the VM retains its MAC address in case it is moved to another host. You can configure the MAC address by editing the settings of the virtual machine in Hyper-V Manager.
- For more details, refer to Supported CentOS and Red Hat Enterprise Linux virtual machines on Hyper-V.
For more details, refer to Supported CentOS and Red Hat Enterprise Linux virtual machines on Hyper-V - "RHEL/CentOS 5.x Series".
File system freeze/thaw
Some operating systems support the notion of freezing and thawing the file system (refer to http://rwmj.wordpress.com/2010/06/09/freezing-filesystems/
- coreXL - affinity
hv_netvsc interfaces are automatically affined by hyper-v to all cores.
This behavior cannot be controlled from the VM.
there for you can't assign hv_netvsc interfaces to specific CPU cores
SCSI disks are currently not supported (at least not for the main installation disk).
Attempting to use SCSI disks may cause the image installation to fail in unexpected ways.
- Dynamic Disk
Dynamic Disk should never be used in a production environment. Dynamic Disks is not suitable for for VM's with a long life span.
- Prone to fragmentation issues that can potential causes the VM to become unresponsive.
- Slower read rates
- Performance decreases overtime
- Unpredictable storage utilization patterns
This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.