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.
DescriptionWainer dos Santos Moschetta
2018-05-22 22:07:50 UTC
Description of problem:
The qemu-kvm (via virsh) was unable to detect GIC support on some Qualcomm Amberwing machines with chip that has GICv4.
We were executing CI jobs on Amberwing machines properly but then some test cases started failing due the inability to detect GIC. Even on machines that used to pass the tests (e.g. qualcomm-amberwing-rep-09.khw3.lab.eng.bos.redhat.com), now are failing.
Version-Release number of selected component (if applicable):
qemu-kvm-ma-2.10.0-21.el7.aarch64
How reproducible:
It was reproduced on two machines from Beaker:
qualcomm-amberwing-rep-05.khw3.lab.eng.bos.redhat.com (Model 65-LA-115-151)
qualcomm-amberwing-rep-16.khw3.lab.eng.bos.redhat.com (Model CV90-LA115-P111)
Steps to Reproduce:
1. Provision an Amberwing machine from Beaker with RHEL-ALT-7.5 aarch64
2. Install qemu-kvm-ma, libvirt and libvirt-client packages.
3. Run "virsh domcapabilities --machine virt --virttype kvm | grep gic"
Actual results:
<gic supported='no'/>
Expected results:
<gic supported='yes'>
</gic>
Additional info:
# uname -a
Linux qualcomm-amberwing-rep-16.khw3.lab.eng.bos.redhat.com 4.14.0-49.el7a.aarch64 #1 SMP Wed Mar 14 10:02:34 EDT 2018 aarch64 aarch64 aarch64 GNU/Linux
# grep GIC /var/log/messages
May 22 01:20:04 qualcomm-amberwing-rep-16 kernel: GICv3: GIC: Using split EOI/Deactivate mode
May 22 01:20:04 qualcomm-amberwing-rep-16 kernel: GICv3: Distributor has no Range Selector support
May 22 01:20:04 qualcomm-amberwing-rep-16 kernel: GICv3: VLPI support, no direct LPI support
May 22 01:20:04 qualcomm-amberwing-rep-16 kernel: GIC: enabling workaround for ITS: QDF2400 erratum 0065
May 22 01:20:04 qualcomm-amberwing-rep-16 kernel: GIC: using LPI property table @0x00000017c0510000
May 22 01:20:04 qualcomm-amberwing-rep-16 kernel: ITS: Allocated DevID ffffffff as GICv4 proxy device (64 slots)
May 22 01:20:04 qualcomm-amberwing-rep-16 kernel: ITS: Enabling GICv4 support
May 22 01:20:04 qualcomm-amberwing-rep-16 kernel: GICv3: CPU0: found redistributor 0 region 0:0x000000ff7f000000
<... OUTPUT OMITTED ...>
May 22 01:20:04 qualcomm-amberwing-rep-16 kernel: GICv3: CPU45: found redistributor 1701 region 45:0x000000ff7fbc0000
May 22 01:20:04 qualcomm-amberwing-rep-16 kernel: CPU features: detected feature: GIC system register CPU interface
May 22 01:20:04 qualcomm-amberwing-rep-16 kernel: ACPI: Using GIC for interrupt routing
# On machine that detects GIC properly you can see messages like:
[ 4.645854] kvm [1]: 16-bit VMID
[ 4.648909] kvm [1]: IDMAP page: 1213000
[ 4.652815] kvm [1]: HYP VA range: 800000000000:ffffffffffff
[ 4.658627] kvm [1]: GICv4 support disabled
[ 4.662623] kvm [1]: GICv3: no GICV resource entry
[ 4.667409] kvm [1]: disabling GICv2 emulation
[ 4.671825] kvm [1]: GIC system register CPU interface enabled
[ 4.678245] kvm [1]: vgic interrupt IRQ1
[ 4.681550] kvm [1]: virtual timer IRQ3
[ 4.685908] kvm [1]: Hyp mode initialized successfully
This is a known issue being tracked by bug 1580461. The amberwing firmware needs to be updated to properly populate the ACPI tables for the vgic interrupt.
*** This bug has been marked as a duplicate of bug 1580461 ***