Bug 1313470

Summary:	advertise e1000 supported for windows
Product:	[Community] Virtualization Tools	Reporter:	Agostino Sarubbo <ago>
Component:	libosinfo	Assignee:	Fabiano Fidêncio <fidencio>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	berrange, cfergeau, crobinso, fidencio, gscrivan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-01 06:57:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Agostino Sarubbo 2016-03-01 16:22:58 UTC

I did an installation of a WINDOWS 7 guest. If I don't specify anything it picks rtl8139 as default.

Since I need a gigabit card I need to specify model=e1000.


So I guess virt-install should pick e1000 instead of rtl3189 by default.


on this system I have:
horizon ~ # qemu-system-x86_64 -net nic,model=?
qemu: Supported NIC models: ne2k_pci,i82551,i82557b,i82559er,rtl8139,e1000,pcnet,virtio


horizon ~ # virt-install --version
1.3.2

Comment 1 Daniel Berrangé 2016-03-01 16:26:14 UTC

Looking at the libosinfo database, it appears that the windows XML data files are configured on the assumption that the application will be installing the windows virtio driver add-ons.

This may be desirable, but we shouldn't assume that, so I think libosinfo database probably ought to *also* list e1000 as a valid NIC for windows, so that e1000 gets used in cases where virtio drivers are not installed by the virt-manager

Comment 3 Fabiano Fidêncio 2018-10-01 06:57:45 UTC

master:
 9de37b18e826636d24c8f4641e53dfcf07163d30