kubevirt icon indicating copy to clipboard operation
kubevirt copied to clipboard

GA BochsDisplayForEFIGuests

Open xpivarc opened this issue 1 year ago • 9 comments

What this PR does

Promote Boshs display as default for EFI x86 guests. For retaining the compatibility (in case some guest need direct access) we provide kubevirt.io/vga-display-efi-x86 annotation on the Kubevirt CR that needs to be set before cluster upgrade.

Fixes #

Special notes for your reviewer

Release note

BochsDisplayForEFIGuests is GAed, use  "kubevirt.io/vga-display-efi-x86" annotation on Kubevirt CR before upgrading in case you need retain compatibility.

xpivarc avatar Sep 30 '24 12:09 xpivarc

Skipping CI for Draft Pull Request. If you want CI signal for your change, please convert it to an actual PR. You can still manually trigger a test run with /test all

kubevirt-bot avatar Sep 30 '24 12:09 kubevirt-bot

/lgtm

fossedihelm avatar Oct 10 '24 08:10 fossedihelm

/cc

jean-edouard avatar Oct 14 '24 13:10 jean-edouard

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jean-edouard

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

kubevirt-bot avatar Oct 14 '24 13:10 kubevirt-bot

Required labels detected, running phase 2 presubmits: /test pull-kubevirt-e2e-windows2016 /test pull-kubevirt-e2e-kind-1.30-vgpu /test pull-kubevirt-e2e-kind-sriov /test pull-kubevirt-e2e-k8s-1.30-ipv6-sig-network /test pull-kubevirt-e2e-k8s-1.29-sig-network /test pull-kubevirt-e2e-k8s-1.29-sig-storage /test pull-kubevirt-e2e-k8s-1.29-sig-compute /test pull-kubevirt-e2e-k8s-1.29-sig-operator /test pull-kubevirt-e2e-k8s-1.30-sig-network /test pull-kubevirt-e2e-k8s-1.30-sig-storage /test pull-kubevirt-e2e-k8s-1.30-sig-compute /test pull-kubevirt-e2e-k8s-1.30-sig-operator

kubevirt-commenter-bot avatar Oct 14 '24 13:10 kubevirt-commenter-bot

/lgtm

fossedihelm avatar Oct 16 '24 12:10 fossedihelm

Required labels detected, running phase 2 presubmits: /test pull-kubevirt-e2e-windows2016 /test pull-kubevirt-e2e-kind-1.30-vgpu /test pull-kubevirt-e2e-kind-sriov /test pull-kubevirt-e2e-k8s-1.30-ipv6-sig-network /test pull-kubevirt-e2e-k8s-1.29-sig-network /test pull-kubevirt-e2e-k8s-1.29-sig-storage /test pull-kubevirt-e2e-k8s-1.29-sig-compute /test pull-kubevirt-e2e-k8s-1.29-sig-operator /test pull-kubevirt-e2e-k8s-1.30-sig-network /test pull-kubevirt-e2e-k8s-1.30-sig-storage /test pull-kubevirt-e2e-k8s-1.30-sig-compute /test pull-kubevirt-e2e-k8s-1.30-sig-operator

kubevirt-commenter-bot avatar Oct 16 '24 12:10 kubevirt-commenter-bot

/unhold

jean-edouard avatar Oct 16 '24 13:10 jean-edouard

@fossedihelm Rebased

xpivarc avatar Oct 21 '24 06:10 xpivarc

/lgtm Thanks

fossedihelm avatar Oct 21 '24 06:10 fossedihelm

Required labels detected, running phase 2 presubmits: /test pull-kubevirt-e2e-windows2016 /test pull-kubevirt-e2e-kind-1.30-vgpu /test pull-kubevirt-e2e-kind-sriov /test pull-kubevirt-e2e-k8s-1.30-ipv6-sig-network /test pull-kubevirt-e2e-k8s-1.29-sig-network /test pull-kubevirt-e2e-k8s-1.29-sig-storage /test pull-kubevirt-e2e-k8s-1.29-sig-compute /test pull-kubevirt-e2e-k8s-1.29-sig-operator /test pull-kubevirt-e2e-k8s-1.30-sig-network /test pull-kubevirt-e2e-k8s-1.30-sig-storage /test pull-kubevirt-e2e-k8s-1.30-sig-compute /test pull-kubevirt-e2e-k8s-1.30-sig-operator

kubevirt-commenter-bot avatar Oct 21 '24 06:10 kubevirt-commenter-bot

use "kubevirt.io/vga-display-efi-x86" annotation on Kubevirt CR before upgrading in case you need retain compatibility.

This is a bad hack which has been suggested in several scenarios and sometime successfully stoped.

I understand we have not agreed yet about using such API patterns.

EdDev avatar Oct 21 '24 11:10 EdDev

use "kubevirt.io/vga-display-efi-x86" annotation on Kubevirt CR before upgrading in case you need retain compatibility.

This is a bad hack which has been suggested in several scenarios and sometime successfully stoped.

I understand we have not agreed yet about using such API patterns.

We don't have API patterns afaik. There is precedence of using annotations, especially for hacks/escape hatch

xpivarc avatar Oct 21 '24 13:10 xpivarc