Bug 1967602

Summary: There is no qemu-kvm on aarch64
Product: [Fedora] Fedora Reporter: Gerd Hoffmann <kraxel>
Component: kata-containersAssignee: Eduardo Lima (Etrunko) <elima>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 34CC: dinechin, elima
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: kata-containers-2.1.0-2.fc34 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-06-07 15:19:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gerd Hoffmann 2021-06-03 13:04:23 UTC
Description of problem:
There is no qemu-kvm on aarch64, the default configuration doesn't work because of that.  qemu-system-aarch64 should be used instead.

Comment 1 Christophe de Dinechin 2021-06-04 15:35:17 UTC
Proposed fix https://src.fedoraproject.org/rpms/kata-containers/pull-request/2.

Comment 2 Fedora Update System 2021-06-07 12:20:41 UTC
FEDORA-2021-9206a7e7ae has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-9206a7e7ae

Comment 3 Eduardo Lima (Etrunko) 2021-06-07 15:19:30 UTC
Fixed in rawhide and 34.

Comment 4 Fedora Update System 2021-06-09 01:16:16 UTC
FEDORA-2021-9206a7e7ae has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-9206a7e7ae`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-9206a7e7ae

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2021-06-16 20:46:07 UTC
FEDORA-2021-9206a7e7ae has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.