Atomic Working Group (ARCHIVED) August 2017

atomic@lists.fedoraproject.org

7 participants
83 discussions

[atomic-wg] Issue #299: Concerns related to enabling Atomic Host CloudImages compose in Rawhide for multi-arches
by Dusty Mabe 02 Aug '17

02 Aug '17

dustymabe added a new comment to an issue you are following: `` > Update: > I have succeeded in creating FAH CloudImage on aarch64 using imagefactory on local machine. Image gets generated successfully when we use reqpart in fedora-atomic kickstart file. > There are two issues while booting generated cloudImage on aarch64: > 1. "can't find command linuxefi, can't find command initrdefi" . Modifying kernel boot parameter from linuxefi to linux and initrdefi to initrd fixes this problem. This problem has been fixed here https://github.com/ostreedev/ostree/pull/1021 . sweet - are we testing this with rawhide or f26? > 2. After changes made as stated in 1st issue, booting gets stuck with following messages: > EFI stub: Booting Linux Kernel... > EFI stub: Using DTB from configuration table > EFI stub: Exiting boot services and installing virtual address map... > It seems to be a problem with console option passed in fedora-atomic kickstart file at https://pagure.io/fedora-kickstarts/blob/master/f/fedora-atomic.ks#_20 . It seems, arm devices uses console=ttyAMA0. Either adding console=ttyAMA0 in line#20 or removing console=tty1 console=ttyS0,115200n8 fixes the problem. I wish i would have known you were debugging this :) - I hit this same problem a few months ago: https://twitter.com/dustymabe/status/867225301985755137. I guess we need to find a way to specify that to just the aarch64 images. > With above two problem fixed, aarch64 image boots successfully. :tada: have we tried with any other architectures? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/299

1 0

[atomic-wg] Issue #299: Concerns related to enabling Atomic Host CloudImages compose in Rawhide for multi-arches
by Sinny Kumari 02 Aug '17

02 Aug '17

sinnykumari added a new comment to an issue you are following: `` Update: I have succeeded in creating FAH CloudImage on aarch64 using imagefactory on local machine. Image gets generated successfully when we use reqpart in fedora-atomic kickstart file. There are two issues while booting generated cloudImage on aarch64: 1. "can't find command linuxefi, can't find command initrdefi" . Modifying kernel boot parameter from linuxefi to linux and initrdefi to initrd fixes this problem. This problem has been fixed here https://github.com/ostreedev/ostree/pull/1021 . 2. After changes made as stated in 1st issue, booting gets stuck with following messages: EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... It seems to be a problem with console option passed in fedora-atomic kickstart file at https://pagure.io/fedora-kickstarts/blob/master/f/fedora-atomic.ks#_20 . It seems, arm devices uses console=ttyAMA0. Either adding console=ttyAMA0 in line#20 or removing console=tty1 console=ttyS0,115200n8 fixes the problem. With above two problem fixed, aarch64 image boots successfully. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/299

1 0

[Fedocal] Reminder meeting : Atomic Working Group Weekly Meeting
by dusty＠dustymabe.com 01 Aug '17

01 Aug '17

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2017-08-02 from 17:00:00 to 18:00:00 UTC At fedora-meeting-1@freenode The meeting will be about: This is the meeting for the Fedora Atomic Working Group. We typically go over previous meeting action items and then cover all tickets with the meeting keyword: https://pagure.io/atomic-wg/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/Atomic_WG#Meetings](https://fedoraproject.or… Source: https://apps.fedoraproject.org/calendar/meeting/6370/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) August 2017