On 10/03/2016 02:57 PM, Dusty Mabe wrote:
On 10/03/2016 02:47 AM, Trishna Guha wrote:
> On Wed, Sep 28, 2016 at 9:26 PM, Kushal Das <mail(a)kushaldas.in> wrote:
>> Hi all,
>> The current F25 Atomic images are failing to boot, I never managed to reach
>> dracut emergency shell in my local box.
>> Can anyone else also please have a look?
>>  https://apps.fedoraproject.org/autocloud/jobs/704/output
> All the Fedora 25 Atomic images: qcow2, vagrant-libvirt,
> vagrant-virtualbox are failing to boot.
There is a kernel panic happening early in boot. Here is the serial
console log from one of those boots:
Interesting thing to note from the atomic host's kernel log:
[ 1.805434] x86/mm: Checked W+X mappings: passed, no W+X pages found.
Fatal: no entropy gathering module detected
[ 1.820475] traps: init general protection ip:7f544fd74652 sp:7fff58acd720 error:0
[ 1.823822] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Where the Fedora cloud base image (boots fine) has this:
[ 0.793666] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[ 0.799823] random: systemd: uninitialized urandom read (16 bytes read)
[ 0.800433] random: systemd: uninitialized urandom read (16 bytes read)
[ 0.800446] random: systemd: uninitialized urandom read (16 bytes read)
[ 0.811359] systemd: systemd 231 running in system mode. (+PAM +AUDIT +SELINUX +IMA
-APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP
+BLKID +ELFUTILS +KMOD +IDN)
Looks like there is some problem with generating/obtaining random data
on boot for Atomic Host.