Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-38160

Add virt-host-validate and systemd-detect-virt to CNV must-gather

XMLWordPrintable

    • cnv-must-gather-extension-4.19
    • Hide

      Have the data from the above command collected in MG

      Show
      Have the data from the above command collected in MG
    • Green
    • To Do
    • CNV-11934 - Improved troubleshooting
    • 100% To Do, 0% In Progress, 0% Done
    • dev-ready, doc-ready, po-ready, qe-ready, ux-ready
    • Hide

      2023-12-04: automation in review....

      Show
      2023-12-04: automation in review....

      Goal

      We want to have greater visibilty to where CNV is installed.

      `virt-host-validate` command is used to validate that the host machine is configured correctly to support virtualization. When you run virt-host-validate, it performs a series of checks to ensure that the virtualization environment is properly set up and capable of running virtual machines (VMs) efficiently and securely.

      `systemd-detect-virt` command is is used to detect if the system is running in a virtualized environment and, if so, which virtualization technology is being used. 

      When you run systemd-detect-virt, it performs checks to determine:

      Virtualization Technology: Whether the system is running inside a virtual machine (VM) or container, and it identifies the specific virtualization technology (e.g., QEMU/KVM, Xen, VMware, Microsoft Hyper-V, Oracle VirtualBox, LXC, Docker, etc.).

      Type of Virtualization: It differentiates between full virtualization technologies (where an entire machine is simulated) and containerization technologies (which share the host's kernel but provide isolated user spaces).

      User Stories

      • As a developer I would like to get additional information in the CNV must-gather collected from virt-host-validate and systemd-detect-virt to be able to help us to know where CNV is installed, so that we can priorities and plan our work and testing.

      Non-Requirements

      • List of things not included in this epic, to alleviate any doubt raised during the grooming process.

      Notes

      • Any additional details or decisions made/needed

      Done Checklist

      Who What Reference
      DEV Upstream roadmap issue (or individual upstream PRs) <link to GitHub Issue>
      DEV Upstream documentation merged <link to meaningful PR>
      DEV gap doc updated <name sheet and cell>
      DEV Upgrade consideration <link to upgrade-related test or design doc>
      DEV CEE/PX summary presentation label epic with cee-training and add a <link to your support-facing preso>
      QE Test plans in Polarion <link or reference to Polarion>
      QE Automated tests merged <link or reference to automated tests>
      DOC Downstream documentation merged <link to meaningful PR>

            stirabos Simone Tiraboschi
            sradco Shirly Radco
            Debarati Basu-Nag Debarati Basu-Nag
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: