Description of problem: I was installing rawhide in VM today (virt-install --connect qemu:///system --name rawhide-uefi --boot uefi --disk size=20 --memory 1024 --cdrom Fedora-Server-netinst-x86_64-Rawhide-20170708.n.0.iso), and it stops as in $subject. It's not frozen — anaconda reacts to user input, I can go the the "create user" pane, and I can switch to the text terminal. It just doesn't seem to be doing anything in particular. Version-Release number of selected component (if applicable): Server-netinst-x86_64-Rawhide-20170708.n.0.iso How reproducible: don't know yet
Created attachment 1295619 [details] anaconda.log
Created attachment 1295620 [details] program.log
Created attachment 1295621 [details] storage.log
Created attachment 1295622 [details] /tmp/syslog
Hi Zbigniew, Please verify if it is reproducible for you. We are having similar issue in our tests, which are using virt-install heavily. For us it is not reproducible; it happens approximately 1 from 5 installations. Thank you for reporting this.
I tried a second time (this time with --memory 1024) and it worked without issue. I'll try to find time to make a few more tries later.
> I tried a second time (this time with --memory 1024) That was supposed to be 2048. I tried a few more times with --memory 1024 and it seems to work OK every time.
IMHO, it looks like you have encountered the same issue as we have. It happens even more when there is heavy parallel usage of virt-install.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
FTR I'm also hitting this during the installation of Fedora 30.