> Source: [sk106855](https://support.checkpoint.com/results/sk/sk106855)

# sk106855 - Check Point Gaia OS support for Hyper-V

| Property | Value |
|----------|-------|
| Solution ID | sk106855 |
| Date Created | 2015-07-15 |
| Last Modified | 2026-08-24 |
| Technical Level | General |
| Products | Security Gateway, Security Management Server, Multi-Domain Security Management Server |
| Versions | R82, R81.20, R81.10 (EOS), R82, R81.20, R81 (EOS), R81.10 (EOS), R81 (EOS), R81 (EOS), R81.10 (EOS), R81.20, R82 |
| OS | Gaia |
| Platform | Intel/PC |

## Solution

**Table of Contents:**

* Introduction
* Supported Hyper-V versions
* Drivers Incorporated into Gaia OS
* Network Interfaces
* Non-Supported Features
* Troubleshooting

### Introduction {#Introduction}

Check Point Gaia OS (ISO image) for all supported versions starting from R77.30 can be deployed over [Hyper-V infrastructure](https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-technology-overview) in Windows Server on Security Gateway / Security Management Server / Multi-Domain Security Management Server.

Refer to [Check Point Hardware Compatibility List](https://www.checkpoint.com/support-services/hcl/#vm) - at the top, click "**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 {#Supported Hyper-V versions}

|------------------------|-----------------|
| Version                | Status          |
| Windows 2025 Server    | Supported (?)   |
| Windows 2022 Server    | Supported (?)   |
| Windows 2019 Server    | Supported (�)   |
| Windows 2016 Server    | Supported ^(�)^ |
| Windows 2012 Server R2 | Supported ^(�)^ |
| Windows 2012 Server    | *Not* supported |
| Windows 2008 Server R2 | *Not* supported |
| Windows 2008 Server    | *Not* supported |

^(�)^ Refer to [Check Point Hardware Compatibility List](https://www.checkpoint.com/support-services/hcl/#vm) - go to tab "Virtual Machines".  
^(�)^ R80.30 Management is supported only with Windows 2016 server.  
(�) R80.40 up to and including R81.20 are supported on Windows Server 2019.   
(?) R82 and higher versions are supported on Windows 2022 and Windows 2025 servers.

**Note** : If you are unsure whether a specific version is supported, refer to the official [Hardware Compatibility List (HCL)](https://www.checkpoint.com/support-services/hcl/#virtual-machines) as the authoritative source.

### Drivers Incorporated into Gaia OS {#Drivers incorporated into Gaia OS R77.30}

|----------------------|--------------|---------------------------------------------------------------------------------------------------------------------|
| Driver Type          | Driver Name  | Description                                                                                                         |
| Hyper-V vmbus driver | *hv_vmbus*   | Provides the infrastructure for other Hyper-V drivers to communicate with the hypervisor                            |
| Utility driver       | *hv_utils*   | Provides Hyper-V integration services such as shutdown, time synchronization, heartbeat and Key-Value Pair Exchange |
| Network driver       | *hv_netvsc*  | Provides network performance improvements                                                                           |
| Storage driver       | *hv_storvsc* | Increases performance when accessing storage (IDE and SCSI) devices                                                 |
| Mouse driver         | *hid_hyperv* | Improves user experience by allowing mouse focus changes for a virtualized guest                                    |
| Clocksource driver   |              | Provides a stable clock source running within the Hyper-V platform                                                  |

**Notes:**

* In a rare scenario. Hyper-V Time Synchronization does not 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>.

### Network Interfaces {#Network interfaces}

Hyper-V supports two types of network interfaces:

|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Interface Type               | Notes                                                                                                                                                                                                                                                                                           |
| 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 - We recommend to use a synthetic network interface.**                                                                                                                                                                                              |

**Notes:**

* 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](https://technet.microsoft.com/windows-server-docs/compute/hyper-v/supported-centos-and-red-hat-enterprise-linux-virtual-machines-on-hyper-v#BKMK_5x).

### Non-Supported Features {#Non-supported features}

For more details, refer to [Supported CentOS and Red Hat Enterprise Linux virtual machines on Hyper-V](https://technet.microsoft.com/windows-server-docs/compute/hyper-v/supported-centos-and-red-hat-enterprise-linux-virtual-machines-on-hyper-v#BKMK_5x) - "RHEL/CentOS 5.x Series".

* **Generation-2 virtual machines
  Note:** On Windows 2022 Server - supported for UEFI, not for secure boot

* **Hyper-V clocksource does not work on 64-bit kernel**

  Refer to [sk105862 - In a Hyper-V environment, the Virtual Machine's clock moves faster than the hardware time](https://support.checkpoint.com/results/sk/sk105862).
* **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/>)
* **vRSS (Virtual Receive Side Scaling)**

  Hyper-V can support the notion of multi-queue. This is done by a feature in Windows called RSS (Receive Side Scaling).

  Gaia built-in feature Multi-Queue is not supported on the *hv_netvsc* interfaces.
* **CoreXL Affinity of interfaces**

  Hyper-V automatically affines the *hv_netvsc* interfaces to all CPU cores.

  This behavior cannot be controlled from the VM. Therefore, you cannot assign the *hv_netvsc* interfaces to specific CPU cores.
* **SCSI**

  * SCSI disks are supported with Hyper-V Gen2.

  * Using SCSI disks with Hyper-V Gen1 isn't supported

* **Dynamic Disk**

  Never use Dynamic Disk in a production environment.

  Dynamic Disk is not suitable for VMs 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
* **SR-IOV (Single Root I/O Virtualization)**

  SR-IOV, designed to provide VMs more direct access to the physical host's hardware, is currently *not* certified for use on Hyper-V.
* ***lsvmbus* command**

* **Hyper-V Sockets**

* **TRIM support**

* **Dynamic Memory - Hot-Add**

* **Runtime Memory Resize**

* **PCI Passthrough/DDA**

* **Boot using UEFI**

* **Secure boot**

* **Microsoft Converged Storage**

* **Live Migration**

### Troubleshooting {#Troubleshooting}

* By default, ClusterXL uses Unicast for Cluster Control Protocol (CCP). If the hypervisor environment does not use Unicast, CCP packets do not reach other cluster members.

  For more details, refer to [sk169763 - Cluster member in OpenStack or Hyper-V does not work properly](https://support.checkpoint.com/results/sk/sk169763).

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content
