Bug 1563004
| Summary: | Add drivers for Windows Server 2019 (rhel-7.6) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jeff Nelson <jen> | ||||
| Component: | virtio-win | Assignee: | Danilo de Paula <ddepaula> | ||||
| virtio-win sub component: | distribution | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||
| Severity: | high | ||||||
| Priority: | high | CC: | ailan, asimonel, brian, chayang, chris.smart, coli, darkbasic, ddepaula, jen, jinzhao, juzhang, juzhou, kchamart, knoel, lijin, lmiksik, md, michal.skrivanek, mjankula, mtessun, mvanderw, mxie, mzhan, ngu, phou, qzhang, redhat, salmy, toneata, tzheng, vpagar, wquan, wyu, xfu, xiagao, xiaodwan, yama, yfu, yvugenfi, zili | ||||
| Version: | 7.5 | Keywords: | FutureFeature, ZStream | ||||
| Target Milestone: | beta | ||||||
| Target Release: | 7.6 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | virtio-win-1.9.7-0.el7 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1563005 1639567 1693106 (view as bug list) | Environment: | |||||
| Last Closed: | 2019-08-06 13:34:56 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1563005, 1639567, 1655503, 1659067, 1693106 | ||||||
| Attachments: |
|
||||||
|
Description
Jeff Nelson
2018-04-02 21:52:38 UTC
Our current Windows 10 virtio-win drivers support Windows Server 2019. Should we close this as NOTABUG? Please open bug for RHV Windows Guest Tools ISO if new drivers need to be added within the ISO. Thanks. 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. My fault, I have two similar VMs and I was looking at the one with non-virtio drivers. Works perfectly with 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? (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 Fixed in: virtio-win-1.9.7-0.el7 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 We need a clone. I'm wondering why this wasn't cloned. @Jeff, shouldn't this be done automagically? 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 |