Bug 1869208 - Limit UI network model choices to what q35 supports (virtio + e1000e)
Summary: Limit UI network model choices to what q35 supports (virtio + e1000e)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 2.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 2.6.0
Assignee: sgott
QA Contact: Israel Pinto
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-17 09:51 UTC by Fabian Deutsch
Modified: 2021-04-29 08:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-31 14:11:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Fabian Deutsch 2020-08-17 09:51:27 UTC
Description of problem:
Today kubevirt allows to select

"Interface model. One of: e1000, e1000e, ne2k_pci, pcnet, rtl8139, virtio. Defaults to virtio."

We should limit the options to what q35 permits or what is ideal to q35 which is aong the lines of
e1000e, ne2k_pci and virtio -- this should be checked

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Go to the UI or API and check which network modesl can be set
2.
3.

Actual results:
Many models can be set

Expected results:
Optimal models can be set

Additional info:

Comment 5 Fabian Deutsch 2020-08-31 10:29:31 UTC
q35 supports (beyond others) virtio and e1000e - both together cover recent WIndows guests and Linux distributions.

Comment 7 Yaacov Zamir 2020-08-31 12:57:10 UTC

*** This bug has been marked as a duplicate of bug 1869620 ***

Comment 8 Yaacov Zamir 2020-08-31 13:00:40 UTC
Re opining : this BZ is about the API not the UI, the UI side is handled in https://bugzilla.redhat.com/show_bug.cgi?id=1869620

Comment 9 Petr Horáček 2020-08-31 14:11:12 UTC
We will not drop unsupported models from API. It may be useful for workarounds or PoCs. And if we remove it from UI and docs, blocking it in our codebase would be redundant.


Note You need to log in before you can comment on or make changes to this bug.