mtpti5iD/redhat-docs_dataset huggingface dataset:
9.4. NUMA-Aware Kernel SamePage Merging (KSM) Kernel SamePage Merging (KSM) allows virtual machines to share identical memory pages. From Red Hat Enterprise Linux 6.5, KSM can detect that a system is using NUMA memory and control merging pages across different NUMA nodes. Use the sysfs /sys/kernel/mm/ksm/merge_across_nodes parameter to control merging of pages across different NUMA nodes. By default, pages from all nodes can be merged together. When this parameter is set to zero, only pages from the same node are merged. Generally, unless you are oversubscribing the system memory, you will get better runtime performance by disabling KSM sharing. Important When KSM merges across nodes on a NUMA host with multiple guest virtual machines, guests and CPUs from more distant nodes can suffer a significant increase of access latency to the merged KSM page. To instruct the hypervisor to disable share pages for a guest, add the following to the guest's XML: For more information about tuning memory settings with the <memoryBacking> element, see Section 8.3.2, "Memory Tuning with virsh" .

Commands:
<memoryBacking> <nosharepages/> </memoryBacking>
1.2. KVM Hypervisor Requirements The KVM hypervisor requires: an Intel processor with the Intel VT-x and Intel 64 virtualization extensions for x86-based systems; or an AMD processor with the AMD-V and the AMD64 virtualization extensions. Virtualization extensions (Intel VT-x or AMD-V) are required for full virtualization. Enter the following commands to determine whether your system has the hardware virtualization extensions, and that they are enabled. Procedure 1.1. Verifying virtualization extensions Verify the CPU virtualization extensions are available enter the following command to verify the CPU virtualization extensions are available: Analyze the output The following example output contains a vmx entry, indicating an Intel processor with the Intel VT-x extension: The following example output contains an svm entry, indicating an AMD processor with the AMD-V extensions: If the grep -E 'svm|vmx' /proc/cpuinfo command returns any output, the processor contains the hardware virtualization extensions. In some circumstances, manufacturers disable the virtualization extensions in the BIOS. If the extensions do not appear, or full virtualization does not work, see Procedure A.3, "Enabling virtualization extensions in BIOS" for instructions on enabling the extensions in your BIOS configuration utility. Ensure the KVM kernel modules are loaded As an additional check, verify that the kvm modules are loaded in the kernel with the following command: If the output includes kvm_intel or kvm_amd , the kvm hardware virtualization modules are loaded. Note The virsh utility (provided by the libvirt-client package) can output a full list of your system's virtualization capabilities with the following command:

Commands:
grep -E 'svm|vmx' /proc/cpuinfo
flags : fpu tsc msr pae mce cx8 vmx apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext svm fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8legacy ts fid vid ttp tm stc
lsmod | grep kvm
virsh capabilities
Chapter 6. Publishing and running your playbooks in Ansible Automation Platform The following procedures describe how to deploy your new playbooks in your instance of Ansible Automation Platform so that you can use them to run automation jobs. 6.1. Saving your project in SCM Save your playbook project as a repository in your source control management system, for example GitHub. Procedure Initialize your project directory as a git repository. Push your project up to a source control system such as GitHub. 6.2. Running your playbook in Ansible Automation Platform To run your playbook in Ansible Automation Platform, you must create a project in automation controller for the repository where you stored your playbook project. You can then create a job template for each playbook from the project. Procedure In a browser, log in to automation controller. Configure a Source Control credential type for your source control system if necessary. See the Creating new credentials section of Using automation execution for more details. https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/using_automation_execution/controller-credentials#controller-create-credential In automation controller, create a project for the GitHub repository where you stored your playbook project. Refer to the Projects chapter of Using automation execution . Create a job template that uses a playbook from the project that you created. Refer to the Job Templates chapter of Using automation execution . Run your playbook from automation controller by launching the job template. Refer to the Launching a job template section of Using automation execution .

