Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-0.58]Fix evmcs hyperv vendor bug #8861

Conversation

Barakmor1
Copy link
Member

@Barakmor1 Barakmor1 commented Nov 27, 2022

What this PR does / why we need it:
This is a manual backport PR for #8840
the cherry-pick conflict was redundant import in hyperv_test.go
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

NONE

Currently whenever EVMCS HyperV feature
Is not nil in the vm spec than we require intel vendor.
Even if we set to vmi.Spec.Domain.Features.Hyperv.EVMCS.Enabled
to be false.

Signed-off-by: bmordeha <bmodeha@redhat.com>
@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/M labels Nov 27, 2022
make sure that if we set vmi.Spec.Domain.Features.Hyperv.EVMCS.Enabled
to be false than intel vendor isn't required.

Signed-off-by: bmordeha <bmodeha@redhat.com>
@Barakmor1 Barakmor1 force-pushed the Fix_evmcs_hyperv_vendor_bug_release58 branch from 6e267ec to 3e08057 Compare November 27, 2022 13:32
@fossedihelm
Copy link
Contributor

/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Nov 28, 2022
Copy link
Member

@xpivarc xpivarc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xpivarc

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 kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 28, 2022
@kubevirt-bot kubevirt-bot merged commit 2aabc7d into kubevirt:release-0.58 Nov 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants