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.
Bug 1326420 - AArch64: clean and add devices to fully support aarch64 vm
Summary: AArch64: clean and add devices to fully support aarch64 vm
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.3
Hardware: aarch64
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1173755 1221569
TreeView+ depends on / blocked
 
Reported: 2016-04-12 15:45 UTC by Andrew Jones
Modified: 2019-06-01 11:11 UTC (History)
6 users (show)

Fixed In Version: qemu-kvm-rhev-2.6.0-5.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-01 11:11:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
kvm-Add-i82801b11-bridge-device-for-AArch64.patch (385 bytes, patch)
2016-06-16 05:40 UTC, Jon Masters 		no flags Details | Diff
View All

Description Andrew Jones 2016-04-12 15:45:06 UTC 
expand build to include chips needed for pci hotplug
Comment 1 Jon Masters 2016-04-12 17:58:51 UTC 
Any more context on this?
Comment 2 Andrew Jones 2016-05-04 13:46:20 UTC 
Bumping the priority of this.

We're currently actively reducing the devices we build for qemu-kvm-rhev and have now lost the ability to manage our guests on ARM with libvirt, because libvirt expects certain PCI bridges to be available. Here's the error you get when attempting a virt-install

ERROR    unsupported configuration: the dmi-to-pci-bridge (i82801b11-bridge) controller is not supported in this QEMU binary

We need to determine what's necessary for the AArch64 build in order to support PCIe and PCIe hotplug, and then also make sure libvirt (bug 1244151) only adds those devices/bridges by default.
Comment 3 Wei Huang (AMD) 2016-05-06 14:42:49 UTC 
(In reply to Andrew Jones from comment #2)
> Bumping the priority of this.
> 
> We're currently actively reducing the devices we build for qemu-kvm-rhev and
> have now lost the ability to manage our guests on ARM with libvirt, because
> libvirt expects certain PCI bridges to be available. Here's the error you
> get when attempting a virt-install
> 
> ERROR    unsupported configuration: the dmi-to-pci-bridge (i82801b11-bridge)
> controller is not supported in this QEMU binary
> 
> We need to determine what's necessary for the AArch64 build in order to
> support PCIe and PCIe hotplug, and then also make sure libvirt (bug 1244151)
> only adds those devices/bridges by default.

What parameters you used in virt-install? I want to reproduce it myself.
Comment 4 Andrew Jones 2016-05-06 18:04:05 UTC 
(In reply to Wei Huang from comment #3)
> What parameters you used in virt-install? I want to reproduce it myself.

virt-install -n rhelsa -l $PATH_TO_REPO --vcpus=4 --memory 4096 --disk size=6 --network default --boot uefi
Comment 5 Wei Huang (AMD) 2016-05-27 21:41:50 UTC 
Since RHELSA 7.2, we have been pretty strict about the supported devices. Going forward we want to keep the same rule, in the meanwhile we also want to expand the scope of supported devices to cover new features (e.g. hotplug). 

So I expand the scope of this BZ to cover the following two items:
* add necessary devices to qemu to support new features
* trim the devices we don't want to make sure the list is as minimal as possible

-Wei
Comment 6 Miroslav Rezanina 2016-06-06 10:50:41 UTC 
Fix included in qemu-kvm-rhev-2.6.0-5.el7
Comment 8 Jon Masters 2016-06-16 01:21:02 UTC 
Um. Maybe not? I'm seeing the following whenever I try to create a new domain:

ERROR    unsupported configuration: the dmi-to-pci-bridge (i82801b11-bridge) controller is not supported in this QEMU binary
Comment 9 Jon Masters 2016-06-16 01:23:20 UTC 
[root@mustang ~]# virt-install --name rhelsa72_test1 --location "http://kickstart.bos.jonmasters.org/rhelsa/latest/Server/aarch64/os/" --vcpus=2 --memory 2048 --disk size=10 --network default --boot uefi

Starting install...
Retrieving file vmlinuz...                               |  11 MB     00:00 !!! 
Retrieving file initrd.img...                            |  61 MB     00:01 !!! 
Allocating 'rhelsa72_test1-2.qcow2'                      |  10 GB     00:00     
ERROR    unsupported configuration: the dmi-to-pci-bridge (i82801b11-bridge) controller is not supported in this QEMU binary
Domain installation does not appear to have been successful.
If it was, you can restart your domain by running:
  virsh --connect qemu:///system start rhelsa72_test1
otherwise, please restart your installation.
Comment 10 Jon Masters 2016-06-16 05:21:15 UTC 
You removed the arm-softmmu inclusion in the aarch64 default-config via a patch you're carrying in qemu-kvm-rhev, which means that i82801b11-bridge isn't included (but it is if you build upstream). I've got a scratch build going that re-adds it.
Comment 11 Jon Masters 2016-06-16 05:23:50 UTC 
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=11189510
Comment 12 Jon Masters 2016-06-16 05:40:27 UTC 
Created attachment 1168560 [details]
kvm-Add-i82801b11-bridge-device-for-AArch64.patch
Comment 13 Andrew Jones 2016-06-16 07:35:14 UTC 
(In reply to Jon Masters from comment #10)
> You removed the arm-softmmu inclusion in the aarch64 default-config via a
> patch you're carrying in qemu-kvm-rhev, which means that i82801b11-bridge
> isn't included (but it is if you build upstream). I've got a scratch build
> going that re-adds it.

We don't want it. We need to patch libvirt, not qemu.
Comment 14 Andrea Bolognani 2016-06-16 07:35:34 UTC 
The problem you're seeing is a known issue, caused by the
fact that libvirt insists on adding the dmi-to-pci-bridge
and pci-bridge to each and every mach-virt guest.

We're working on lifting that restriction[1]; after doing
so, everything will work without adding any more devices
to our QEMU configuration.


[1] https://www.redhat.com/archives/libvir-list/2016-June/msg01017.html
Note You need to log in before you can comment on or make changes to this bug.