Commands:
17.6. Advanced RAID Device Creation In some cases, you may wish to install the operating system on an array that can't be created after the installation completes. Usually, this means setting up the /boot or root file system arrays on a complex RAID device; in such cases, you may need to use array options that are not supported by Anaconda . To work around this, perform the following procedure: Procedure 17.1. Advanced RAID device creation Insert the install disk as you normally would. During the initial boot up, select Rescue Mode instead of Install or Upgrade . When the system fully boots into Rescue mode , the user will be presented with a command line terminal. From this terminal, use parted to create RAID partitions on the target hard drives. Then, use mdadm to manually create raid arrays from those partitions using any and all settings and options available. For more information on how to do these, refer to Chapter 13, Partitions , man parted , and man mdadm . Once the arrays are created, you can optionally create file systems on the arrays as well. Refer to Section 11.2, "Overview of Supported File Systems" for basic technical information on file systems supported by Red Hat Enterprise Linux 6. Reboot the computer and this time select Install or Upgrade to install as normal. As Anaconda searches the disks in the system, it will find the pre-existing RAID devices. When asked about how to use the disks in the system, select Custom Layout and click . In the device listing, the pre-existing MD RAID devices will be listed. Select a RAID device, click Edit and configure its mount point and (optionally) the type of file system it should use (if you did not create one earlier) then click Done . Anaconda will perform the install to this pre-existing RAID device, preserving the custom options you selected when you created it in Rescue Mode . Note The limited Rescue Mode of the installer does not include man pages. Both the man mdadm and man md contain useful information for creating custom RAID arrays, and may be needed throughout the workaround. As such, it can be helpful to either have access to a machine with these man pages present, or to print them out prior to booting into Rescue Mode and creating your custom arrays.

Commands:
Chapter 2. Making Media Use the methods described in this section to create the following types of installation and boot media: an installation DVD a minimal boot CD or DVD that can boot the installer a USB flash drive to boot the installer 2.1. Making an Installation DVD You can make an installation DVD using the CD or DVD burning software on your computer. Make sure that your disc burning software is capable of burning discs from image files. Although this is true of most disc burning software, exceptions exist. In particular, note that the disc burning feature built into Windows XP and Windows Vista cannot burn DVDs; and that earlier Windows operating systems did not have any disc burning capability installed by default at all. Therefore, if your computer has a Windows operating system prior to Windows 7 installed on it, you need separate software for this task. Examples of popular disc burning software for Windows that you might already have on your computer include Nero Burning ROM and Roxio Creator . Most widely used disc burning software for Linux, such as Brasero and K3b has the built-in ability to burn discs from ISO image files. The exact series of steps that produces a DVD from an ISO image file varies greatly from computer to computer, depending on the operating system and disc burning software installed. Consult your disc burning software's documentation for detailed information on burning DVDs.

Commands:
Chapter 5. Running .NET 6.0 applications in containers Use the ubi8/dotnet-60-runtime image to run a precompiled application inside a Linux container. Prerequisites Preconfigured containers. The following example uses podman. Procedure Optional: If you are in another project's directory and do not wish to create a nested project, return to the parent directory of the project: Create a new MVC project in a directory called mvc_runtime_example : Publish the project: Create the Dockerfile : Build your image: Run your image: Verification steps View the application running in the container:

Commands:
cd ..
dotnet new mvc --output mvc_runtime_example
dotnet publish mvc_runtime_example -f net6.0 -c Release
cat > Dockerfile <<EOF FROM registry.access.redhat.com/ubi8/dotnet-60-runtime ADD bin/Release/net6.0/publish/ . CMD ["dotnet", "mvc_runtime_example.dll"] EOF
podman build -t dotnet-60-runtime-example .
podman run -d -p8080:8080 dotnet-60-runtime-example
xdg-open http://127.0.0.1:8080
12.3.4. Deleting a Storage Pool Using virsh The following demonstrates how to delete a storage pool using virsh: To avoid any issues with other guest virtual machines using the same pool, it is best to stop the storage pool and release any resources in use by it. Optionally, if you want to remove the directory where the storage pool resides use the following command: Remove the storage pool's definition

