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

[Tech Preview] Allow VM-owners to explicitly set the video device type

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • CNV v4.21.0
    • None
    • CNV Virt-Cluster
    • None
    • video-device-type
    • Product / Portfolio Work
    • 77
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • Green
    • In Progress
    • 0% To Do, 17% In Progress, 83% Done
    • doc-ready
    • Tech Preview
    • Hide

      2025-12-01:
      Dev work is done. Docs work In Progress....

      Show
      2025-12-01: Dev work is done. Docs work In Progress....

      Background

      • The VideoConfig feature gate was introduced as Alpha (Dev Preview) to allow users to explicitly configure the video device type for their VirtualMachines.
        Previously, KubeVirt automatically selected a default video device based on the architecture and firmware type (e.g., VGA or Bochs for AMD64, virtio for ARM and s390x), without user configurability.

      Goal

      • Promote the VideoConfig feature gate to Beta (Tech Preview), signaling increased stability and readiness for wider adoption.
        This enables VM owners to confidently use the video configuration field in production-like environments to specify the desired video model (e.g., virtio, bochs, vga) supported by the target architecture.
      • Enable the FG to be active by default

       

      User Stories

      • As a VM owner, I want to reliably configure the video device type in my VM spec so that I can use the most suitable video model for my architecture.
      • As a cluster administrator, I want to enable the VideoConfig feature gate in Tech Preview mode to validate the feature’s behavior under production workloads before general availability.

      Non-Requirements

      • No new video device types are introduced as part of this promotion.
      • No changes to the default video device behavior when the feature gate is not active.

      Notes

      • The promotion to Beta (Tech Preview) reflects feature maturity, broader test coverage, and community validation.
      • Documentation updates will provide clear guidance on supported video models per architecture and instructions for enabling the feature gate.

          1.
          upstream roadmap issue Sub-task New Undefined Unassigned
          2.
          upstream design Sub-task New Undefined Unassigned
          3.
          upstream documentation Sub-task New Undefined Unassigned
          4.
          upstream roadmap issue Sub-task New Undefined Unassigned
          5.
          upgrade consideration Sub-task New Undefined Unassigned
          6.
          upstream design Sub-task New Undefined Unassigned
          7.
          test plans in polarion Sub-task New Undefined Unassigned
          8.
          upstream documentation Sub-task New Undefined Unassigned
          9.
          automated tests Sub-task New Undefined Unassigned
          10.
          upgrade consideration Sub-task New Undefined Unassigned
          11.
          downstream documentation merged Sub-task New Undefined Unassigned
          12.
          test plans in polarion Sub-task New Undefined Unassigned
          13.
          CNV QE DevOps Requirement/Enablement Sub-task New Undefined Unassigned
          14.
          automated tests Sub-task New Undefined Unassigned
          15.
          downstream documentation merged Sub-task New Undefined Unassigned
          16.
          CNV QE DevOps Requirement/Enablement Sub-task New Undefined Unassigned

              rh-ee-dsionov Daniel Sionov
              kbidarka@redhat.com Kedar Bidarkar
              Akriti gupta Akriti gupta
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: