Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1548906

Summary:	Fedora 26, with Xen hypervisor dont boot with kernel 4.15.4-200
Product:	[Fedora] Fedora	Reporter:	Trever <sdmau63ndf>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	26	CC:	airlied, ajax, alekcejk, bskeggs, ewk, extras-qa, hdegoede, h.reindl, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, labbott, linville, m.a.young, mchehab, mjg59, steved
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1544963	Environment:
Last Closed:	2018-02-26 22:25:36 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 Trever 2018-02-26 00:50:38 UTC

+++ This bug was initially created as a clone of Bug #1544963 +++
Same upstream bug seems to apply to F26.

Description of problem:
'Fedora, with Xen hypervisor' dont boot with kernel 4.15.4-200

Version-Release number of selected component (if applicable):
kernel-4.15.4-200.fc26.x86_64

Steps to Reproduce:
Boot Fedora with Xen hypervisor with kernel 4.15.4-200

Actual results:
Kernel does not start and vm terminates, with no kernel messages.

Additional info:
Encountered on Qubes OS 3.2, which uses Xen hypervisor.
kernel 4.15.3-200 also fails.
kernel 4.14.18-200 boots fine.

Comment 1 Laura Abbott 2018-02-26 22:25:36 UTC

There's no need to create a separate bug for F26. F26 and F27 get the same kernel updates so having a separate bug only creates more work for us.

*** This bug has been marked as a duplicate of bug 1544963 ***