dustymabe added a new comment to an issue you are following:
``
Closing this as the fix is in and will be in the next two week release.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
___
cloud
jberkus added a new comment to an issue you are following:
``
@dustymabe I tested this on one of the minnowboards, and it installed and
booted fine.
Note that, instead of allocating specific bytes for /boot, you can use this KS
command:
reqpart --add-boot
``
To reply, visit the link below or
dustymabe added a new comment to an issue you are following:
``
> VM install of Fedora-Atomic-ostree-x86_64-25-20170118.1.iso to a clean LV
> succeeds, for both BIOS and UEFI firmware. Using default partitioning, the
> required layout is created. Both installations completely startup, I can
>
chrismurphy added a new comment to an issue you are following:
``
VM install of Fedora-Atomic-ostree-x86_64-25-20170118.1.iso to a clean LV
succeeds, for both BIOS and UEFI firmware. Using default partitioning, the
required layout is created. Both installations completely startup, I can login,
dustymabe added a new comment to an issue you are following:
``
First build is out that contains this fix. Please test:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170118.1/compose/Atomic/x86_64/iso/
Keep in mind you will need to have a /boot partition in order for this
dustymabe added a new comment to an issue you are following:
``
[here](https://pagure.io/pungi/issue/508) is a pungi rfe that will enable us to
get the anaconda update in once it is fixed:
@lsedlar is going to work on it tomorrow.
``
To reply, visit the link below or just reply to this email
dustymabe added a new comment to an issue you are following:
``
>>
>> We were also affected by this issue and spent a huge amount of time figuring
>> out why the installation fails. Are there any updates from releng?
>
> hi @nightvisi0n - due to the recent holidays we didn't have much time to
dustymabe added a new comment to an issue you are following:
``
> Yeah, merged /boot with ostree doesn't quite work for us yet. See
> https://github.com/ostreedev/ostree/pull/215
hmm. and that is only an issue on UEFI because I've been doing legacy boot
without a /boot partition for a while
walters added a new comment to an issue you are following:
``
Yeah, merged /boot with ostree doesn't quite work for us yet. See
https://github.com/ostreedev/ostree/pull/215
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
dustymabe added a new comment to an issue you are following:
``
I'll note that if I give myself a boot partition (i.e. a filesystem mounted at
`/boot`) then things work ok:
```text
# Partition info
zerombr
clearpart --all
reqpart
part pv.01 --grow
volgroup atomicos pv.01
logvol / --size=3000
dustymabe added a new comment to an issue you are following:
``
Hey @walters I created an
[updates.img](https://dustymabe.fedorapeople.org/fixuefi-updates.img) with your
change in it and I'm seeing an issue where the install succeeds but the
grub.cfg in the efi partition seems to have the
dustymabe added a new comment to an issue you are following:
``
> We were also affected by this issue and spent a huge amount of time figuring
> out why the installation fails. Are there any updates from releng?
hi @nightvisi0n - due to the recent holidays we didn't have much time to work
sedrubal added a new comment to an issue you are following:
``
You can also reproduce this issue by installing fedora atomic in qemu+kvm using
UEFI BIOS (edk2-ovmf) ;)
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
dustymabe added a new comment to an issue you are following:
``
A new version of anaconda made it to
[stable](https://bodhi.fedoraproject.org/updates/FEDORA-2016-69bb5a1d7c). It
has also been [tagged](https://pagure.io/releng/issue/6568) such that the next
isos that are generated should have
walters added a new comment to an issue you are following:
``
Anaconda PR with updates.img available:
https://github.com/rhinstaller/anaconda/pull/903
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
dustymabe added a new comment to an issue you are following:
``
FYI walters has opened this upstream issue for this problem:
https://github.com/rhinstaller/anaconda/issues/900
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
dustymabe added a new comment to an issue you are following:
``
@kushal - can you make sure we have a test for this in the future once this
gets fixed. You can use UEFI in KVM/QEMU with `--boot uefi` parameter.
``
To reply, visit the link below or just reply to this email
The issue: `November 21 ISO is not bootable` of project: `atomic-wg` has been
assigned to `walters` by dustymabe.
https://pagure.io/atomic-wg/issue/185
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to
walters added a new comment to an issue you are following:
``
I'll take this issue.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
___
cloud mailing list -- cloud@lists.fedoraproject.org
To
dustymabe added a new comment to an issue you are following:
``
> 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.
in this environment bin is a symlink and that symlink isn't set up at
chrismurphy added a new comment to an issue you are following:
``
[](/atomic-wg/issue/raw/files/cb8148271c4c88af8e1abebf3d2b725e0f44eaa2ffc65b837c6424c061eb4755-program.log)
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
jberkus added a new comment to an issue you are following:
``
Report from the field:
```
Last night, I'm try to install Fedora 25 atomic host on UEFI notebook.
But all the time installation finished with error fail to install bootloader.
As I see after this message /mnt/sysimage have no grub
On 12/08/2016 02:20 PM, Chris Murphy wrote:
> Using virt-manager set to use UEFI
>
> 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
Using virt-manager set to use UEFI
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
jberkus added a new comment to an issue you are following:
``
Per atomic-devel list, ISOs are in fact broken for UEFI.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
___
cloud mailing list --
jberkus added a new comment to an issue you are following:
``
Hmmm. Didn't have issues with 24. Let me retest now that 12/7 is available.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
___
cloud
walters added a new comment to an issue you are following:
``
This might be UEFI vs bios - if you're using default virt-manager you get BIOS.
Some more info here https://fedoraproject.org/wiki/Using_UEFI_with_QEMU
``
To reply, visit the link below or just reply to this email
kushal added a new comment to an issue you are following:
``
It also passed the Automated tests in OpenQA
https://openqa.fedoraproject.org/tests/overview?distri=fedora=Atomic=Fedora-Atomic-25-20161121.0=1
``
To reply, visit the link below or just reply to this email
dustymabe added a new comment to an issue you are following:
``
thanks @miabbott, I also just tried out the latest ISO and it works for me.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
___
cloud
miabbott added a new comment to an issue you are following:
``
I downloaded the Nov 21 ISO from here:
https://dl.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-20161121.0/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20161121.0.iso
...and wrote it to a USB key. Then successfully
jberkus added a new comment to an issue you are following:
``
Aside from the problem with installing, this raises the question of whether
anyone other than me is testing ISOs on bare metal at all. Queued for meeting
because of this.
``
To reply, visit the link below or just reply to this
jberkus reported a new issue against the project: `atomic-wg` that you are
following:
``
I'm currently testing the November 21 ISOs by installing on my minnowboard
cluster. It seems to be the case that these ISOs are not bootable; after
getting through most of the install, they give the
33 matches
Mail list logo
