| Summary: | [regression] Guest usb mouse/keyboard could not be used on qemu-kvm-rhev-2.3.0-24.el7.ppc64le | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Gu Nini <ngu> |
| Component: | qemu-kvm-rhev | Assignee: | David Gibson <dgibson> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.2 | CC: | areis, dgibson, juzhang, knoel, kraxel, lmiksik, lvivier, michen, mrezanin, qzhang, virt-maint, xuhan, zhengtli |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | ppc64le | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-rhev-2.3.0-25.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-04 16:58:37 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: | |
|
Description
Gu Nini
2015-09-21 11:11:49 UTC
I can reproduce this. It happens with qemu-kvm-rhev-2.3.0-24.el7.x86_64 but not with upstream qemu. What seems to be happening is that the ohci driver in the guest isn't binding to the device, but I'm not sure why yet - there aren't any obvious error messages. Interestingly SLOF *is* able to see and use the USB device. But neither BE nor LE Linux guest is. I think I've tracked this down to the patches moving PCI device node creation to qemu. Specifically we're missing upstream commit 4a7c347 which means the guest isn't getting the class code information it needs to match the OHCI driver to the device. Case for blocker status:
* This represents a serious regression - USB interfaces (and possibly other PCI devices) won't work in Power guests any more.
* The fix is small, low-risk and already upstream.
Karen, Miya, if you could add some ACKs to this please.
I found PCI devices sequence has been reversed. If there are two or more virtio-blk storages, in this case, guest would assign the low address device with a "newer" nodename (e.g. /dev/vdb), and this behavior is different from previous. 2015-09-21 09:27:48: Populating /pci@800000020000000 2015-09-21 09:27:48: 00 3000 (D) : 1af4 1000 virtio [ net ] 2015-09-21 09:27:48: 00 2800 (D) : 1af4 1001 virtio [ block ] 2015-09-21 09:27:48: 00 2000 (D) : 1af4 1001 virtio [ block ] 2015-09-21 09:27:48: 00 1800 (D) : 106b 003f serial bus [ usb-ohci ] 2015-09-21 09:27:48: 00 0000 (D) : 1234 1111 2015-09-21 09:27:48: qemu vga Is it the same cause with this issue? Xu Han, Yes the change in device order probably has the same cause. THe move to qemu DT construction is likely to have changed the order of nodes in the flattened tree, which in turn might affect guest probe order. However, guests shouldn't generally rely on probe order (that's why mount by UUID is a good idea). So I'm not sure it's a bug. Xu Han, Yes the change in device order probably has the same cause. THe move to qemu DT construction is likely to have changed the order of nodes in the flattened tree, which in turn might affect guest probe order. However, guests shouldn't generally rely on probe order (that's why mount by UUID is a good idea). So I'm not sure it's a bug. Fix included in qemu-kvm-rhev-2.3.0-25.el7 Have updated to qemu-kvm-rhev-2.3.0-25.el7.ppc64le, for the guest new booted up, usb mouse/keyboard could be used correctly now, so the bug should be verified. While for the PCI devices sequence reversed issue mentioned in comment 4, we should do more checks. The original bug has been verified pass in comment 8. And for the pci device order issue in comment 4, it still exists in the latest qemu-kvm-rhev-2.3.0-26. I created a separate Red Hatbug 1266385, let's move the discussion here. So I will set this bug to VERIFIED first. 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://rhn.redhat.com/errata/RHBA-2015-2546.html |