chrismurphy added a new comment to an issue you are following: `` Fedora-Atomic-ostree-x86_64-25-20161207.0.iso in virt-manager set to use UEFI; and default automatic partitioning. program.log 12:04:03,606 INFO program: Running... efibootmgr 12:04:03,647 INFO program: EFI variables are not supported on this system. 12:04:03,648 DEBUG program: Return code: 2 12:04:03,648 INFO program: Running... efibootmgr -c -w -L Fedora -d /dev/vda -p 1 -l \EFI\fedora\shim.efi 12:04:03,658 INFO program: EFI variables are not supported on this system. 12:04:03,659 DEBUG program: Return code: 2 12:04:03,660 INFO program: Running... grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg 12:04:04,055 INFO program: /usr/bin/grub2-editenv: error: cannot rename the file /boot/grub2/grubenv.new to /boot/grub2/grubenv: No such file or directory. 12:04:04,056 INFO program: /sbin/grub2-mkconfig: line 247: /boot/efi/EFI/fedora/grub.cfg.new: No such file or directory 12:04:04,057 DEBUG program: Return code: 1 However, if I get to a vt and run efibootmgr there is no error. So I'm not sure why anaconda has a problem running it. The last two errors likewise don't make sense on their own, so to try and reproduce the problem I tried: # chroot /mnt/sysimage chroot: failed to run command '/bin/sh': No such file or directory Huh. So that usually works on netinstalls and lives. And /bin/sh does exist, it's a symlink to bash and /bin/bash does exist also. So I'm still confused. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/185 _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
