mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
CNV-70051: Removing unused assemblies from CNV docs
This commit is contained in:
Ashleigh Brennan
committed by
openshift-cherrypick-robot
openshift-cherrypick-robot
parent
8ef93298c3
commit
e870046a59
@@ -4824,10 +4824,6 @@ Topics:
|
||||
- Name: Creating a virtual machine
|
||||
Dir: creating_vm
|
||||
Topics:
|
||||
# - Name: Overview
|
||||
# File: virt-basic-vm-overview
|
||||
# - Name: Setting up your environment
|
||||
# File: virt-setting-up-environment
|
||||
- Name: Creating VMs from instance types
|
||||
File: virt-creating-vms-from-instance-types
|
||||
- Name: Creating VMs from templates
|
||||
|
||||
@@ -1463,8 +1463,6 @@ Topics:
|
||||
# Topics:
|
||||
# - Name: Overview
|
||||
# File: virt-vm-overview
|
||||
# - Name: Setting up your environment
|
||||
# File: virt-setting-up-environment
|
||||
# - Name: Creating VMs from instance types
|
||||
# File: virt-creating-vms-from-instance-types
|
||||
# - Name: Creating VMs from templates
|
||||
@@ -1472,8 +1470,6 @@ Topics:
|
||||
# - Name: Advanced VM creation
|
||||
# Dir: creating_vms_advanced
|
||||
# Topics:
|
||||
# - Name: Overview
|
||||
# File: virt-advanced-vm-overview
|
||||
# - Name: Creating VMs in the web console
|
||||
# Dir: creating_vms_advanced_web
|
||||
# Topics:
|
||||
|
||||
@@ -1741,10 +1741,6 @@ Topics:
|
||||
- Name: Creating a virtual machine
|
||||
Dir: creating_vm
|
||||
Topics:
|
||||
# - Name: Overview
|
||||
# File: virt-basic-vm-overview
|
||||
# - Name: Setting up your environment
|
||||
# File: virt-setting-up-environment
|
||||
- Name: Creating VMs from instance types
|
||||
File: virt-creating-vms-from-instance-types
|
||||
- Name: Creating VMs from templates
|
||||
@@ -1752,8 +1748,6 @@ Topics:
|
||||
- Name: Advanced VM creation
|
||||
Dir: creating_vms_advanced
|
||||
Topics:
|
||||
# - Name: Overview
|
||||
# File: virt-advanced-vm-overview
|
||||
- Name: Creating VMs from Red Hat images
|
||||
Dir: creating_vms_advanced_web
|
||||
Topics:
|
||||
|
||||
@@ -1583,10 +1583,6 @@ Topics:
|
||||
- Name: Creating a virtual machine
|
||||
Dir: creating_vm
|
||||
Topics:
|
||||
# - Name: Overview
|
||||
# File: virt-basic-vm-overview
|
||||
# - Name: Setting up your environment
|
||||
# File: virt-setting-up-environment
|
||||
- Name: Creating VMs from instance types
|
||||
File: virt-creating-vms-from-instance-types
|
||||
- Name: Creating VMs from templates
|
||||
@@ -1594,8 +1590,6 @@ Topics:
|
||||
- Name: Advanced VM creation
|
||||
Dir: creating_vms_advanced
|
||||
Topics:
|
||||
# - Name: Overview
|
||||
# File: virt-advanced-vm-overview
|
||||
- Name: Creating VMs from Red Hat images
|
||||
Dir: creating_vms_advanced_web
|
||||
Topics:
|
||||
|
||||
@@ -1,143 +0,0 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * virt/virtual_machines/advanced_vm_management/virt-configuring-cluster-realtime-workloads.adoc
|
||||
|
||||
:_mod-docs-content-type: PROCEDURE
|
||||
[id="virt-configuring-cluster-real-time_{context}"]
|
||||
= Configuring a cluster for real-time workloads
|
||||
|
||||
[role="_abstract"]
|
||||
You can configure an {product-title} cluster to run real-time workloads.
|
||||
|
||||
.Prerequisites
|
||||
* You have access to the cluster as a user with `cluster-admin` permissions.
|
||||
* You have installed the OpenShift CLI (`oc`).
|
||||
* You have installed the Node Tuning Operator.
|
||||
|
||||
.Procedure
|
||||
|
||||
. Label a subset of the compute nodes with a custom role, for example, `worker-realtime`:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc label node <node_name> node-role.kubernetes.io/worker-realtime=""
|
||||
----
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
You must use the default `master` role for {sno} and compact clusters.
|
||||
====
|
||||
|
||||
. Create a new `MachineConfigPool` manifest that contains the `worker-realtime` label in the `spec.machineConfigSelector` object.
|
||||
+
|
||||
Example `MachineConfigPool` manifest:
|
||||
+
|
||||
[source,yaml]
|
||||
----
|
||||
apiVersion: machineconfiguration.openshift.io/v1
|
||||
kind: MachineConfigPool
|
||||
metadata:
|
||||
name: worker-realtime
|
||||
labels:
|
||||
machineconfiguration.openshift.io/role: worker-realtime
|
||||
spec:
|
||||
machineConfigSelector:
|
||||
matchExpressions:
|
||||
- key: machineconfiguration.openshift.io/role
|
||||
operator: In
|
||||
values:
|
||||
- worker
|
||||
- worker-realtime
|
||||
nodeSelector:
|
||||
matchLabels:
|
||||
node-role.kubernetes.io/worker-realtime: ""
|
||||
----
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
You do not need to create a new `MachineConfigPool` manifest for {sno} and compact clusters.
|
||||
====
|
||||
|
||||
. If you created a new `MachineConfigPool` manifest in step 2, apply it to the cluster by using the following command:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc apply -f <real_time_mcp>.yaml
|
||||
----
|
||||
|
||||
. Create a `PerformanceProfile` manifest that applies to the labeled nodes and the machine config pool that you created in the previous steps.
|
||||
+
|
||||
Example `PerformanceProfile` manifest:
|
||||
+
|
||||
[source,yaml]
|
||||
----
|
||||
apiVersion: performance.openshift.io/v2
|
||||
kind: PerformanceProfile
|
||||
metadata:
|
||||
name: profile-1
|
||||
spec:
|
||||
cpu:
|
||||
isolated: 4-39,44-79
|
||||
reserved: 0-3,40-43
|
||||
globallyDisableIrqLoadBalancing: true
|
||||
hugepages:
|
||||
defaultHugepagesSize: 1G
|
||||
pages:
|
||||
- count: 8
|
||||
size: 1G
|
||||
realTimeKernel:
|
||||
enabled: true
|
||||
workloadHints:
|
||||
highPowerConsumption: true
|
||||
realTime: true
|
||||
nodeSelector:
|
||||
node-role.kubernetes.io/worker-realtime: ""
|
||||
numa:
|
||||
topologyPolicy: single-numa-node
|
||||
----
|
||||
|
||||
. Apply the `PerformanceProfile` manifest:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc apply -f <real_time_pp>.yaml
|
||||
----
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
The compute nodes automatically reboot twice after you apply the `MachineConfigPool` and `PerformanceProfile` manifests. This process might take a long time.
|
||||
====
|
||||
|
||||
. Retrieve the name of the generated `RuntimeClass` resource from the `status.runtimeClass` field of the `PerformanceProfile` object:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc get performanceprofiles.performance.openshift.io profile-1 -o=jsonpath='{.status.runtimeClass}{"\n"}'
|
||||
----
|
||||
|
||||
. Set the previously obtained `RuntimeClass` name as the default container runtime class for the `virt-launcher` pods by editing the `HyperConverged` custom resource (CR):
|
||||
+
|
||||
[source,terminal,subs="attributes+"]
|
||||
----
|
||||
$ oc patch hyperconverged kubevirt-hyperconverged -n {CNVNamespace} \
|
||||
--type='json' -p='[{"op": "add", "path": "/spec/defaultRuntimeClass", "value":"<runtimeclass_name>"}]'
|
||||
----
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
Editing the `HyperConverged` CR changes a global setting that affects all VMs that are created after the change is applied.
|
||||
====
|
||||
|
||||
. If your real-time-enabled compute nodes use simultaneous multithreading (SMT), enable the `alignCPUs` feature gate by editing the `HyperConverged` CR:
|
||||
+
|
||||
[source,terminal,subs="attributes+"]
|
||||
----
|
||||
$ oc patch hyperconverged kubevirt-hyperconverged -n {CNVNamespace} \
|
||||
--type='json' -p='[{"op": "replace", "path": "/spec/featureGates/alignCPUs", "value": true}]'
|
||||
----
|
||||
+
|
||||
[NOTE]
|
||||
====
|
||||
Enabling `alignCPUs` allows {VirtProductName} to request up to two additional dedicated CPUs to bring the total CPU count to an even parity when using
|
||||
emulator thread isolation.
|
||||
====
|
||||
@@ -1,194 +0,0 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * virt/virtual_machines/advanced_vm_management/virt-configuring-cluster-realtime-workloads.adoc
|
||||
|
||||
:_mod-docs-content-type: PROCEDURE
|
||||
[id="virt-configuring-vm-real-time_{context}"]
|
||||
= Configuring a virtual machine for real-time workloads
|
||||
|
||||
[role="_abstract"]
|
||||
You can configure a virtual machine (VM) to run real-time workloads.
|
||||
|
||||
.Prerequisites
|
||||
* Your cluster is configured to run real-time workloads.
|
||||
* You have installed the `virtctl` CLI.
|
||||
* You have installed the {oc-first}.
|
||||
|
||||
.Procedure
|
||||
. Create a `VirtualMachine` manifest to include information about CPU topology, CRI-O annotations, and huge pages.
|
||||
+
|
||||
Example `VirtualMachine` manifest:
|
||||
+
|
||||
[source,yaml]
|
||||
----
|
||||
apiVersion: kubevirt.io/v1
|
||||
kind: VirtualMachine
|
||||
metadata:
|
||||
name: realtime-vm
|
||||
spec:
|
||||
runStrategy: Always
|
||||
template:
|
||||
metadata:
|
||||
annotations:
|
||||
cpu-load-balancing.crio.io: disable # <1>
|
||||
cpu-quota.crio.io: disable # <2>
|
||||
irq-load-balancing.crio.io: disable # <3>
|
||||
spec:
|
||||
domain:
|
||||
cpu:
|
||||
dedicatedCpuPlacement: true
|
||||
isolateEmulatorThread: true
|
||||
model: host-passthrough
|
||||
numa:
|
||||
guestMappingPassthrough: {}
|
||||
realtime: {}
|
||||
sockets: 1 # <4>
|
||||
cores: 4 # <5>
|
||||
threads: 1
|
||||
devices:
|
||||
autoattachGraphicsDevice: false
|
||||
autoattachMemBalloon: false
|
||||
autoattachSerialConsole: true
|
||||
ioThreadsPolicy: auto
|
||||
memory:
|
||||
guest: 4Gi
|
||||
hugepages:
|
||||
pageSize: 1Gi # <6>
|
||||
terminationGracePeriodSeconds: 0
|
||||
# ...
|
||||
----
|
||||
<1> This annotation specifies that load balancing is disabled for CPUs that are used by the container.
|
||||
<2> This annotation specifies that the CPU quota is disabled for CPUs that are used by the container.
|
||||
<3> This annotation specifies that interrupt request (IRQ) load balancing is disabled for CPUs that are used by the container.
|
||||
<4> The number of sockets inside the VM.
|
||||
<5> The number of cores inside the VM. This must be a value greater than or equal to `1`.
|
||||
<6> The size of the huge pages. The possible values for x86-64 architectures are `1Gi` and `2Mi`. In this example, the request is for 4 huge pages of size 1 Gi.
|
||||
. Apply the `VirtualMachine` manifest:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc apply -f <file_name>.yaml
|
||||
----
|
||||
. Configure the guest operating system. The following example shows the configuration steps for a {op-system-base} 9 operating system:
|
||||
.. Run the following command to connect to the VM console:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ virtctl console <vm_name>
|
||||
----
|
||||
.. If you are not already logged in as a root user, switch to the root user account to execute the remaining configuration steps.
|
||||
.. Disable the `irqbalance` service by using the following command:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
# systemctl disable irqbalance && systemctl stop irqbalance
|
||||
----
|
||||
.. Enable the real-time and network function virtualization (NFV) repositories:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
# subscription-manager repos --enable rhel-9-for-x86_64-rt-rpms --enable rhel-9-for-x86_64-nfv-rpms
|
||||
----
|
||||
.. Install the necessary packages by running the following command:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
# dnf install tuned cloud-init
|
||||
----
|
||||
.. To achieve low-latency tuning by using the `realtime-virtual-guest` profile in the TuneD application, run the following commands:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
# dnf install kernel-rt realtime-tests tuned-profiles-realtime
|
||||
----
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
# dnf install tuned-profiles-nfv-guest
|
||||
----
|
||||
.. Edit the `/etc/tuned/realtime-virtual-guest-variables.conf` file:
|
||||
+
|
||||
[source,conf]
|
||||
----
|
||||
#
|
||||
# Variable settings below override the definitions from the
|
||||
# /etc/tuned/realtime-variables.conf file.
|
||||
|
||||
#
|
||||
# Core isolation
|
||||
#
|
||||
# The 'isolated_cores=' variable below controls which cores should be
|
||||
# isolated. By default we reserve 1 core per socket for housekeeping
|
||||
# and isolate the rest. But you can isolate any range as shown in the
|
||||
# examples below. Just remember to keep only one isolated_cores= line.
|
||||
#
|
||||
# Examples:
|
||||
# isolated_cores=2,4-7
|
||||
# isolated_cores=2-23
|
||||
#
|
||||
# Reserve 1 core per socket for housekeeping, isolate the rest.
|
||||
# Change this for a core list or range as shown above.
|
||||
isolated_cores=2-3 <1>
|
||||
|
||||
#
|
||||
# Uncomment the 'isolate_managed_irq=Y' bellow if you want to move kernel
|
||||
# managed IRQs out of isolated cores. Note that this requires kernel
|
||||
# support. Please only specify this parameter if you are sure that the
|
||||
# kernel supports it.
|
||||
#
|
||||
isolate_managed_irq=Y <2>
|
||||
|
||||
#
|
||||
# Set the desired combined queue count value using the parameter provided
|
||||
# below. Ideally this should be set to the number of housekeeping CPUs i.e.,
|
||||
# in the example given below it is assumed that the system has 4 housekeeping
|
||||
# (non-isolated) CPUs.
|
||||
#
|
||||
# netdev_queue_count=4
|
||||
----
|
||||
<1> The first two CPUs (0 and 1) are set aside for house keeping tasks and the rest are isolated for the real-time application.
|
||||
<2> Set the `isolate_managed_irq` parameter to `Y` to move kernel-managed interrupt requests out of isolated cores.
|
||||
.. Activate the TuneD profile:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
# tuned-adm profile realtime-virtual-guest
|
||||
----
|
||||
.. Set the real-time kernel as the default by using the GRUB boot loader command-line interface:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
# grubby --set-default=/boot/vmlinuz-<installed_rt_kernel_version>
|
||||
----
|
||||
.. Set the kernel arguments by using the GRUB boot loader command-line interface:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
# grubby --args="iommu=pt intel_iommu=on default_hugepagesz=1G idle=poll" --update-kernel=$(grubby --default-kernel)
|
||||
----
|
||||
. Restart the VM to apply the changes.
|
||||
|
||||
.Verification
|
||||
* Use the `cyclictest` tool to verify that the real-time guest is configured properly:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
# cyclictest --priority 1 --policy fifo -h 50 -a 2-3 --mainaffinity 0,1 -t 2 -m -q -i 200 -D 12h
|
||||
----
|
||||
+
|
||||
where:
|
||||
+
|
||||
--
|
||||
`-a`:: Specifies the CPU set on which the test runs. This is the same as the isolated CPUs that you configured in the `realtime-variables.conf` file.
|
||||
`-D`:: Specifies the test duration. Append `m`, `h`, or `d` to specify minutes, hours or days.
|
||||
--
|
||||
+
|
||||
Example output:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
# Min Latencies: 00004 00004
|
||||
# Avg Latencies: 00004 00004
|
||||
# Max Latencies: 00014 00013 <1>
|
||||
----
|
||||
<1> The `Max Latencies` value in the output must be less than 40 micro seconds.
|
||||
@@ -1,6 +1,6 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * virt/virtual_machines/virt-specifying-instance-preference.adoc
|
||||
// * virt/creating_vm/virt-creating-vms-from-instance-types.adoc
|
||||
|
||||
:_mod-docs-content-type: PROCEDURE
|
||||
[id="virt-infer-instancetype-preference_{context}"]
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * virt/virtual_machines/virt-specifying-instance-preference.adoc
|
||||
// * virt/creating_vm/virt-creating-vms-from-instance-types.adoc
|
||||
|
||||
:_mod-docs-content-type: PROCEDURE
|
||||
[id="inferfromvolume-labels_{context}"]
|
||||
@@ -22,7 +22,6 @@ Use the following labels on your PVC, data source, or data volume to instruct th
|
||||
.Procedure
|
||||
|
||||
* To apply a label to a data source, use `oc label`. The following command applies a label that points to a cluster-wide instance type:
|
||||
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
// Module included in the following assemblies:
|
||||
//
|
||||
// * virt/virtual_machines/virt-specifying-instance-preference.adoc
|
||||
// * virt/creating_vm/virt-creating-vms-from-instance-types.adoc
|
||||
|
||||
:_mod-docs-content-type: PROCEDURE
|
||||
[id="virt-using-flags-specify_{context}"]
|
||||
|
||||
@@ -57,4 +57,3 @@ Interfaces:
|
||||
fe80::1420:84ff:fe10:17aa/64
|
||||
Mac: 16:20:84:10:17:aa
|
||||
----
|
||||
|
||||
|
||||
@@ -1,5 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="virt-basic-vm-overview"]
|
||||
= Virtual machines overview
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: virt-basic-vm-overview
|
||||
@@ -1,5 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="virt-setting-up-environment"]
|
||||
= Setting up your environment
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: virt-setting-up-environment
|
||||
@@ -1,16 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="virt-specifying-instance-preference"]
|
||||
= Specifying an instance type or preference
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: virt-specifying-instance-preference
|
||||
|
||||
toc::[]
|
||||
|
||||
You can specify an instance type, a preference, or both to define a set of workload sizing and runtime characteristics for reuse across multiple VMs.
|
||||
|
||||
include::modules/virt-using-flags-specify.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/virt-infer-instancetype-preference.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/virt-inferfromvolume-labels.adoc[leveloffset=+1]
|
||||
|
||||
@@ -1,38 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="virt-advanced-vm-overview"]
|
||||
= Advanced virtual machines overview
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: virt-advanced-vm-overview
|
||||
toc::[]
|
||||
|
||||
In addition to creating virtual machines (VM) using templates or instances in the web console, you can also create VMs from custom operating system images by using one of the following methods:
|
||||
|
||||
* xref:../../virt/creating_vms_advanced/creating_vms_cli/virt-creating-vms-from-container-disks.adoc#virt-creating-vms-from-container-disks[Importing the image as a container disk from a registry].
|
||||
+
|
||||
Optional: You can enable auto updates for your container disks. See xref:../../virt/storage/virt-automatic-bootsource-updates.adoc#virt-automatic-bootsource-updates[Managing automatic boot source updates] for details.
|
||||
|
||||
* xref:../../virt/creating_vms_advanced/creating_vms_advanced_web/virt-creating-vms-from-web-images.adoc#virt-creating-vms-from-web-images[Importing the image from a web page].
|
||||
* xref:../../virt/creating_vms_advanced/creating_vms_advanced_web/virt-creating-vms-uploading-images.adoc#virt-creating-vms-uploading-images[Uploading the image from a local machine].
|
||||
* xref:../../virt/creating_vms_advanced/creating_vms_cli/virt-creating-vms-by-cloning-pvcs.adoc#virt-creating-vms-by-cloning-pvcs[Cloning a persistent volume claim (PVC) that contains the image].
|
||||
|
||||
The Containerized Data Importer (CDI) imports the image into a PVC by using a data volume. You add the PVC to the VM by using the {product-title} web console or command line.
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
You must install the xref:../../virt/managing_vms/virt-installing-qemu-guest-agent.adoc#virt-installing-qemu-guest-agent[QEMU guest agent] on VMs created from operating system images that are not provided by Red Hat.
|
||||
|
||||
You must also install xref:../../virt/managing_vms/virt-installing-qemu-guest-agent.adoc#installing-virtio-drivers[VirtIO drivers] on Windows VMs.
|
||||
|
||||
The QEMU guest agent is included with Red Hat images.
|
||||
====
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
You can create virtual machines (VMs) from the command line by editing or creating a `VirtualMachine` manifest. You can simplify VM configuration by using an xref:../../virt/creating_vm/virt-creating-vms-from-instance-types.adoc#virt-creating-vms-from-instance-types[instance type] in your VM manifest.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
You can also xref:../../virt/creating_vm/virt-creating-vms-from-instance-types.adoc#virt-creating-vm-instancetype_virt-creating-vms-from-instance-types[create VMs from instance types by using the web console].
|
||||
====
|
||||
@@ -1,21 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="virt-configuring-cluster-realtime-workloads"]
|
||||
= Running real-time workloads
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: virt-configuring-cluster-realtime-workloads
|
||||
|
||||
toc::[]
|
||||
|
||||
You can configure an {product-title} cluster to run real-time virtual machine (VM) workloads that require low and predictable latency. {product-title} provides the Node Tuning Operator to implement automatic tuning for real-time and low latency workloads.
|
||||
|
||||
include::modules/virt-configuring-cluster-real-time.adoc[leveloffset=+1]
|
||||
|
||||
include::modules/virt-configuring-vm-real-time.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
[id="additional-resources_configuring-cluster-real-time"]
|
||||
== Additional resources
|
||||
|
||||
* xref:../../../../scalability_and_performance/using-node-tuning-operator.adoc#using-node-tuning-operator[Using the Node Tuning Operator]
|
||||
* xref:../../../../scalability_and_performance/cnf-provisioning-low-latency-workloads.adoc#cnf-provisioning-low-latency-workloads[Provisioning real-time and low latency workloads]
|
||||
* xref:../../../../scalability_and_performance/cnf-tuning-low-latency-nodes-with-perf-profile.adoc#cnf-reducing-nic-queues-with-nto[Reducing NIC queues using the Node Tuning Operator]
|
||||
@@ -1,17 +0,0 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="virt-viewing-ip-of-vm-nic"]
|
||||
= Viewing virtual machine IP addresses
|
||||
include::_attributes/common-attributes.adoc[]
|
||||
:context: virt-viewing-ip-of-vm-nic
|
||||
|
||||
toc::[]
|
||||
|
||||
You can view the IP address of a virtual machine network interface by using the {product-title} web console or the command line.
|
||||
|
||||
include::modules/virt-viewing-vmi-ip-cli.adoc[leveloffset=+1]
|
||||
include::modules/virt-viewing-vmi-ip-web.adoc[leveloffset=+1]
|
||||
|
||||
[role="_additional-resources"]
|
||||
[id="additional-resources_virt-viewing-ip-of-vm-nic"]
|
||||
== Additional resources
|
||||
* xref:../../virt/managing_vms/virt-installing-qemu-guest-agent.adoc#virt-installing-qemu-guest-agent[Installing the QEMU guest agent]
|
||||
Reference in New Issue
Block a user