Skip to content

Commit 4552fe4

Browse files
committed
machine_configuration: Update readme
Disable the in-tree i915 and intel_vsec configuration so KMM can modprobe the OOT drivers. This is the short-term solution. In the long-run, the in-tree drivers unload should be handled by KMM operator. Signed-off-by: Hersh Pathak hersh.pathak@intel.com
1 parent 81ae172 commit 4552fe4

File tree

1 file changed

+9
-10
lines changed

1 file changed

+9
-10
lines changed

machine_configuration/README.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
# Setting up Machine Configuration
22

33
# Introduction
4-
Machine configuration operation is used to configure [Red Hat Enterprise Linux CoreOS (RHCOS)](https://docs.openshift.com/container-platform/4.12/architecture/architecture-rhcos.html) on each node in a RHOCP cluster.
4+
Machine configuration operation is used to configure [Red Hat Enterprise Linux CoreOS (RHCOS)](https://docs.openshift.com/container-platform/4.13/architecture/architecture-rhcos.html) on each node in a RHOCP cluster.
55

66
[Machine config operator](https://github.com/openshift/machine-config-operator) (MCO) is provided by Red Hat to manage the operating system and machine configuration. In this project through the MCO, cluster administrators can configure and update the kernel to provision Intel Hardware features on the worker nodes.
77

8-
MCO is one of the technologies used in this project to manage the machine configuration. In current OCP-4.12, MCO might reboot the node to enable the machine configuration. Since rebooting the node is undesirable, alternative machine configuration technologies are under investigation. For more details, see this [issue](https://github.com/intel/intel-technology-enabling-for-openshift/issues/34).
8+
MCO is one of the technologies used in this project to manage the machine configuration. In current OCP, MCO might reboot the node to enable the machine configuration. Since rebooting the node is undesirable, alternative machine configuration technologies are under investigation. For more details, see this [issue](https://github.com/intel/intel-technology-enabling-for-openshift/issues/34).
99

1010
The best approach is to work with the RHCOS team to push the RHCOS configuration as the default configuration for a RHOCP cluster on [Day 0](https://www.ibm.com/cloud/architecture/content/course/red-hat-openshift-container-platform-day-2-ops/).
1111

@@ -16,7 +16,7 @@ If the configuration cannot be set as the default setting, we recommend using so
1616
Any contribution in this area is welcome.
1717

1818
# Prerequisites
19-
- Provisioned RHOCP 4.12 cluster. Follow steps [here](/README.md#provisioning-rhocp-cluster).
19+
- Provisioned RHOCP cluster. Follow steps [here](/README.md#provisioning-rhocp-cluster).
2020
- Setup node feature discovery (NFD). Follow steps [here](/nfd/README.md).
2121

2222
# General configuration
@@ -70,22 +70,21 @@ intel-dgpu rendered-intel-dgpu-58fb5f4d72fe6041abb066880e112acd True Fa
7070
```
7171
Ensure `intel-dgpu` MachineConfigPool is present.
7272

73-
# Disable conflicting driver
74-
Run the command shown below to disable the loading of a potential conflicting driver, such as `ast` driver.
75-
76-
**Note**: The `i915` driver depends on a ported `drm` module. Some other drivers, such as ast that depends on in-tree drm module might have a compatibility issue. The known issue will be resolved on i915 driver for RHEL `9.x`, which will be used for RHOCP `4.13`.
73+
# Disable in-tree drivers
74+
Run the command shown below to disable the loading of in-tree drivers 'i915' and 'intel_vsec'.
7775
```
78-
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/machine_configuration/100-intel-dgpu-machine-config-disable-ast.yaml
76+
$ oc apply -f https://raw.githubusercontent.com/intel/intel-technology-enabling-for-openshift/main/machine_configuration/100-intel-dgpu-machine-config-disable-intree-i915-vsec.yaml
7977
```
8078
**Note**: This command will reboot the worker nodes in the `intel-dgpu` MachineConfigPool sequentially.
8179

8280
## Verification
8381
Navigate to the node terminal on the web console (Compute -> Nodes -> Select a node -> Terminal). Run the following commands in the terminal.
8482
```
8583
$ chroot /host
86-
$ lsmod | grep ast
84+
$ lsmod | grep i915
85+
$ lsmod | grep intel_vsec
8786
```
88-
Ensure that ast driver is not loaded.
87+
Ensure that the in-tree i915 and intel_vsec driver is not loaded.
8988

9089
# Machine Configuration for Provisioning Intel® QAT
9190

0 commit comments

Comments
 (0)