Bug 1445998 - Traceback on VM boot under QEMU/KVM
Summary: Traceback on VM boot under QEMU/KVM
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 26
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-27 00:09 UTC by Robbie Harwood
Modified: 2018-02-28 18:42 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-28 18:42:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robbie Harwood 2017-04-27 00:09:46 UTC
With kernel-core-4.11.0-0.rc7.git3.1.fc27.x86_64, I get this traceback which halts boot:

https://rharwood.fedorapeople.org/screenshots/2017-04-24-153656_3840x1080_scrot.png

This behavior doesn't occur with 4.11.0-0.rc6.git3.1.fc27.x86_64.

(The screenshot is from the fc26 versions, which exhibit the same behavior.

Comment 1 Laura Abbott 2017-04-27 01:06:15 UTC
Can you test with -rc8? Someone on IRC reported similar behavior on -rc7 and reported it was fixed on -rc8.

Comment 2 Robbie Harwood 2017-04-27 02:32:58 UTC
Sure thing.

4.11.0-0.rc8.git2.1.fc27.x86_64 is good, as is 4.11.0-0.rc8.git0.1.fc26.x86_64.  (I've also given karma on the bodhi.)

Thanks!

Comment 3 Adam Williamson 2017-04-28 00:19:46 UTC
Saw something similar in openQA testing of virtio-scsi disks when RC7 landed in Fedora 26. Testing with a couple of custom-built images confirms this was caused by RC7 and seems to be resolved in RC8.

Comment 4 Fedora Update System 2017-04-28 00:29:28 UTC
kernel-4.11.0-0.rc8.git0.1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-847f5e68b1

Comment 5 Fedora Update System 2017-04-28 14:36:09 UTC
kernel-4.11.0-0.rc8.git0.1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

Comment 6 Laura Abbott 2018-02-28 03:36:48 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs.
 
Fedora 26 has now been rebased to 4.15.4-200.fc26.  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 27, and are still experiencing this issue, please change the version to Fedora 27.
 
If you experience different issues, please open a new bug report for those.

Comment 7 Robbie Harwood 2018-02-28 18:42:24 UTC
(I think this bug was supposed to have been closed per comment#5.)


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