Bug 2153741
| Summary: | [fwcfg 32bit support] osinfo-db does not know about the "fwcfg" virtio-win driver | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Laszlo Ersek <lersek> |
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> |
| virtio-win sub component: | distribution | QA Contact: | leidwang <leidwang> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | coli, jinzhao, juzhang, tpelka, victortoso, vrozenfe, ymankad |
| Version: | unspecified | Keywords: | Reopened, RFE, Triaged |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-09 07:55:12 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: | 1983947 | ||
| Bug Blocks: | 2151752 | ||
|
Description
Laszlo Ersek
2022-12-15 10:34:32 UTC
(Originally encountered under bug 2151752.) Ok, should be a matter of extending the commit https://gitlab.com/libosinfo/osinfo-db/-/commit/43913618247a70ed7727dcf24e5b560507ccaf20 Just a quick update. Current osinfo-db uses virtio-win from 2019 which does not have fwcfg in it [0] [0] https://fedorapeople.org/groups/virt/unattended/drivers/preinst/virtio-win/0.1.171/w10/x86/ So, we need to unpack a new virtio-win release into fedorapeople.org/groups/virt/* and then update osinfo-db with new files per windows releases. I plan to have this fixed for 9.2 so devel_ack+ Hi Laszlo, Do you have an easy way to test installation of osinfo-db's windows drivers? I got osinfo-db updated in osinfo-db!552 but I'm not sure what is the best way to test win 10 and win 11, only win 8.1 https://gitlab.com/libosinfo/osinfo-db/-/merge_requests/552 Hi Victor, thanks for the osinfo-db update. The best (or at least "original") way for testing this would be for you to build a new RHEL-9 package (official development build, or just a scratch build), and then to hand that to the Virt-Tools QE team. They could repeat the virt-v2v conversions from bug 2151752, for the win2022, win11, win2019, win10 guests, and then we could verify from the conversion logs that virt-v2v located the drivers from "virtio-win-1.9.30-0.el9_1.noarch" based on the osinfo content. For this, it would also be necessary that the new RHEL-9 osinfo-db package match the latest content of virtio-win in RHEL-9. (currently 1.9.30-0.el9_1, IIUC.) Thanks! The transition to fwcfg driver is not complete yet, so there is no point in updating osinfo-db for incomplete/unsupported drivers. I still plan to update virtio-win references in osinfo-db upstream and in fedora. Any suggestions on how properly test them from osinfo-db or host-side installation of those drivers are very much welcomed! Removing devel-ack, we should probably address this in 9.3.0. Radek, I'm removing ITM/DTM just to be sure the bot would not nag us latter. Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. Moving to virtio-win. fwcfg driver can be installed/uninstalled by the new installer in virtio-win-1.9.33-0.el9_2,move the bz to verified.Thanks! 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 (virtio-win bug fix and enhancement update), 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-2023:2451 |