Merge branch 'one-6.10-maintenance' into b-2226

OpenNebula · Jan 17, 2025 · b4fcb2a · b4fcb2a
2 parents 9c56c2a + f8f5249
commit b4fcb2a
Show file tree

Hide file tree

Showing 7 changed files with 59 additions and 7 deletions.
diff --git a/...and_configuration/frontend_installation/opennebula_repository_configuration.rst b/...and_configuration/frontend_installation/opennebula_repository_configuration.rst
@@ -168,7 +168,7 @@ To add OpenNebula repository, execute the following as user ``root``:
 **RHEL 8, 9**
 
 .. prompt:: bash # auto
-   :substitutions:
+    :substitutions:
 
     # cat << "EOT" > /etc/yum.repos.d/opennebula.repo
     [opennebula]
@@ -184,7 +184,7 @@ To add OpenNebula repository, execute the following as user ``root``:
 **AlmaLinux 8, 9**
 
 .. prompt:: bash # auto
-   :substitutions:
+    :substitutions:
 
     # cat << "EOT" > /etc/yum.repos.d/opennebula.repo
     [opennebula]

diff --git a/source/installation_and_configuration/ha/vm_ha.rst b/source/installation_and_configuration/ha/vm_ha.rst
@@ -67,7 +67,7 @@ This process tries to connect to the host via SSH, synchronize the probes and st
 
 The following is a an example configuration
 
-.. code-block:: language
+.. code-block::
 
     Host *
     ServerAliveInterval 10

diff --git a/source/integration_and_development/system_interfaces/api.rst b/source/integration_and_development/system_interfaces/api.rst
@@ -129,6 +129,8 @@ onevm
 +----------------------+---------------------------+-------------------+
 | disk-snapshot-rename | one.vm.disksnapshotrename | VM:MANAGE         |
 +----------------------+---------------------------+-------------------+
+| disk-snapshot-list   | one.vmpool.info           | VM:USE            |
++----------------------+---------------------------+-------------------+
 | disk-attach*         | one.vm.attach             | VM:MANAGE         |
 |                      |                           |                   |
 |                      |                           | IMAGE:USE         |
@@ -173,6 +175,8 @@ onevm
 +----------------------+---------------------------+-------------------+
 | snapshot-revert*     | one.vm.snapshotrevert     | VM:MANAGE         |
 +----------------------+---------------------------+-------------------+
+| snapshot-list        | one.vmpool.info           | VM:USE            |
++----------------------+---------------------------+-------------------+
 | resize*              | one.vm.resize             | VM:MANAGE         |
 +----------------------+---------------------------+-------------------+
 | update               | one.vm.update             | VM:MANAGE         |
@@ -2105,7 +2109,7 @@ The supported attributes are:
 | ``OS``             | ``ARCH``, ``MACHINE``, ``KERNEL``, ``INITRD``, ``BOOTLOADER``, ``BOOT``,       |
 |                    | ``KERNEL_CMD``, ``ROOT``, ``SD_DISK_BUS``, ``UUID``, ``FIRMWARE``              |
 +--------------------+--------------------------------------------------------------------------------+
-|  ``CPU_MODEL``     | ``MODEL``                                                                      |
+|  ``CPU_MODEL``     | ``MODEL``, ``FEATURES``                                                        |
 +--------------------+--------------------------------------------------------------------------------+
 | ``FEATURES``       | ``ACPI``, ``PAE``, ``APIC``, ``LOCALTIME``, ``HYPERV``, ``GUEST_AGENT``,       |
 |                    | ``VIRTIO_SCSI_QUEUES``, ``VIRTIO_BLK_QUEUES``, ``IOTHREADS``                   |

diff --git a/source/intro_release_notes/release_notes_enterprise/resolved_issues_6103.rst b/source/intro_release_notes/release_notes_enterprise/resolved_issues_6103.rst
@@ -7,8 +7,20 @@ A complete list of solved issues for 6.10.3 can be found in the `project develop
 
 The following new features have been backported to 6.10.3:
 
+- Added support for the new NVIDIA mediated devices framework introduced in Ubuntu 24.04. The legacy method remains unaffected by this new feature. For more details, see the :ref:`NVIDIA vGPU documentation <kvm_vgpu>`.
+- `Added capability to change CPU_MODEL/FEATURES with one.vm.updateconf request <https://github.com/OpenNebula/one/issues/6636>`__.
+- `Added new cli command onevm snapshot-list <https://github.com/OpenNebula/one/issues/6623>`__.
 
 The following issues has been solved in 6.10.3:
 
 - `Fix an error when downloading images from HTTP-based marketplaces caused by a missing trailing slash in the ENDPOINT attribute <https://github.com/OpenNebula/one/issues/6619>`__.
 - `Fix VM cluster ID after moving host to different cluster <https://github.com/OpenNebula/one/issues/2226>`__.
