mtpti5iD/redhat-docs_dataset huggingface dataset:
21.11. KVM Networking Performance By default, KVM virtual machines are assigned a virtual Realtek 8139 (rtl8139) NIC (network interface controller). Whereas Red Hat Enterprise Linux guests are assigned a virtio NIC by default, Windows guests or the guest type is not specified. The rtl8139 virtualized NIC works fine in most environments,but this device can suffer from performance degradation problems on some networks, such as a 10 Gigabit Ethernet. To improve performance, you can switch to the paravirtualized network driver. Note Note that the virtualized Intel PRO/1000 ( e1000 ) driver is also supported as an emulated driver choice. To use the e1000 driver, replace virtio in the procedure below with e1000 . For the best performance it is recommended to use the virtio driver. Procedure 21.4. Switching to the virtio driver Shutdown the guest operating system. Edit the guest's configuration file with the virsh command (where GUEST is the guest's name): The virsh edit command uses the USDEDITOR shell variable to determine which editor to use. Find the network interface section of the configuration. This section resembles the snippet below: Change the type attribute of the model element from 'rtl8139' to 'virtio' . This will change the driver from the rtl8139 driver to the e1000 driver. Save the changes and exit the text editor Restart the guest operating system. Creating New Guests Using Other Network Drivers Alternatively, new guests can be created with a different network driver. This may be required if you are having difficulty installing guests over a network connection. This method requires you to have at least one guest already created (possibly installed from CD or DVD) to use as a template. Create an XML template from an existing guest (in this example, named Guest1 ): Copy and edit the XML file and update the unique fields: virtual machine name, UUID, disk image, MAC address, and any other unique parameters. Note that you can delete the UUID and MAC address lines and virsh will generate a UUID and MAC address. Add the model line in the network interface section: Create the new virtual machine:

Commands:
virsh edit GUEST
<interface type='network'> [output truncated] <model type='rtl8139' /> </interface>
<interface type='network'> [output truncated] <model type= 'virtio' /> </interface>
virsh dumpxml Guest1 > /tmp/ guest-template .xml
cp /tmp/ guest-template .xml /tmp/ new-guest .xml vi /tmp/ new-guest .xml
<interface type='network'> [output truncated] <model type='virtio' /> </interface>
virsh define /tmp/new-guest.xml virsh start new-guest
6.6. Insufficient Free Extents for a Logical Volume You may get the error message "Insufficient free extents" when creating a logical volume when you think you have enough extents based on the output of the vgdisplay or vgs commands. This is because these commands round figures to 2 decimal places to provide human-readable output. To specify exact size, use free physical extent count instead of a multiple of bytes to determine the size of the logical volume. The vgdisplay command, by default, includes this line of output that indicates the free physical extents. Alternately, you can use the vg_free_count and vg_extent_count arguments of the vgs command to display the free extents and the total number of extents. With 8780 free physical extents, you can enter the following command, using the lower-case l argument to use extents instead of bytes: This uses all the free extents in the volume group. Alternately, you can extend the logical volume to use a percentage of the remaining free space in the volume group by using the -l argument of the lvcreate command. For information, see Section 4.4.1, "Creating Linear Logical Volumes" .

Commands:
vgdisplay --- Volume group --- Free PE / Size 8780 / 34.30 GB
vgs -o +vg_free_count,vg_extent_count VG #PV #LV #SN Attr VSize VFree Free #Ext testvg 2 0 0 wz--n- 34.30G 34.30G 8780 8780
lvcreate -l 8780 -n testlv testvg
vgs -o +vg_free_count,vg_extent_count VG #PV #LV #SN Attr VSize VFree Free #Ext testvg 2 1 0 wz--n- 34.30G 0 0 8780
Chapter 7. Federal Information Processing Standard (FIPS) Red Hat Ceph Storage uses FIPS validated cryptography modules when run on Red Hat Enterprise Linux 7.6 or Red Hat Enterprise Linux 8.1, or Red Hat Enterprise Linux 8.2. Enable FIPS mode on Red Hat Enterprise Linux either during system installation or after it. For bare-metal deployments, follow the instructions in the Red Hat Enterprise Linux 8 Security Hardening Guide . For container deployments, follow the instructions in the Red Hat Enterprise Linux 8 Security Hardening Guide . Additional Resources Refer to the US Government Standards to know the latest information on FIPS validations.

