[13.4-stable] pillar: Fix OVMF binary file for ARM64 #4339
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of PR: #4327
Commit e23b37f separated OVMF firmware files and standardized names. However, these changes were available only for x86_64. On arm64 we keep using the ovmf.bin binary (with the firmware code + variables), leading to the following error:
qemu-system-aarch64: Could not find ROM image '/usr/lib/xen/boot/OVMF_CODE.fd'
This commit fixes this issue by using the ovmf.bin only for arm64.