Description of problem: Running F36 on an aarch64 machine that also has aarch32, using virt-manager to create a new VM with the public fedora 36/armhfp disk image virt-manager throws the following error when the "finish" button is clicked. Unable to complete install: 'unsupported configuration: TPM model 'tpm-tis' is only available for x86 and aarch64 guests' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createvm.py", line 2008, in _do_async_install installer.start_install(guest, meter=meter) File "/usr/share/virt-manager/virtinst/install/installer.py", line 695, in start_install domain = self._create_guest( File "/usr/share/virt-manager/virtinst/install/installer.py", line 637, in _create_guest domain = self.conn.createXML(initial_xml or final_xml, 0) File "/usr/lib64/python3.10/site-packages/libvirt.py", line 4400, in createXML raise libvirtError('virDomainCreateXML() failed') libvirt.libvirtError: unsupported configuration: TPM model 'tpm-tis' is only available for x86 and aarch64 guests Version-Release number of selected component (if applicable): 36 How reproducible: 100% Steps to Reproduce: 1. On a aarch64 host, running f36 2. Download Fedora-Server-36-20220424.n.0.armhfp.raw.xz, decompress it 3. start virt-manager, click "Create new virtual machine" 4. "import existing disk image" (or Local media install) 5. Virt type KVM/arm/virt 6. next->select disk image 7. next->next->finish. Actual results: Fails to create machine with error about tpm. Expected results: Creates machine and starts booting it. Additional info:
Thanks for the report, should be fixed upstream now: commit 48f66f27fd8ca4694b2dd9f17602db857a924083 (HEAD -> main, origin/main, origin/HEAD, work) Author: Cole Robinson <crobinso> Date: Fri Jun 17 13:04:05 2022 -0400 domcaps: armv7l doesn't support tpm-tis
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.