Commands:
Chapter 4. Kafka 4 impact and adoption schedule Streams for Apache Kafka 3.0 is scheduled for release in 2025. The introduction of Apache Kafka 4 in the release brings significant changes to how Kafka clusters are deployed, configured, and operated. For more information on how these changes affect the Streams for Apache Kafka 3.0 release, refer to the article Streams for Apache Kafka 3.0: Kafka 4 Impact and Adoption .

Commands:
8.184. rpm 8.184.1. RHBA-2013:1665 - rpm bug fix update Updated rpm packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The RPM Package Manager (RPM) is a command-line driven package management system capable of installing, uninstalling, verifying, querying, and updating software packages. Bug Fixes BZ# 868332 Previously, the brp-python-bytecompile script skipped those paths that included "/usr/lib.*/python.+/" string. Consequently, when creating an RPM that contained Python modules in paths (like "/opt/myapp/usr/lib64/python2.6/site-packages/mypackage/"), bytecode was not created. The reproducer specification has been changed, and bytecode is now created for all paths. BZ# 904818 When wildcard characters were used with the "%caps" tag in the spec file, the rpmbuild utility terminated unexpectedly. The provided patch corrects the problem by making a copy of the caps data for each file it applies to, and thus rpmbuild no longer crashes in the described scenario. BZ# 919435 Previously, when installing a package with a high (80k) number of files, the RPM Package Manager terminated unexpectedly with a segmentation fault. As a workaround, the segmentation fault has been replaced with an error message when a package with a high number of files fails to install. BZ# 920190 Previously the rpm program attempted to unconditionally process any "%include" directive it found in a spec file, either leading to unwanted content in the package or error messages. The updated rpm package properly honours various spec conditionals for "%include". BZ# 963724 With this update, Red Hat Enterprise Linux 5 backwards-compatibility option, "%_strict_script_errors macro", has been added. The default behavior of Red Hat Enterprise Linux 6 does not change with this update and users that do not demand this option specifically are not advised to use it. Users of rpm are advised to upgrade to these updated packages, which fix these bugs. All running applications linked against the RPM library must be restarted for this update to take effect.

Commands:
Chapter 2. Eclipse Temurin features Eclipse Temurin does not contain structural changes from the upstream distribution of OpenJDK. For the list of changes and security fixes that the latest OpenJDK 11 release of Eclipse Temurin includes, see OpenJDK 11.0.24 Released . New features and enhancements Review the following release notes to understand new features and feature enhancements included with the Eclipse Temurin 11.0.24 release: DTLS 1.0 is disabled by default OpenJDK 9 introduced support for both version 1.0 and version 1.2 of the Datagram Transport Layer Security (DTLS) protocol ( JEP-219 ). DTLSv1.0, which is based on TLS 1.1, is no longer recommended for use, because this protocol is considered weak and insecure by modern standards. In OpenJDK 11.0.24, if you attempt to use DTLSv1.0, the JDK throws an SSLHandshakeException by default. If you want to continue using DTLSv1.0, you can remove DTLSv1.0 from the jdk.tls.disabledAlgorithms system property either by modifying the java.security configuration file or by using the java.security.properties system property. Note Continued use of DTLSv1.0 is not recommended and is at the user's own risk. See JDK-8256660 (JDK Bug System) . RPATH preferred over RUNPATH for USDORIGIN runtime search paths in internal JDK binaries Native executables and libraries in the JDK use embedded runtime search paths (rpaths) to locate required internal JDK native libraries. On Linux systems, binaries can specify these search paths by using either DT_RPATH or DT_RUNPATH : If a binary specifies search paths by using DT_RPATH , these paths are searched before any paths that are specified in the LD_LIBRARY_PATH environment variable. If a binary specifies search paths by using DT_RUNPATH , these paths are searched only after paths that are specified in LD_LIBRARY_PATH . This means that the use of DT_RUNPATH can allow JDK internal libraries to be overridden by any libraries of the same name that are specified in LD_LIBRARY_PATH , which is undesirable from a security perspective. In earlier releases, the type of runtime search path used was based on the default search path for the dynamic linker. In OpenJDK 11.0.24, to ensure that DT_RPATH is used, the --disable-new-dtags option is explicitly passed to the linker. See JDK-8326891 (JDK Bug System) . GlobalSign R46 and E46 root certificates added In OpenJDK 11.0.24, the cacerts truststore includes two GlobalSign TLS root certificates: Certificate 1 Name: GlobalSign Alias name: globalsignr46 Distinguished name: CN=GlobalSign Root R46, O=GlobalSign nv-sa, C=BE Certificate 2 Name: GlobalSign Alias name: globalsigne46 Distinguished name: CN=GlobalSign Root E46, O=GlobalSign nv-sa, C=BE See JDK-8316138 (JDK Bug System) . Revised on 2024-08-02 13:32:25 UTC

