Description of problem:

https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html-single/installing_on_bare_metal/index#preparing-the-provisioner-node-for-openshift-install_ipi-install-installation-workflow

The BareMetal IPI documentation instructs users to install libvirt and configure user permissions, but does not explicitly state that the `libvirtd.service` must be running on the provisioner host before running `openshift-install`.

On modern RHEL systems, libvirt may be installed while the `libvirtd` service remains inactive by default. In this state, the libvirt UNIX socket (`/var/run/libvirt/libvirt-sock`) does not exist, causing the OpenShift installer to fail during early platform provisioning checks.

Observed Impact:

When `libvirtd.service` is installed but not running, the installer fails with errors such as:

failed to generate asset "Platform Provisioning Check":
platform.baremetal.libvirtURI: failed to connect to libvirt:
dial unix /var/run/libvirt/libvirt-sock: no such file or directory

This failure occurs before any bare-metal hosts are provisioned and is not clearly attributable to the libvirt service state, according to the documentation.

Expected Behavior / Clarification:

The documentation should clearly state that:

• `libvirtd.service` must be running and reachable
• The libvirt socket must exist at `/var/run/libvirt/libvirt-sock`
• This requirement must be met before running `openshift-install`

Suggested Documentation Update:

Add an explicit validation step, for example:

sudo systemctl enable --now libvirtd
systemctl is-active libvirtd
ls -l /var/run/libvirt/libvirt-sock

Optionally include a note explaining that socket activation alone is insufficient if the service is not active.

Version-Release number of selected component (if applicable):

4.20.z