Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Windows Server 2019 was announced on March 20, 2018.
Create and populate a directory structure for drivers that matches how we support drivers in other Windows releases.
Comment 1Yvugenfi@redhat.com
2018-07-15 07:35:59 UTC
Our current Windows 10 virtio-win drivers support Windows Server 2019.
Created attachment 1499497[details]
Windows Server 2019 doesn't accept the NetKVM driver
Can you please link me te RHV Windows Guest Tools ISO bug report?
The following instructions are no longer true for Windows Server 2019: https://access.redhat.com/articles/2470791
First of all, 99% of the devices don't show up anymore in the "Other devices" group, which makes finding them very difficult. If I right click the .inf file and I manually select "Install" (as suggested here: https://pve.proxmox.com/wiki/Windows_2012_guest_best_practices) nothing happens.
Take for example the NetKVM driver: if I right click the "Intel PRO/1000 MT Network Connection" device, then "Update driver" and selecting the virtual CD-ROM with latest virtio-win the driver doesn't show up. If I try to manually pick the driver from the NetKVM folder it does show up, but Windows complains (see attached screenshot). I'm pretty sure that we need updated drivers and updated instructions for Windows Server 2019.
(In reply to Jeff Nelson from comment #0)
> Description of problem:
> Windows Server 2019 was announced on March 20, 2018.
>
> Create and populate a directory structure for drivers that matches how we
> support drivers in other Windows releases.
So, as Li Jin pointed in Bug 169567 comment 9, this is not just a matter of copying the w10 driver into a new folder.
We need to have the driver signed for W2k19, and this didn't happened yet.
Li Jin, do you have an estimate about when this is going to happen?
Comment 14Michal Skrivanek
2018-12-13 14:05:47 UTC
(In reply to Sandro Bonazzola from comment #6)
> Please open bug for RHV Windows Guest Tools ISO if new drivers need to be
> added within the ISO.
> Thanks.
opened bug 1659067 for rhv tools iso
also, for qemu-ga reporting see bug 1659071
verify with virtio-win-1.9.7-0.el7: win2019 drivers exist in both /usr/share/virtio-win/drivers/amd64/, virtio-win-1.9.7_servers_amd64.vfd and virtio-win-1.9.7.iso
So change status to verified
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:2362