Commands:
Part I. Creating and managing manifests A manifest is a set of encrypted files containing information about your subscriptions. You can use a manifest to import your subscriptions into Red Hat Satellite. After the manifest is imported, you can use it to manage RHEL systems and synchronize content. An authorized Satellite user on a connected network can create, export, delete, and modify manifests from Red Hat Hybrid Cloud Console. Note Users on a connected network create and manage their subscription manifests on the Red Hat Hybrid Cloud Console, however, users on a disconnected network must use the Customer Portal. For more information, see Using manifests for a disconnected Satellite Server .

Commands:
Chapter 3. The gofmt formatting tool Instead of a style guide, the Go programming language uses the gofmt code formatting tool. gofmt automatically formats your code according to the Go layout rules. 3.1. Prerequisites Go Toolset is installed. For more information, see Installing Go Toolset . 3.2. Formatting code You can use the gofmt formatting tool to format code in a given path. When the path leads to a single file, the changes apply only to the file. When the path leads to a directory, all .go files in the directory are processed. Procedure To format your code in a given path, run: On Red Hat Enterprise Linux 8: Replace < code_path > with the path to the code you want to format. On Red Hat Enterprise Linux 9: Replace < code_path > with the path to the code you want to format. Note To print the formatted code to standard output instead of writing it to the original file, omit the -w option. 3.3. Previewing changes to code You can use the gofmt formatting tool to preview changes done by formatting code in a given path. The output in unified diff format is printed to standard output. Procedure To show differences in your code in a given path, run: On Red Hat Enterprise Linux 8: Replace < code_path > with the path to the code you want to compare. On Red Hat Enterprise Linux 9: Replace < code_path > with the path to the code you want to compare. 3.4. Simplifying code You can use the gofmt formatting tool to simplify your code. Procedure To simplify code in a given path, run: On Red Hat Enterprise Linux 8: Replace < code_path > with the path to the code you want to simplify. On Red Hat Enterprise Linux 9: Replace < code_path > with the path to the code you want to simplify. To apply the changes, run: On Red Hat Enterprise Linux 8: Replace < code_path > with the path to the code you want to format. On Red Hat Enterprise Linux 9: Replace < code_path > with the path to the code you want to format. 3.5. Refactoring code You can use the gofmt formatting tool to refactor your code by applying arbitrary substitutions. Procedure To refactor your code in a given path, run: On Red Hat Enterprise Linux 8: Replace < code_path > with the path to the code you want to refactor and < rewrite_rule > with the rule you want it to be rewritten by. On Red Hat Enterprise Linux 9: Replace < code_path > with the path to the code you want to refactor and < rewrite_rule > with the rule you want it to be rewritten by. To apply the changes, run: On Red Hat Enterprise Linux 8: Replace < code_path > with the path to the code you want to format. On Red Hat Enterprise Linux 9: Replace < code_path > with the path to the code you want to format. 3.6. Additional resources The official gofmt documentation .

