Bug 1294094

Summary:	Vagrant Cloud fails to boot on CentOS 7 standard libvirt+kvm environment
Product:	[Fedora] Fedora	Reporter:	Julius Schwartzenberg <julius.schwartzenberg>
Component:	fedora-productimg-atomic	Assignee:	Colin Walters <walters>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	23	CC:	adimania, dustymabe, dwalsh, lsm5, walters
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-20 17:22:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Julius Schwartzenberg 2015-12-24 16:17:39 UTC

Description of problem:
When using the official Fedora 23 cloud image from:
https://getfedora.org/en/cloud/download/
Booting up the VM fails as the kernel panics with a call trace.

I would expect CentOS/RHEL to be a primary testing environment for the Fedora cloud images. It's surprising it's failing now. Other OSses work without issues.
The Fedora 22 cloud image also does *not* have this problem.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install RHEL/CentOS 7 with libvirt+kvm
2. Install Vagrant
3. Load the Fedora 23 cloud image in it

Actual results:
Fedora 23 crashes at start-up.

Expected results:
A working Fedora 23 VM.

Additional info:

Comment 1 Julius Schwartzenberg 2016-05-03 14:29:47 UTC

I found a workaround. Add this to the Vagrantfile to prevent the kernel panic:

  config.vm.provider "libvirt" do |libvirt|
    libvirt.cpu_feature :name => 'avx', :policy => 'disable'
  end

Comment 2 Fedora End Of Life 2016-11-24 14:30:31 UTC

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2016-12-20 17:22:25 UTC

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.