+- `Fix corrupted quota after VM deploy and recover --recreate actions, in case RUNNING quota is exceeded <https://github.com/OpenNebula/one/issues/6823>`__.
+
+The following issues have been solved in the Sunstone Web UI:
+
+- `Fix currency symbol not displaying <https://github.com/OpenNebula/one/issues/6846>`__.
+- `Fix making available "Flush" button on FSunstone to resched all VMs in another hosts <https://github.com/OpenNebula/one/issues/6763>`__.
+- `Fix dettach disk or nic is disabled in regular users <https://github.com/OpenNebula/one/issues/6820>`__.
+- `Fix wrong user groups being displayed <https://github.com/OpenNebula/one/issues/6794>`__.
+- `Fix service template role name validation <https://github.com/OpenNebula/one/issues/6816>`__.
diff --git a/source/management_and_operations/vm_management/vm_instances.rst b/source/management_and_operations/vm_management/vm_instances.rst
@@ -565,7 +565,7 @@ Some of the VM configuration attributes defined in the VM Template can be update
 +-------------------+-------------------------------------------------------------------------+
 | ``RAW``           | ``DATA``, ``DATA_VMX``, ``TYPE``, ``VALIDATE``                          |
 +-------------------+-------------------------------------------------------------------------+
-| ``CPU_MODEL``     | ``MODEL``                                                               |
+| ``CPU_MODEL``     | ``MODEL``, ``FEATURES``                                                 |
 +-------------------+-------------------------------------------------------------------------+
 | ``BACKUP_CONFIG`` | ``FS_FREEZE``, ``KEEP_LAST``, ``BACKUP_VOLATILE``, ``MODE``,            |
 |                   | ``INCREMENT_MODE``                                                      |

diff --git a/source/open_cluster_deployment/kvm_node/kvm_driver.rst b/source/open_cluster_deployment/kvm_node/kvm_driver.rst
@@ -28,7 +28,7 @@ The full list of configuration attributes are:
     GRAPHICS  = ["TYPE", "LISTEN", "PASSWD", "KEYMAP", "COMMAND" ]
     VIDEO     = ["TYPE", "IOMMU", "ATS", "VRAM", "RESOLUTION"]
     RAW       = ["DATA", "DATA_VMX", "TYPE", "VALIDATE"]
-    CPU_MODEL = ["MODEL"]
+    CPU_MODEL = ["MODEL", "FEATURES"]
     BACKUP_CONFIG = ["FS_FREEZE", "KEEP_LAST", "BACKUP_VOLATILE", "MODE", "INCREMENT_MODE"]
     CONTEXT (any value, except ETH*, **variable substitution will be made**)
 

diff --git a/source/open_cluster_deployment/kvm_node/vgpu.rst b/source/open_cluster_deployment/kvm_node/vgpu.rst
@@ -139,4 +139,40 @@ Finally, add the following udev rule:
 Using the vGPU
 --------------------------------------------------------------------------------
 
-Once everything is set up, you can follow :ref:`these steps <pci_config>`.
+Once the setup is complete, you can follow the :ref:`general steps <pci_config>` for adding PCI devices to a VM. For NVIDIA GPUs, please consider the following:
+
+- OpenNebula supports both the legacy mediated device interface and the new vendor-specific interface introduced with Ubuntu 24.04. The vGPU device configuration is handled automatically by the virtualization and monitoring drivers. The monitoring process automatically sets the appropriate mode for each device using the ``MDEV_MODE`` attribute.
+
+- NVIDIA vGPUs can be configured using different profiles, which define the vGPU's characteristics and hardware capabilities. These profiles are retrieved from the drivers by the monitoring process, allowing you to easily select the one that best suits your application's requirements.
+
+The following example shows the monitoring information for a NVIDIA vGPU device:
+
+.. prompt:: bash $ auto
+
+    $ onehost show -j 13
+    ...
+        "PCI_DEVICES": {
+        "PCI": [
+          {
+            "ADDRESS": "0000:41:00:4",
+            "BUS": "41",
+            "CLASS": "0302",
+            "CLASS_NAME": "3D controller",
+            "DEVICE": "2236",
+            "DEVICE_NAME": "NVIDIA Corporation GA102GL [A10]",
+            "DOMAIN": "0000",
+            "FUNCTION": "4",
+            "MDEV_MODE": "nvidia",
+            "NUMA_NODE": "-",
+            "PROFILES": "588 (NVIDIA A10-1B),589 (NVIDIA A10-2B),590 (NVIDIA A10-1Q),591 (NVIDIA A10-2Q),592 (NVIDIA A10-3Q),593 (NVIDIA A10-4Q),594 (NVIDIA A10-6Q),595 (NVIDIA A10-8Q),596 (NVIDIA A10-12Q),597 (NVIDIA A10-24Q),598 (NVIDIA A10-1A),599 (NVIDIA A10-2A),600 (NVIDIA A10-3A),601 (NVIDIA A10-4A),602 (NVIDIA A10-6A),603 (NVIDIA A10-8A),604 (NVIDIA A10-12A),605 (NVIDIA A10-24A)",
+            "SHORT_ADDRESS": "41:00.4",
+            "SLOT": "00",
+            "TYPE": "10de:2236:0302",
+            "UUID": "e4042b96-e63d-56cf-bcc8-4e6eecccc12e",
+            "VENDOR": "10de",
+            "VENDOR_NAME": "NVIDIA Corporation",
+            "VMID": "-1"
+          }
+
+.. important::
+    When using NVIDIA cards, ensure that only the GPU (for PCI passthrough) or vGPUs (for SR-IOV) are exposed through the PCI monitoring probe. Do not mix both types of devices in the same configuration.