Commands:
virsh pool-destroy guest_images_disk
virsh pool-delete guest_images_disk
virsh pool-undefine guest_images_disk
8.6. batik 8.6.1. RHBA-2013:1530 - batik bug fix update Updated batik packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The batik packages provide the Batik toolkit based on a Java technology. This toolkit is used by applications that require to use images in the Scalable Vector Graphics (SVG) format for various purposes, such as viewing, generation, or manipulation. Bug Fixes BZ# 631677 This update removes the empty batik-debuginfo package. BZ# 867701 , BZ# 995471 Previously, an attempt to use the rasterizer utility to convert an SVG image to the JPEG format caused an error to be returned. This update applies a patch to fix this bug and rasterizer now converts SVG images to the JPEG format correctly. BZ# 883464 Previously, the manifest.mf file included the keyword "version" instead of "bundle-version". Consequently, the Eclipse platform did not work correctly with Batik utilities. This bug has been fixed and Eclipse now works as expected. BZ# 979527 , BZ# 995471 Due to a bug in the underlying source code, an attempt to use the ttf2svg font converter failed with an exception. This update applies a patch to fix this bug and ttf2svg now works correctly. BZ# 995471 Previously, the batik packages contained many bugs, among others classpath errors and errors connected with a missing module for handling the JPEG format. Consequently, Batik utilities, such as raterizer, svgpp, and ttf2svg, failed with exceptions. With this update, the underlying source code has been modified to fix these bugs and the aforementioned utilities now work as expected. Users of batik are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 4. User-managed encryption for IBM Cloud By default, provider-managed encryption is used to secure the following when you deploy an OpenShift Container Platform cluster: The root (boot) volume of control plane and compute machines Persistent volumes (data volumes) that are provisioned after the cluster is deployed You can override the default behavior by specifying an IBM(R) Key Protect for IBM Cloud(R) (Key Protect) root key as part of the installation process. When you bring our own root key, you modify the installation configuration file ( install-config.yaml ) to specify the Cloud Resource Name (CRN) of the root key by using the encryptionKey parameter. You can specify that: The same root key be used be used for all cluster machines. You do so by specifying the key as part of the cluster's default machine configuration. When specified as part of the default machine configuration, all managed storage classes are updated with this key. As such, data volumes that are provisioned after the installation are also encrypted using this key. Separate root keys be used for the control plane and compute machine pools. For more information about the encryptionKey parameter, see Additional IBM Cloud configuration parameters . Note Make sure you have integrated Key Protect with your IBM Cloud Block Storage service. For more information, see the Key Protect documentation . 4.1. steps Install an OpenShift Container Platform cluster: Installing a cluster on IBM Cloud with customizations Installing a cluster on IBM Cloud with network customizations Installing a cluster on IBM Cloud into an existing VPC Installing a private cluster on IBM Cloud

Commands:
7.8. Creating Audit Reports The aureport utility allows you to generate summary and columnar reports on the events recorded in Audit log files. By default, all audit.log files in the /var/log/audit/ directory are queried to create the report. You can specify a different file to run the report against using the aureport options -if file_name command. Example 7.8. Using aureport to Generate Audit Reports To generate a report for logged events in the past three days excluding the current example day, use the following command: To generate a report of all executable file events, use the following command: To generate a summary of the executable file event report above, use the following command: To generate a summary report of failed events for all users, use the following command: To generate a summary report of all failed login attempts per each system user, use the following command: To generate a report from an ausearch query that searches all file access events for user ID 1000 , use the following command: To generate a report of all Audit files that are queried and the time range of events they include, use the following command: For a full listing of all aureport options, see the aureport (8) man page.

Commands:
~]# aureport --start 04/08/2013 00:00:00 --end 04/11/2013 00:00:00
~]# aureport -x
~]# aureport -x --summary
~]# aureport -u --failed --summary -i
~]# aureport --login --summary -i
~]# ausearch --start today --loginuid 1000 --raw | aureport -f --summary
~]# aureport -t
18.6. Welcome Screen and Language Selection The first screen of the installation program is the Welcome to Red Hat Enterprise Linux screen. Here you select the language that Anaconda will use for the rest of the installation. This selection will also become the default for the installated system, unless changed later. In the left panel, select your language of choice, for example English . Then you can select a locale specific to your region in the right panel, for example English (United States) . Note One language is pre-selected by default on top of the list. If network access is configured at this point (for example, if you booted from a network server instead of local media), the pre-selected language will be determined based on automatic location detection using the GeoIP module. Alternatively, type your preferred language into the search box as shown below. Once you have made your selection, click the Continue button to proceed to the Installation Summary screen. Figure 18.3. Language Configuration After you click the Continue button, the unsupported hardware dialog may appear. This happens if you are using hardware that the kernel does not support.

Commands:
Chapter 1. Service Mesh 3.x 1.1. Service Mesh overview Red Hat OpenShift Service Mesh manages and secures communication between microservices by providing traffic management, advanced routing, and load balancing. Red Hat OpenShift Service Mesh also enhances security through features like mutual TLS, and offers observability with metrics, logging, and tracing to monitor and troubleshoot applications. Note Because Red Hat OpenShift Service Mesh 3.0 releases on a different cadence from OpenShift Container Platform, the Service Mesh documentation is available as a separate documentation set at Red Hat OpenShift Service Mesh .

