Bug 1325979 - Fedora 23 Base Cloud image fails to boot on OpenStack
Summary: Fedora 23 Base Cloud image fails to boot on OpenStack
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-11 14:04 UTC by Akos Ladanyi
Modified: 2016-12-14 00:32 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-10-26 16:46:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Console log (23.40 KB, text/plain)
2016-04-11 14:04 UTC, Akos Ladanyi
no flags Details

Description Akos Ladanyi 2016-04-11 14:04:08 UTC
Created attachment 1146005 [details]
Console log

1. Downloaded Fedora-Cloud-Base-23-20151030.x86_64.qcow2.
2. Booted it using qemu-kvm. It worked fine.
3. I ran "dnf upgrade", rebooted and it still worked fine.
4. After that I uploaded the resulting image to an OpenStack cloud and I tried to create an instance based on it. The instance failed to boot. I attached the console log.

Comment 1 Josh Boyer 2016-04-11 14:07:52 UTC
Looks like whatever your VM software is (VMWare?) is advertising instructions that it doesn't actually implement, and the kernel gets an invalid opcode error when it tries to execute them.

Comment 2 Bogdan A 2016-04-12 07:18:43 UTC
Can you pinpoint the exact instructions?(In reply to Josh Boyer from comment #1)
> Looks like whatever your VM software is (VMWare?) is advertising
> instructions that it doesn't actually implement, and the kernel gets an
> invalid opcode error when it tries to execute them.

Comment 3 Josh Boyer 2016-04-12 11:22:37 UTC
(In reply to Bogdan A from comment #2)
> Can you pinpoint the exact instructions?

Not at the moment, but given where the kernel crashes it likely has to do with AVX instructions:

[    1.147136] AVX version of gcm_enc/dec engaged.
[    1.151831] AES CTR mode by8 optimization enabled
[    1.166980] invalid opcode: 0000 [#1] SMP 
[    1.167023] Modules linked in:
[    1.167023] CPU: 0 PID: 108 Comm: cryptomgr_test Not tainted 4.4.6-301.fc23.x86_64 #1
[    1.167023] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.7.5-20150310_111955-batsu 04/01/2014
[    1.167023] task: ffff88003a9c5640 ti: ffff88003ab88000 task.ti: ffff88003ab88000
[    1.167023] RIP: 0010:[<ffffffff810934aa>]  [<ffffffff810934aa>] aes_ctr_enc_128_avx_by8+0xa/0x1250
[    1.167023] RSP: 0018:ffff88003ab8b8c8  EFLAGS: 00010206
[    1.167023] RAX: 0000000000000010 RBX: 0000000000000000 RCX: ffff88003ab3a000
[    1.167023] RDX: ffff88003ab17050 RSI: ffff88003ab8bd70 RDI: ffff88003ab3a000
[    1.167023] RBP: ffff88003ab8b8d0 R08: 0000000000000040 R09: ffff88003ab3a000
[    1.167023] R10: ffff88003ab3a000 R11: 0000000000000000 R12: ffff88003ab17050
[    1.167023] R13: ffff88003ab8b9d0 R14: ffff88003ab8bd70 R15: ffff88003ab3a000
[    1.167023] FS:  0000000000000000(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000
[    1.167023] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    1.167023] CR2: 00007f9ae7348944 CR3: 0000000001c09000 CR4: 00000000001006f0
[    1.167023] Stack:
[    1.167023]  ffffffff8107d181 ffff88003ab8b9c0 ffffffff8107ca49 00000000f1110fd0
[    1.167023]  0000000000000000 ffffea0000eace80 ffff88003ab3a000 ffffea0000eace80
[    1.167023]  ffff88003ab3a000 ffff88003ab8bb70 0000000000000000 ffff880000000040
[    1.167023] Call Trace:
[    1.167023]  [<ffffffff8107d181>] ? aesni_ctr_enc_avx_tfm+0x41/0x50
[    1.167023]  [<ffffffff8107ca49>] ctr_crypt+0x99/0x1e0
[    1.167023]  [<ffffffff8137d842>] __ablk_encrypt+0x52/0x70
[    1.167023]  [<ffffffff8137d884>] ablk_encrypt+0x24/0xa0
[    1.167023]  [<ffffffff8135ec9e>] skcipher_encrypt_ablkcipher+0x5e/0x60
[    1.167023]  [<ffffffff81363a97>] __test_skcipher+0x297/0xc50
[    1.167023]  [<ffffffff810cdda0>] ? wake_up_q+0x70/0x70
[    1.167023]  [<ffffffff8136dcc7>] ? cryptd_blkcipher_init_tfm+0x27/0x40

Comment 4 Laura Abbott 2016-09-23 19:29:06 UTC
*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs.
 
Fedora 23 has now been rebased to 4.7.4-100.fc23.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25.
 
If you experience different issues, please open a new bug report for those.

Comment 5 Laura Abbott 2016-10-26 16:46:10 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 6 Akos Ladanyi 2016-12-14 00:32:33 UTC
No longer relevant.


Note You need to log in before you can comment on or make changes to this bug.