Commands:
gofmt -w < code_path >
gofmt -w < code_path >
gofmt -d < code_path >
gofmt -d < code_path >
gofmt -s -w < code_path >
gofmt -s -w < code_path >
gofmt -w < code_path >
gofmt -w < code_path >
gofmt -r -w < rewrite_rule > < code_path >
gofmt -r -w < rewrite_rule > < code_path >
gofmt -w < code_path >
gofmt -w < code_path >
7.3. Run Red Hat JBoss Data Grid in Clustered Mode Clustered mode refers to a cluster made up of two or more Red Hat JBoss Data Grid instances. Run the following script to start JBoss Data Grid in clustered mode: This command starts JBoss Data Grid using the default configuration information provided in the USDJDG_HOME/standalone/configuration/ clustered.xml file. Report a bug

Commands:
USDJDG_HOME/bin/clustered.sh
Chapter 15. Infrastructure services The following chapter contains the most notable changes to infrastructure services between RHEL 8 and RHEL 9. 15.1. Notable changes to infrastructure services Support for Berkeley DB dynamic back end has been removed With this release, the Berkeley DB ( libdb ) dynamic back end is no longer supported. The named-sdb build is no longer provided. You can use the DLZ loadable plugins for each back end, for example, sqlite3 or mysql . Those plugins are not built or shipped and have to be built from the source. The mod_php module provided with PHP for use with the Apache HTTP Server has been removed The mod_php module provided with PHP for use with the Apache HTTP Server is no longer available in RHEL 9. Since RHEL 8, PHP scripts are run using the FastCGI Process Manager ( php-fpm ) by default. For more information, see Using PHP with the Apache HTTP Server . The BIND 9.18 is now supported in RHEL BIND 9.18 has been added in RHEL 9.5 in the new bind9.18 package. The notable feature enhancements include the following: Added support for DNS over TLS (DoT) and DNS over HTTPS (DoH) in the `named`daemon Added support for both incoming and outgoing zone transfers over TLS Improved support for OpenSSL 3.0 interfaces New configuration options for tuning TCP and UDP send and receive buffers Various improvements to the dig utility

Commands:
4. Known Issues 4.1. Installer In some circumstances, disks that contain a whole disk format (e.g. a LVM Physical Volume populating a whole disk) are not cleared correctly using the clearpart --initlabel kickstart command. Adding the --all switch - as in clearpart --initlabel --all - ensures disks are cleared correctly. During the installation on POWER systems, the error messages similar to: may be returned to sys.log . The errors do not prevent installation and only occur during initial setup. The filesystem created by the installer will function correctly. When installing on the IBM System z architecture, if the installation is being performed over SSH, avoid resizing the terminal window containing the SSH session. If the terminal window is resized during installation, the installer will exit and installation will terminate. The kernel image provided on the CD/DVD is too large for Open Firmware. Consequently, on the POWER architecture, directly booting the kernel image over a network from the CD/DVD is not possible. Instead, use yaboot to boot from a network. The anaconda partition editing interface includes a button labeled Resize . This feature is intended for users wishing to shrink an existing filesystem and underlying volume to make room for installation of the new system. Users performing manual partitioning cannot use the Resize button to change sizes of partitions as they create them. If you determine a partition needs to be larger than you initially created it, you must delete the first one in the partitioning editor and create a new one with the larger size. Channel IDs(read, write, data) for network devices are required for defining and configuring network devices on s390 systems. However, system-config-kickstart - the graphical user interface for generating a kickstart configuration - cannot define channel IDs for a network device. To work around this issue, manually edit the kickstart configuration that system-config-kickstart generates to include the desired network devices.

