Bug 1856591
Summary: | libusbx isn't updated with qemu-kvm | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux Advanced Virtualization | Reporter: | mxie <mxie> |
Component: | qemu-kvm | Assignee: | Miroslav Rezanina <mrezanin> |
qemu-kvm sub component: | General | QA Contact: | yduan |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | coli, ddepaula, hhan, jen, jinzhao, jsuchane, juzhang, juzhou, mrezanin, mzhan, ptoscano, rjones, tyan, tzheng, virt-maint, xiaodwan, yafu, yduan, zili |
Version: | 8.3 | Keywords: | Triaged |
Target Milestone: | rc | ||
Target Release: | 8.3 | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-5.1.0-6.module+el8.3.0+8041+42ff16b8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-17 17:50:15 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
mxie@redhat.com
2020-07-14 02:49:39 UTC
Qemu log: 2020-07-16 05:04:23.772+0000: 888678: error : qemuProcessQMPLaunch:8531 : internal error: Failed to start QEMU binary /usr/libexec/qemu-kvm for probing: 2020-07-16 05:04:23.752+0000: 888761: debug : virFileClose:134 : Closed fd 34 /usr/libexec/qemu-kvm: symbol lookup error: /usr/libexec/qemu-kvm: undefined symbol: libusb_wrap_sys_device 2020-07-16 05:04:23.772+0000: 888678: warning : virQEMUCapsLogProbeFailure:5376 : Failed to probe capabilities for /usr/libexec/qemu-kvm: internal error: Failed to start QEMU binary /usr/libexec/qemu-kvm for probing: 2020-07-16 05:04:23.752+0000: 888761: debug : virFileClose:134 : Closed fd 34 /usr/libexec/qemu-kvm: symbol lookup error: /usr/libexec/qemu-kvm: undefined symbol: libusb_wrap_sys_device 2020-07-16 05:04:23.772+0000: 888678: error : virQEMUCapsCacheLookup:5650 : internal error: no capabilities available for /usr/libexec/qemu-kvm Assigned to Jeff for initial triage per bz process and age of bug created or assigned to virt-maint without triage Using the latest compose RHEL-8.3.0-20200721.n.0, libusbx version is 1.0.23-3. # rpm -q libusbx libusbx-1.0.23-3.el8.x86_64 There are several versions of qemu-kvm mentioned in the problem description. They all start with "qemu-kvm-5.0.0". That means the system has the qemu-kvm that is part of RHEL AV. In fact, one can tell that this is happening because the last version contains the string "wrb" (weekly rebase). Here are the mentions: > 1.Check current version of qemu-kvm and libusbx > # rpm -q qemu-kvm libusbx > qemu-kvm-5.0.0-0.module+el8.3.0+6620+5d5e1420.x86_64 > libusbx-1.0.22-1.el8.x86_64 > > >2.Configure correct repo to update qemu-kvm to latest version but found libusbx is not updated with qemu-kvm together and qemu-kvm doesn't depend on libusbx > >2.1 # yum update qemu-kvm -y > >2.2 # rpm -q qemu-kvm libusbx >qemu-kvm-5.0.0-0.module+el8.3.0+7323+d54bb644.wrb200701.x86_64 >libusbx-1.0.22-1.el8.x86_64 > >2.3 # yum deplist qemu-kvm >...... >package: qemu-kvm-15:5.0.0-0.module+el8.3.0+7323+d54bb644.wrb200701.x86_64 This appears to be a legitimate bug; it appears that the qemu-kvm package doesn't have the correct dependency to libusbx. Moving this report to the RHEL AV product, reassigning for followup and setting ITR to 8.3.0. Fixed in the rebase Still can reproduce this problem with qemu-kvm-5.1.0-4.module+el8.3.0+7846+ae9b566f.x86_64 and libusbx-1.0.22-1.el8.x86_64. # yum deplist ./qemu-kvm-core-5.0.0-0.module+el8.3.0+7323+d54bb644.wrb200701.x86_64.rpm | grep usb Last metadata expiration check: 0:09:05 ago on Mon 07 Sep 2020 10:18:31 AM EDT. dependency: libusb-1.0.so.0()(64bit) provider: libusbx-1.0.23-4.el8.x86_64 dependency: libusbredirparser.so.1()(64bit) provider: usbredir-0.8.0-1.el8.x86_64 dependency: libusbx >= 1.0.19 <============================= provider: libusbx-1.0.23-4.el8.i686 provider: libusbx-1.0.23-4.el8.x86_64 dependency: usbredir >= 0.7.1 provider: usbredir-0.8.0-1.el8.i686 provider: usbredir-0.8.0-1.el8.x86_64 # yum deplist ./qemu-kvm-core-5.1.0-4.module+el8.3.0+7846+ae9b566f.x86_64.rpm | grep usb Last metadata expiration check: 0:09:52 ago on Mon 07 Sep 2020 10:18:31 AM EDT. dependency: libusb-1.0.so.0()(64bit) provider: libusbx-1.0.23-4.el8.x86_64 dependency: libusbx >= 1.0.19 <============================= provider: libusbx-1.0.23-4.el8.i686 provider: libusbx-1.0.23-4.el8.x86_64 dependency: usbredir >= 0.7.1 provider: usbredir-0.8.0-1.el8.i686 provider: usbredir-0.8.0-1.el8.x86_64 IIUC, there is no change for qemu-kvm dependency to libusbx. Should be working now. # yum deplist ./qemu-kvm-core-5.0.0-0.module+el8.3.0+7323+d54bb644.wrb200701.x86_64.rpm | grep usb Last metadata expiration check: 2:42:25 ago on Thu 10 Sep 2020 09:39:08 PM EDT. dependency: libusb-1.0.so.0()(64bit) provider: libusbx-1.0.23-4.el8.x86_64 dependency: libusbredirparser.so.1()(64bit) provider: usbredir-0.8.0-1.el8.x86_64 dependency: libusbx >= 1.0.19 <============================= provider: libusbx-1.0.23-4.el8.i686 provider: libusbx-1.0.23-4.el8.x86_64 dependency: usbredir >= 0.7.1 provider: usbredir-0.8.0-1.el8.i686 provider: usbredir-0.8.0-1.el8.x86_64 # yum deplist ./qemu-kvm-core-5.1.0-6.module+el8.3.0+8041+42ff16b8.x86_64.rpm | grep usb Last metadata expiration check: 2:41:25 ago on Thu 10 Sep 2020 09:39:08 PM EDT. dependency: libusb-1.0.so.0()(64bit) provider: libusbx-1.0.23-4.el8.x86_64 dependency: libusbx >= 1.0.23 <============================= provider: libusbx-1.0.23-4.el8.i686 provider: libusbx-1.0.23-4.el8.x86_64 dependency: usbredir >= 0.7.1 provider: usbredir-0.8.0-1.el8.i686 provider: usbredir-0.8.0-1.el8.x86_64 Clear the NEEDINFO. 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 (virt:8.3 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-2020:5137 |