Description of problem: As $subject says, these are very ugly and not upstreamable hacks which let us boot guests on OpenStack on aarch64 (ARM 64 bit). This bug is just to track the hacks and also discuss what can be done to turn them into something upstreamable. Version-Release number of selected component (if applicable): openstack-nova-2014.2.1-15.aa7a Additional information: At the moment I have added these hacks to rhos-6.0-rhel-7-aarch64 in dist-git.
Created attachment 988596 [details] 0001-Massive-hacks-to-get-things-working-on-aarch64-RHBZ-.patch
The attached patch doesn't change any code except the specfile ?!?!
Bugzilla is broken and is known to corrupt patches. Use this link: https://bugzilla.redhat.com/attachment.cgi?id=988596
Bugzilla PatchReader bug 554878.
Created attachment 993650 [details] 0001-HACK-nova-Workaround-for-libvirt-RHBZ-1184411.patch Updated patch 1/2.
Created attachment 993651 [details] 0002-HACK-nova-loader-element-for-AAVMF.patch Updated patch 2/2.
Setting to MODIFIED as there is a new build which includes these hacks: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=8754987
Setting back to ASSIGNED, since we could add support for virtio-scsi CDROMs. See Dan's comment: http://post-office.corp.redhat.com/archives/virt-arm/2015-March/msg00025.html in this thread: http://post-office.corp.redhat.com/archives/virt-arm/2015-March/thread.html#00012
NB, since we don't have to worry about backwards compatibility with legacy guests that only support virtio-blk, we could probably just make AArch64 default to virtio-scsi for both disks & cdrom, and thus ignore virtio-blk.
(In reply to Daniel Berrange from comment #11) > NB, since we don't have to worry about backwards compatibility with legacy > guests that only support virtio-blk, we could probably just make AArch64 > default to virtio-scsi for both disks & cdrom, and thus ignore virtio-blk. Note that virtio-scsi is buggy upstream on aarch64 (bug 1184405).
Are there still some hacks being tracked? Or does upstream work without them now, and this bug can be closed? Thanks, drew
Upstream is supposed to support it out of the box now, although I've not tested that in a while. In any case it's sufficient that we have this bug with the old patches attached in case we need to refer to them, but it can be closed.