Manual filing of a tb as libreport is broken at present. Will attach all log files.
I was attempting to install F19 Alpha TC2 desktop live to a freshly-created UEFI-based VM, created following Cole's instructions here:
install gets all the way to bootloader installation, then crashes. The target disk would have been entirely empty. I first tried to select custom partitioning (and got dumped back to hub, as is a known bug), then went back through disk selection and picked automatic partitioning.
anaconda 19.13 exception report
Traceback (most recent call first):
File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1666,
raise BootLoaderError("failed to set new efi boot target")
File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1671, in install
File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1690, in write
File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2246, in writeBootLoader
File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 143, in doInstall
writeBootLoader(storage, payload, instClass, ksdata)
File "/usr/lib64/python2.7/threading.py", line 504, in run
File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 141, in run
threading.Thread.run(self, *args, **kwargs)
BootLoaderError: failed to set new efi boot target
Created attachment 717869 [details]
Created attachment 717870 [details]
Created attachment 717871 [details]
Created attachment 717872 [details]
Created attachment 717873 [details]
Created attachment 717874 [details]
Created attachment 717875 [details]
Proposing as an Alpha blocker:
"When using the dedicated installer images, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces."
"This criterion covers showstopper bugs in the installer for which there isn't any other specific criterion: obviously, it can't 'complete an installation' if there's a showstopper."
I just checked that F18 final desktop live installs fine in the same VM config, so this isn't just some kind of bug in the UEFI VM.
18:02:14,568 INFO program: Running... efibootmgr -c -w -L Fedora -d /dev/vda -p 1 -l \EFI\fedora\shim.efi
18:02:14,613 INFO program: Fatal: Couldn't open either sysfs or procfs directories for accessing EFI variables.
18:02:14,614 INFO program: Try 'modprobe efivars' as root.
18:02:14,615 DEBUG program: Return code: 1
could this be related to the bug about missing directories in the install root? https://bugzilla.redhat.com/show_bug.cgi?id=922988
Discussed at 2013-04-03 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-04-03/f19alpha-blocker-review-4.2013-04-03-16.01.log.txt . Accepted as a blocker per criterion "When using the dedicated installer images, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces." in the case of a UEFI install.
This seems to be fixed in TC5, the efibootmgr command succeeds. The created EFI boot manager entry never actually seems to be used, but I suspect that's a flaw in the UEFI firmware itself, I'll have to talk to the virt folks about it. I'll confirm on bare metal, but I'm going to mark this as CLOSED for now.