Bug 1313470 - advertise e1000 supported for windows
advertise e1000 supported for windows
Status: NEW
Product: Virtualization Tools
Classification: Community
Component: libosinfo (Show other bugs)
unspecified
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthias Clasen
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-01 11:22 EST by Agostino Sarubbo
Modified: 2016-09-19 21:46 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Agostino Sarubbo 2016-03-01 11:22:58 EST
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 Berrange 2016-03-01 11:26:14 EST
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

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