Commands:
30.3. Downloading the Upgraded Kernel There are several ways to determine if an updated kernel is available for the system. Security Errata - See http://www.redhat.com/security/updates/ for information on security errata, including kernel upgrades that fix security issues. The Red Hat Network - For a system subscribed to the Red Hat Network, the yum package manager can download the latest kernel and upgrade the kernel on the system. The Dracut utility will create an initial RAM disk image if needed, and configure the boot loader to boot the new kernel. For more information on installing packages from the Red Hat Network, see Chapter 8, Yum . For more information on subscribing a system to the Red Hat Network, see Chapter 6, Registering the System and Managing Subscriptions . If yum was used to download and install the updated kernel from the Red Hat Network, follow the instructions in Section 30.5, "Verifying the Initial RAM Disk Image" and Section 30.6, "Verifying the Boot Loader" , only do not change the kernel to boot by default. Red Hat Network automatically changes the default kernel to the latest version. To install the kernel manually, continue to Section 30.4, "Performing the Upgrade" .

Commands:
Chapter 5. Enabling notifications and integrations You can enable the notifications service on Red Hat Hybrid Cloud Console to send notifications whenever the advisor service detects an issue and generates a recommendation. Using the notifications service frees you from having to continually check the Red Hat Insights for RHEL dashboard for recommendations. For example, you can configure the notifications service to automatically send an email message whenever the advisor service generates a recommendation. 5.1. Requirements for enabling notifications Enabling the notifications service requires three main steps: First, an Organization Administrator creates a User access group with the Notifications administrator role, and then adds account members to the group. , a Notifications administrator sets up behavior groups for events in the notifications service. Behavior groups specify the delivery method for each notification. For example, a behavior group can specify whether email notifications are sent to all users, or just to Organization administrators. Finally, users who receive email notifications from events must set their user preferences so that they receive individual emails for each event. In addition to sending email messages, you can configure the notifications service to send event data in other ways: Using an authenticated client to query Red Hat Insights APIs for event data Using webhooks to send events to third-party applications that accept inbound requests Integrating notifications with applications such as Splunk to route advisor recommendations to the application dashboard Additional resources For more information about how to set up notifications for Advisor recommendations, see Configuring notifications on the Red Hat Hybrid Cloud Console and Integrating the Red Hat Hybrid Cloud Console with third-party applications .

Commands:
Appendix F. Securing Red Hat Virtualization This information is specific to Red Hat Virtualization. It does not cover fundamental security practices related to any of the following: Disabling unnecessary services Authentication Authorization Accounting Penetration testing and hardening of non-RHV services Encryption of sensitive application data Prerequisites You should be proficient in your organization's security standards and practices. If possible, consult with your organization's Security Officer. Consult the Red Hat Enterprise Linux Security hardening before deploying RHEL hosts. F.1. Applying the DISA STIG profile in RHEL based hosts and the standalone Manager When installing RHV, you can select the DISA STIG profile with the UI installer, which is the profile provided by RHEL 8. Important The DISA STIG profile is not supported for Red Hat Virtualization Host (RHVH). Procedure In the Installation Summary screen, select Security Policy . In the Security Policy screen, set the Apply security policy to On . Select DISA STIG for Red Hat Enterprise Linux 8 . Click Select profile . This action adds a green checkmark to the profile and adds packages to the list of Changes that were done or need to be done . Follow the onscreen instructions if they direct you to make any changes. Click Done . On the Installation Summary screen, verify that the status of Security Policy is Everything okay . Reboot the host. F.1.1. Enabling DISA STIG in a self-hosted engine You can enable DISA STIG in a self-hosted engine during deployment when using the command-line. Procedure Start the self-hosted engine deployment script. See Installing Red Hat Virtualization as a self-hosted engine using the command line . When the deployment script prompts Do you want to apply an OpenSCAP security profile? , enter Yes . When the deployment script prompts Please provide the security profile you would like to use? , enter stig . F.2. Applying the PCI-DSS profile in RHV hosts and the standalone Manager When installing RHVH, you can select the PCI-DSS profile with the UI installer, which is the profile provided by RHEL 8. Procedure In the Installation Summary screen, select Security Policy . In the Security Policy screen, set the Apply security policy to On . Select PCI-DSS v3.2.1 Control Baseline for Red Hat Enterprise Linux 8 . Click Select profile . This action adds a green checkmark to the profile and adds packages to the list of Changes that were done or need to be done . Follow the onscreen instructions if they direct you to make any changes. Click Done . In the Installation Summary screen, verify that the status of Security Policy is Everything okay . Reboot the host. F.2.1. Enabling PCI-DSS in a self-hosted engine You can enable PCI-DSS in a self-hosted engine during deployment when using the command-line. Procedure Start the self-hosted engine deployment script. See Installing Red Hat Virtualization as a self-hosted engine using the command line . When the deployment script prompts Do you want to apply an OpenSCAP security profile? , enter Yes . When the deployment script prompts Please provide the security profile you would like to use? , enter pci-dss .

Commands: