You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Copy file name to clipboardExpand all lines: machine_configuration/README.md
+9-10Lines changed: 9 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
# Setting up Machine Configuration
2
2
3
3
# 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.
5
5
6
6
[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.
7
7
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).
9
9
10
10
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/).
11
11
@@ -16,7 +16,7 @@ If the configuration cannot be set as the default setting, we recommend using so
@@ -70,22 +70,21 @@ intel-dgpu rendered-intel-dgpu-58fb5f4d72fe6041abb066880e112acd True Fa
70
70
```
71
71
Ensure `intel-dgpu` MachineConfigPool is present.
72
72
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'.
0 commit comments