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:
$ /usr/libexec/qemu-kvm -M virt-rhel7.4.0 -device nec-usb-xhci,\?
qemu-kvm: -device nec-usb-xhci,?: Device 'nec-usb-xhci' not found
* Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.9.0-1.el7.aarch64
* How reproducible:
always
* Additional info:
On my x86_64 laptop, using the same build:
$ /usr/libexec/qemu-kvm -M pc-q35-rhel7.4.0 -device nec-usb-xhci,\?
[bunch of properties]
Vaguely related: bug 1438682.
(In reply to Laszlo Ersek from comment #0)
> Vaguely related: bug 1438682
That bug is more than vaguely related: since it's going to
be fixed really soon (it's in POST already) I believe there
is no need to drag nec-usb-xhci back in, as libvirt will
pick qemu-xhci over it anyway.
Comment 5Miroslav Rezanina
2017-05-09 15:20:10 UTC
There were no xhci support in RHEL aarch64 qemu-kvm-rhev. We need to add any in case we want to use it.
In today's virt-arm call Mirek confirmed we never had the NEC controller enabled for the aarch64 target in downstream, so this is not a regression. Instead, it is an RFE.
And then, we should enable the qemu-xhci flavor instead.
Comment 7Miroslav Rezanina
2017-05-15 11:37:59 UTC
Do we want to enable qemu-xhci and keep nec-usb-xhci disabled?
As both of the devices are enabled toegether in 2.9.0 we would need add way to be able to select supported xhci device(s). I would like to avoid this change unless we really need only qemu-xhci.
(In reply to Miroslav Rezanina from comment #7)
> Do we want to enable qemu-xhci and keep nec-usb-xhci disabled?
>
> As both of the devices are enabled toegether in 2.9.0 we would need add way
> to be able to select supported xhci device(s). I would like to avoid this
> change unless we really need only qemu-xhci.
OK for now, but let's clone this bug to track upstream work that will allow us to untangle them. As usual we don't want to compile code that we don't want to support, and we don't want to support nec-usb-xhci on aarch64.
Comment 11Miroslav Rezanina
2017-05-23 08:14:49 UTC
This BZ is being closed as CURRENTRELEASE because it falls
into the following criteria:
o It's an aarch64 virt BZ for RHEL7
o It's on ON_QA or VERIFIED state
o Resolution seems to be in place for some years
If you have objections, please add a comment or re-open the BZ.