Bug 2033185 - [RFE] Add e1000e driver on cluster level >=4.7
Summary: [RFE] Add e1000e driver on cluster level >=4.7
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: future
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.5.0
: 4.5.0
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On: 2021545
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-16 07:12 UTC by Ales Musil
Modified: 2022-04-20 06:33 UTC (History)
7 users (show)

Fixed In Version: ovirt-engine-4.5.0
Doc Type: Enhancement
Doc Text:
Add e1000e VM Nic type for cluster level 4.7. The e1000 is depracated from RHEL8.0 and users should switch to e1000e when possible.
Clone Of:
Environment:
Last Closed: 2022-04-20 06:33:59 UTC
oVirt Team: Network
Embargoed:
mperina: ovirt-4.5?
pm-rhel: planning_ack?
mperina: devel_ack+
mburman: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44375 0 None None None 2021-12-16 07:19:23 UTC
oVirt gerrit 118035 0 master ABANDONED core: Add e1000e vnic driver 2022-01-03 13:38:29 UTC
oVirt gerrit 118058 0 master MERGED Add E1000E VM nic interface type 2021-12-21 08:56:50 UTC
oVirt gerrit 118176 0 master MERGED core: Add e1000e driver support 2022-01-17 11:58:09 UTC

Description Ales Musil 2021-12-16 07:12:38 UTC 
The old e1000 is not supported anymore in el8, add e1000e which is it's 
PCIe equivalent. The e1000e should be available from cluster level 4.7 on 
q35 chipset, leaving the e1000 available for i440fx.
Comment 1 Michael Burman 2022-03-22 09:24:13 UTC 
Verified on - rhvm-4.5.0-0.237.el8ev.noarch
Comment 2 Sandro Bonazzola 2022-04-20 06:33:59 UTC 
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022.

Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.