Commands:
attempt to access beyond end of device loop0: rw=0, want=248626, limit=248624
Chapter 52. Updated Drivers Storage Driver Updates The aacraid driver has been updated to version 1.2.1[50792]-custom. The lpfc driver has been updated to version 0:11.2.0.6. The vmw_pvscsi driver has been updated to version 1.0.7.0-k. The megaraid_sas driver has been updated to version 07.701.17.00-rh1. The bfa driver has been updated to version 3.2.25.1. The hpsa driver has been updated to version 3.4.18-0-RH1. The be2iscsi driver has been updated to version 11.2.1.0. The qla2xxx driver has been updated to version 8.07.00.38.07.4-k1. The mpt2sas driver has been updated to version 20.103.00.00. The mpt3sas driver has been updated to version 15.100.00.00. Network Driver Updates The ntb driver has been updated to version 1.0. The igbvf driver has been updated to version 2.4.0-k. The igb driver has been updated to version 5.4.0-k. The ixgbevf driver has been updated to version 3.2.2-k-rh7.4. The i40e driver has been updated to version 1.6.27-k. The fm10k driver has been updated to version 0.21.2-k. The i40evf driver has been updated to version 1.6.27-k. The ixgbe driver has been updated to version 4.4.0-k-rh7.4. The be2net driver has been updated to version 11.1.0.0r. The qede driver has been updated to version 8.10.10.21. The qlge driver has been updated to version 1.00.00.35. The qed driver has been updated to version 8.10.10.21. The bna driver has been updated to version 3.2.25.1r. The bnxt driver has been updated to version 1.7.0. The enic driver has been updated to version 2.3.0.31. The fjes driver has been updated to version 1.2. The hpwdt driver has been updated to version 1.4.02. Graphics Driver and Miscellaneous Driver Updates The vmwgfx driver has been updated to version 2.12.0.0. The hpilo driver has been updated to version 1.5.0.

Commands:
4.5. Configuring Storage-Based Fence Devices with unfencing When creating a SAN/storage fence device (that is, one that uses a non-power based fencing agent), you must set the meta option provides=unfencing when creating the stonith device. This ensures that a fenced node is unfenced before the node is rebooted and the cluster services are started on the node. Setting the provides=unfencing meta option is not necessary when configuring a power-based fence device, since the device itself is providing power to the node in order for it to boot (and attempt to rejoin the cluster). The act of booting in this case implies that unfencing occurred. The following command configures a stonith device named my-scsi-shooter that uses the fence_scsi fence agent, enabling unfencing for the device.

Commands:
pcs stonith create my-scsi-shooter fence_scsi devices=/dev/sda meta provides=unfencing
Chapter 1. Provisioning APIs 1.1. BMCEventSubscription [metal3.io/v1alpha1] Description BMCEventSubscription is the Schema for the fast eventing API Type object 1.2. BareMetalHost [metal3.io/v1alpha1] Description BareMetalHost is the Schema for the baremetalhosts API Type object 1.3. FirmwareSchema [metal3.io/v1alpha1] Description FirmwareSchema is the Schema for the firmwareschemas API Type object 1.4. HardwareData [metal3.io/v1alpha1] Description HardwareData is the Schema for the hardwaredata API Type object 1.5. HostFirmwareSettings [metal3.io/v1alpha1] Description HostFirmwareSettings is the Schema for the hostfirmwaresettings API Type object 1.6. PreprovisioningImage [metal3.io/v1alpha1] Description PreprovisioningImage is the Schema for the preprovisioningimages API Type object 1.7. Provisioning [metal3.io/v1alpha1] Description Provisioning contains configuration used by the Provisioning service (Ironic) to provision baremetal hosts. Provisioning is created by the OpenShift installer using admin or user provided information about the provisioning network and the NIC on the server that can be used to PXE boot it. This CR is a singleton, created by the installer and currently only consumed by the cluster-baremetal-operator to bring up and update containers in a metal3 cluster. Type object

Commands:
Chapter 1. Viewing applications that are connected to OpenShift AI You can view the available open source and third-party connected applications from the OpenShift AI dashboard. Prerequisites You have logged in to Red Hat OpenShift AI. Procedure From the OpenShift AI dashboard, select Applications Explore . The Explore page displays applications that are available for use with OpenShift AI. Click a tile for more information about the application or to access the Enable button. Note: The Enable button is visible only if an application does not require an OpenShift Operator installation. Verification You can access the Explore page and click on tiles.

Commands: