Bug 1434462
| Summary: | frequent kernel panic during VM boot | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||||||||||||||
| 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: | awilliam, cz172638, dustymabe, gansalmon, ichavero, itamar, jkurik, jonathan, jsedlak, kernel-maint, madhu.chinakonda, mchehab, mruckman, rjones, robatino, sgallagh, sumukher | ||||||||||||||||
| 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: | Environment: | ||||||||||||||||||
| Last Closed: | 2017-03-23 21:14:46 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: | |||||||||||||||||||
| Bug Depends On: | |||||||||||||||||||
| Bug Blocks: | 1349184 | ||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
|
Description
Kamil Páral
2017-03-21 14:41:08 UTC
Created attachment 1265097 [details]
vm.xml
Created attachment 1265098 [details]
rpm-qa
Created attachment 1265099 [details]
panic1.txt
Created attachment 1265100 [details]
panic2.txt
Created attachment 1265101 [details]
panic3.txt
Proposing as an alpha blocker under: " A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility. " https://fedoraproject.org/wiki/Fedora_26_Alpha_Release_Criteria#Expected_installed_system_boot_behavior Provided that other people can replicate my issues and it's not just me affected by this. Also please note this might be actually a duplicate of bug 1433899. I forgot to add, my host system is F25: kernel-4.10.4-200.fc25.x86_64 libvirt-2.2.0-2.fc25.x86_64 virt-manager-1.4.1-1.fc25.noarch qemu-system-x86-2.7.1-4.fc25.x86_64 The above was an updated VM from updates-testing. But after some attempts I reproduced the panic even with completely clean Workstation Live Alpha RC1.1 installation (no updates). It happened to me also - kernel panic right at the start of the boot. The third traceback in comment 0 seems to be the same as in bug 1430297. I can also confirm this with WS Live Alpha RC1.2. I booted four times, first time with disk check which succeeded, second time without disk-check led to a kernel panic, third time without a disk-check led to a kernel panic, fourth time without disk-check succeeded. I cannot reproduce this on an *installed* VM of Workstation. I can only get it to panic when booting the Live media. I've been rebooting the installed OS repeatedly for a while now (at least ten boots) and I haven't encountered the panic. I did hit the three-minute timeout that Kamil mentioned twice, but it finished booting. (In reply to Stephen Gallagher from comment #12) > I did hit the three-minute timeout that Kamil mentioned twice, > but it finished booting. Check the logs, I can usually see a kernel panic shortly before this happens, the system just seems to recover in this case (but I saw poweroff hanging when this happened). Note that we have explicit virt criteria, and they're *Beta* criteria: https://fedoraproject.org/wiki/Fedora_26_Beta_Release_Criteria#Virtualization_requirements "The release must be able host virtual guest instances of the same release." is the relevant one here. This has always been held to mean that virt-only bugs can't block Alpha. It is, admittedly, a longstanding situation and came about when use of virtualization was somewhat less common than it is now, but it's how things are at present. On that basis I'm -1 Alpha blocker here, unless we adjust the criteria. I just tested with RC1.2 on Bare metal and it all worked fine. I concur with Adam. -1 Alpha blocker. FWIW I have (only once) seen the copy_process.part / _do_fork traceback, with the latest upstream kernel from git (093b995e3b55a) when booting the kernel virtualized under qemu-2.8.0-2.fc26. A good way to see these issues is to run the following command (all one line). Run it as a normal non-root user: rm -rf /var/tmp/.guestfs-*; while LIBGUESTFS_BACKEND=direct libguestfs-test-tool -t 120 >& /tmp/log ; do echo -n . ; done Then examine the log file containing the failure: cat /tmp/log Tested on Alpha RC 1.2 on bare metal and Virtual Machine Manager couldn't reproduce Kernel Panic. (In reply to Richard W.M. Jones from comment #17) > rm -rf /var/tmp/.guestfs-*; while LIBGUESTFS_BACKEND=direct > libguestfs-test-tool -t 120 >& /tmp/log ; do echo -n . ; done I couldn't reproduce the issue on my F25 host (I assume that's because the test tool boots the same version of OS as the host system is), but Petr Schindler reproduced it on the very first run on his F26 host. Great reproducer, thanks. (In reply to Kamil Páral from comment #19) > (In reply to Richard W.M. Jones from comment #17) > > rm -rf /var/tmp/.guestfs-*; while LIBGUESTFS_BACKEND=direct > > libguestfs-test-tool -t 120 >& /tmp/log ; do echo -n . ; done > > I couldn't reproduce the issue on my F25 host (I assume that's because the > test tool boots the same version of OS as the host system is), but Petr > Schindler reproduced it on the very first run on his F26 host. Great > reproducer, thanks. It tests the highest numbered installed kernel (not necessarily the running kernel). This issue does not affect F25 kernels at all (or any kernel < 4.11) so you would not expect to see it in F25 unless you had installed an F26 kernel using dnf update kernel --releasever=26 --best I concur with Adam and Mike here. If we can not reproduce it on bare metal, I am -1 to block Alpha on this. Created attachment 1265870 [details]
dusty-panic1.txt
I've seen a lot of traces from VMs. here are a few.
Created attachment 1265871 [details]
dusty-panic2.txt
Another one
As 1430297 is the earliest report, and we're fairly sure these are all the same problem, marking as a dupe of that. A kernel build with a potential fix is currently running, we will ask all affected people to test with that build once it's done. We can un-dupe reports later if there turn out to be separate bugs. *** This bug has been marked as a duplicate of bug 1430297 *** |