mtpti5iD/redhat-docs_dataset huggingface dataset:
Setting up an NVIDIA GPU for a virtual machine in Red Hat Virtualization Red Hat Virtualization 4.3 How to configure a virtual machine in Red Hat Virtualization to use a dedicated GPU or vGPU. Red Hat Virtualization Documentation Team Red Hat Customer Content Services rhev-docs@redhat.com Abstract This document describes how to use a host with a graphics processing unit (GPU) to run virtual machines in Red Hat Virtualization for graphics-intensive tasks and software that cannot run without a GPU.

Commands:
Chapter 7. Known issues This section documents known issues found in this release of Red Hat Ceph Storage. 7.1. The Cephadm utility Adding or expanding iSCSI gateways in gwcli across the iSCSI daemons works as expected Previously, due to iSCSI daemons not being reconfigured automatically when a trusted IP list was updated in the specification file, adding or expanding iSCSI gateways in gwcli would fail due to the iscsi-gateway.cfg not matching across the iSCSI daemons. With this fix, you can expand the gateways and add it to the existing gateways with gwcli command. ( BZ#2099470 ) ceph orch ps does not display a version for monitoring stack daemons In cephadm , due to the version grabbing code currently being incompatible with the downstream monitoring stack containers, version grabbing fails for monitoring stack daemons, such as node-exporter , prometheus , and alertmanager . As a workaround, if the user needs to find the version, the daemons' container names include the version. ( BZ#2125382 )

Commands:
Chapter 2. New features and enhancements A list of all major enhancements, and new features introduced in this release of Red Hat Trusted Profile Analyzer (RHTPA). The features and enhancements added by this release are: Trusted Profile Analyzer on Red Hat Enterprise Linux With this release, as a Technical Preview, you can deploy RHTPA on Red Hat Enterprise Linux 9 by using an Ansible Playbook. You can customize this deployment solution by using your own PostgreSQL database, OpenID Connect (OIDC) provider, Simple Storage Service (S3), and Simple Queue Service (SQS) services. You can find more information in the RHTPA Deployment Guide . Redesign of the Trusted Profile Analyzer console, and a new CVE impact panel With this release, we designed a new Dashboard homepage that is more intuitive, and gives users more pertinent data at a glance. The Dashboard shows the Common Vulnerabilities and Exposures (CVE) impact on the last 10 software bill of materials (SBOM) uploaded. Along with the impact data, you can also see the date and time, and the number of documents, such as, Common Security Advisory Framework (CSAF) advisories, SBOMs and CVEs recently uploaded. New version of the component registry With this release, we updated the Graphical Understanding of Artifact Composition (GUAC) component registry to version 0.7.2. This newer GUAC version is easier to support and is more reliable than earlier versions. Currently, there is no upgrade path from RHTPA 1.1 to 1.2. You must do a fresh installation of RHTPA 1.2, and re-upload your documents to use the new features of GUAC 0.7.2. Support for CycloneDX 1.5 and SPDX 2.3 With this release, we now support software bill of materials (SBOM) documents formatted in CycloneDX version 1.5, and SPDX version 2.3.

Commands:
5.90. gnome-power-manager 5.90.1. RHBA-2012:0935 - gnome-power-manager bug fix update Updated gnome-power-manager packages that fix one bug are now available for Red Hat Enterprise Linux 6. GNOME Power Manager uses the information and facilities provided by UPower displaying icons and handling user callbacks in an interactive GNOME session. Bug Fix BZ# 676866 After resuming the system or re-enabling the display, an icon could appear in the notification area with an erroneous tooltip that read "Session active, not inhibited, screen idle. If you see this test, your display server is broken and you should notify your distributor." and included a URL to an external web page. This error message was incorrect, had no effect on the system and could be safely ignored. In addition, linking to an external URL from the notification and status area is unwanted. To prevent this, the icon is no longer used for debugging idle problems. All users of gnome-power-manager are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Installing the Hot Rod C++ client Install the Hot Rod C++ client on your host system as a dynamic library. 1.1. C++ compiler requirements Operating system Required compiler Red Hat Enterprise Linux (RHEL) 8 C++ 11 compiler (GCC 8.5.0) RHEL 9 C++ 11 compiler (GCC 11.3.1) Microsoft Windows 7 x64 C++ 11 compiler (Visual Studio 14 2015 Win64, Microsoft Visual C++ 2013 Redistributable Package for the x64 platform) 1.2. Installing Hot Rod C++ clients on Red Hat Enterprise Linux (RHEL) Data Grid provides an RPM distribution of the Hot Rod C++ client for RHEL. Procedure Enable the repository for the Hot Rod C++ client on RHEL. RHEL version Repository RHEL 8 jb-datagrid-8.4-for-rhel-8-x86_64-rpms RHEL 9 jb-datagrid-8.4-for-rhel-9-x86_64-rpms Install the Hot Rod C++ client. Additional resources Enabling or disabling a repository using Red Hat Subscription Management (Red Hat Knowledgebase) Red Hat Package Browser 1.3. Installing Hot Rod C++ clients on Microsoft Windows Data Grid provides an archived version of the Hot Rod C++ client for installation on Windows. Procedure Download the ZIP archive for the Hot Rod C++ client from the Data Grid Software Downloads . Extract the ZIP archive to your file system.

Commands:
yum install jdg-cpp-client
Appendix C. Using AMQ Broker with the examples The AMQ Core Protocol JMS examples require a running message broker with a queue named exampleQueue . Use the procedures below to install and start the broker and define the queue. C.1. Installing the broker Follow the instructions in Getting Started with AMQ Broker to install the broker and create a broker instance . Enable anonymous access. The following procedures refer to the location of the broker instance as <broker-instance-dir> . C.2. Starting the broker Procedure Use the artemis run command to start the broker. USD <broker-instance-dir> /bin/artemis run Check the console output for any critical errors logged during startup. The broker logs Server is now live when it is ready. USD example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server ... 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... C.3. Creating a queue In a new terminal, use the artemis queue command to create a queue named exampleQueue . USD <broker-instance-dir> /bin/artemis queue create --name exampleQueue --address exampleQueue --auto-create-address --anycast You are prompted to answer a series of yes or no questions. Answer N for no to all of them. Once the queue is created, the broker is ready for use with the example programs. C.4. Stopping the broker When you are done running the examples, use the artemis stop command to stop the broker. USD <broker-instance-dir> /bin/artemis stop Revised on 2020-10-08 11:28:44 UTC

Commands:
<broker-instance-dir> /bin/artemis run
example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
<broker-instance-dir> /bin/artemis queue create --name exampleQueue --address exampleQueue --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop
Appendix D. Create an Amazon S3 bucket Open a terminal and ensure that the AWS CLI is installed and configured with your AWS credentials. Run the following command to create a new S3 bucket: Warning The bucket name must be a unique name. Run the following command to check that the bucket has been successfully created

Commands:
aws s3 mb s3://<bucket-name> --region <region-name>
aws s3 ls | grep <bucket-name>
C.2. Encrypting Block Devices Using dm-crypt/LUKS6tit Linux Unified Key Setup (LUKS) is a specification for block device encryption. It establishes an on-disk format for the data, as well as a passphrase/key management policy. LUKS uses the kernel device mapper subsystem via the dm-crypt module. This arrangement provides a low-level mapping that handles encryption and decryption of the device's data. User-level operations, such as creating and accessing encrypted devices, are accomplished through the use of the cryptsetup utility. C.2.1. Overview of LUKS What LUKS does: LUKS encrypts entire block devices LUKS is thereby well-suited for protecting the contents of mobile devices such as: Removable storage media Laptop disk drives The underlying contents of the encrypted block device are arbitrary. This makes it useful for encrypting swap devices. This can also be useful with certain databases that use specially formatted block devices for data storage. LUKS uses the existing device mapper kernel subsystem. This is the same subsystem used by LVM, so it is well tested. LUKS provides passphrase strengthening. This protects against dictionary attacks. LUKS devices contain multiple key slots. This allows users to add backup keys/passphrases. What LUKS does not do: LUKS is not well-suited for applications requiring many (more than eight) users to have distinct access keys to the same device. LUKS is not well-suited for applications requiring file-level encryption. More detailed information about LUKS is available from the project website at http://code.google.com/p/cryptsetup/ .

Commands:
8.19. coolkey 8.19.1. RHBA-2013:1699 - coolkey bug fix and enhancement update Updated coolkey packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. Coolkey is a smart card support library for the CoolKey, Common Access Card (CAC), and Personal Identity Verification (PIV) smart cards. Bug Fixes BZ# 806038 In versions, coolkey always created a bogus e-gate smart card reader to avoid problems with Network Security Services (NSS) and the PC/SC Lite framework when no smart card reader was available. However, e-gate smart cards are no longer available for smart card authentication, and the NSS and pcsc-lite packages have been updated to handle a situation with no e-gate reader attached. Therefore, this bogus reader in coolkey became unnecessary and could cause problems to some applications under certain circumstances. This update modifies the respective code so that coolkey no longer creates a bogus e-gate smart card. BZ# 906537 With a version of coolkey, some signature operations, such as PKINIT, could fail on PIV endpoint cards that support both CAC and PIV interfaces. The underlying coolkey code has been modified so these PIV endpoint cards now works with coolkey as expected. BZ# 991515 The coolkey library registered only with the NSS DBM database, however, NSS now uses also the SQLite database format, which is preferred. This update modifies coolkey to register properly with both NSS databases. Enhancement BZ# 951272 Support for tokens containing Elliptic Curve Cryptography (ECC) certificates has been added to the coolkey packages so the coolkey library now works with ECC provisioned cards. Users of coolkey are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 10. Viewing and managing JMX domains and MBeans Java Management Extensions (JMX) is a Java technology that allows you to manage resources (services, devices, and applications) dynamically at runtime. The resources are represented by objects called MBeans (for Managed Bean). You can manage and monitor resources as soon as they are created, implemented, or installed. With the JMX plugin on the Fuse Console, you can view and manage JMX domains and MBeans. You can view MBean attributes, run commands, and create charts that show statistics for the MBeans. The JMX tab provides a tree view of the active JMX domains and MBeans organized in folders. You can view details and execute commands on the MBeans. Procedure To view and edit MBean attributes: In the tree view, select an MBean. Click the Attributes tab. Click an attribute to see its details. To perform operations: In the tree view, select an MBean. Click the Operations tab, expand one of the listed operations. Click Execute to run the operation. To view charts: In the tree view, select an item. Click the Chart tab.

Commands:
Chapter 1. Operators overview Operators are among the most important components of Red Hat OpenShift Service on AWS. They are the preferred method of packaging, deploying, and managing services on the control plane. They can also provide advantages to applications that users run. Operators integrate with Kubernetes APIs and CLI tools such as kubectl and the OpenShift CLI ( oc ). They provide the means of monitoring applications, performing health checks, managing over-the-air (OTA) updates, and ensuring that applications remain in your specified state. Operators are designed specifically for Kubernetes-native applications to implement and automate common Day 1 operations, such as installation and configuration. Operators can also automate Day 2 operations, such as autoscaling up or down and creating backups. All of these activities are directed by a piece of software running on your cluster. While both follow similar Operator concepts and goals, Operators in Red Hat OpenShift Service on AWS are managed by two different systems, depending on their purpose: Cluster Operators Managed by the Cluster Version Operator (CVO) and installed by default to perform cluster functions. Optional add-on Operators Managed by Operator Lifecycle Manager (OLM) and can be made accessible for users to run in their applications. Also known as OLM-based Operators . 1.1. For developers As an Operator author, you can perform the following development tasks for OLM-based Operators: Install Operator SDK CLI . Create Go-based Operators , Ansible-based Operators , and Helm-based Operators . Use Operator SDK to build, test, and deploy an Operator . Create an application from an installed Operator through the web console . 1.2. For administrators As an administrator with the dedicated-admin role, you can perform the following Operator tasks: Manage custom catalogs . Install an Operator from OperatorHub . View Operator status . Manage Operator conditions . Upgrade installed Operators . Delete installed Operators . Configure proxy support . 1.3. steps To understand more about Operators, see What are Operators?

Commands:
Chapter 9. Installation and Booting Add-on repositories are now handled correctly when generating and reading kickstart files. Previously, installation would stop and display an error when performing an installation from a kickstart file generated by a installation which used optical media, and enabled one or more add-on repositories. With this update, generated kickstart files will include commands to automatically enable add-on repositories when necessary. (BZ#1099178) The zerombr command is now correctly added to anaconda-ks.cfg when installing using kickstart Previously, when an installation was performed with the kickstart utility using the zerombr option, this option was not added to the generated /root/anaconda-ks.cfg kickstart file. This bug has been fixed, and zerombr is now correctly added to anaconda-ks.cfg . (BZ#1246663) When using the network service, default routes are now correctly created on an installed system. Previously, device-specific GATEWAY values were being included in the /etc/sysconfig/network configuration file, which applies to all devices. As a consequence, for some network configurations using the network service, default routes were not created. With this update, the GATEWAY parameter is no longer created in /etc/sysconfig/network , and default routes are now created correctly. (BZ#1181290) The DEFROUTE option is now handled correctly when the installer generates a kickstart file. Previously, if the DEFROUTE option was set in an ifcfg configuration file during installation, this was not reflected in the kickstart file subsequently generated by the installer. This bug has been fixed, and now the installer generates kickstart files which reflect DEFROUTE settings used during installation by setting the --nodefroute network command option accordingly. (BZ#1274686) The kdump kernel is no longer added to /etc/zipl.conf when kernel-kdump is marked for installation Previously, when installing kernel-kdump , an entry for the kdump kernel was added to the list of kernels in the /etc/zipl.conf configuration file. This bug is now fixed, and the kdump kernel is no longer added to the list. (BZ#1256211)

Commands:
B.17. dmidecode B.17.1. RHBA-2011:1396 - dmidecode bug fix update An updated dmidecode package that fixes one bug is now available for Red Hat Enterprise Linux 6 Extended Update Support. The dmidecode package provides utilities for extracting x86 and Intel Itanium hardware information from the system BIOS or EFI (Extensible Firmware Interface), depending on the SMBIOS/DMI standard. This information typically includes system manufacturer, model name, serial number, BIOS version, and asset tag, as well as other details, depending on the manufacturer. Bug Fix BZ# 745558 Prior to this update, the extended records for the DMI types Memory Device (DMI type 17) and Memory Array Mapped Address (DMI type 19) were missing from the dmidecode utility output. With this update, dmidecode has been upgraded to upstream version 2.11, which updates support for the SMBIOS specification to version 2.7.1, thus fixing this bug. Now, the dmidecode output contains the extended records for DMI type 17 and DMI type 19. All users of dmidecode are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 3. Managing cluster PVC size 3.1. Configuring the default PVC size for your cluster To configure how resources are claimed within your OpenShift AI cluster, you can change the default size of the cluster's persistent volume claim (PVC) ensuring that the storage requested matches your common storage workflow. PVCs are requests for resources in your cluster and also act as claim checks to the resource. Prerequisites You have logged in to OpenShift AI as a user with OpenShift AI administrator privileges. Note Changing the PVC setting restarts the Jupyter pod and makes Jupyter unavailable for up to 30 seconds. As a workaround, it is recommended that you perform this action outside of your organization's typical working day. Procedure From the OpenShift AI dashboard, click Settings Cluster settings . Under PVC size , enter a new size in gibibytes or mebibytes. Click Save changes . Verification New PVCs are created with the default storage size that you configured. Additional resources Understanding persistent storage 3.2. Restoring the default PVC size for your cluster To change the size of resources utilized within your OpenShift AI cluster, you can restore the default size of your cluster's persistent volume claim (PVC). Prerequisites You have logged in to OpenShift AI as a user with OpenShift AI administrator privileges. Procedure From the OpenShift AI dashboard, click Settings Cluster settings . Click Restore Default to restore the default PVC size of 20GiB. Click Save changes . Verification New PVCs are created with the default storage size of 20 GiB. Additional resources Understanding persistent storage

Commands:
Chapter 5. Red Hat Developer Hub support If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer Portal . You can use the Red Hat Customer Portal for the following purposes: To search or browse through the Red Hat Knowledgebase of technical support articles about Red Hat products. To create a support case for Red Hat Global Support Services (GSS). For support case creation, select Red Hat Developer Hub as the product and select the appropriate product version. For detailed information about supported platforms and life cycle details, see Red Hat Developer Hub Life Cycle . steps Installing Red Hat Developer Hub on Amazon Elastic Kubernetes Service Installing Red Hat Developer Hub on Google Cloud Platform on Google Cloud Platform Installing Red Hat Developer Hub on Google Kubernetes Engine Installing Red Hat Developer Hub on Microsoft Azure Kubernetes Service Installing Red Hat Developer Hub on OpenShift Container Platform

Commands:
Appendix C. Supported Data Sources and Translators C.1. Recommended Translators for Data Sources For a list of supported data sources and translators for this version of JDV, see the Red Hat JBoss Data Virtualization 6.x Supported Configurations article on the Red Hat Customer Portal. Note MS Excel is supported in so much as there is a write procedure. Note The MySQL InnoDB storage engine is not suitable for use as an external materialization target.

Commands:
7.33. createrepo 7.33.1. RHBA-2013:0328 - createrepo bug fix and enhancement update Updated createrepo packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The createrepo packages contain the utility that generates a common metadata repository from a directory of RPM packages. Note The createrepo packages have been upgraded to upstream version 0.9.9, which provides a number of bug fixes and enhancements over the version, including support for multitasking in the createrepo utility. This update also modifies the "--update" option to use the SQLite database instead of the XML files in order to reduce memory usage. (BZ#631989, BZ#716235) Bug Fix BZ# 833350 Previously, the createrepo utility ignored the "umask" command for files created in the createrepo cache directory. This behavior caused problems when more than one user was updating repositories. The bug has been fixed, and multiple users can now update repositories without complications. Enhancements BZ#646644 It is now possible to use the "createrepo" command with both the "--split" and the "--pkglist" options simultaneously. BZ# 714094 It is now possible to remove metadata from the repodata directory using the modifyrepo program. This update also enhances updating of the existing metadata. All users of createrepo are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands: