Summary: | sys-kernel/gentoo-sources-4.19.82: libvirt-guests are stuck in reboot-loop | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tastytea <gentoo> |
Component: | Current packages | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | fabian, jasmin+gentoo, randy |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | https://lkml.org/lkml/2019/11/11/194 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 700416 | ||
Bug Blocks: | |||
Attachments: |
libvirt log of guest
dmesg excerpt |
Description
tastytea
2019-11-10 16:24:16 UTC
Created attachment 595666 [details]
libvirt log of guest
Created attachment 595668 [details]
dmesg excerpt
I recompiled the kernel with sys-devel/gcc-8.3.0-r1 to be sure it's not that; the issue persists. Same issue after upgrading from linux-4.14.143-gentoo to linux-4.14.152-gentoo on the VM host. After reboot host works fine, but guests with linux-4.14.143-gentoo are stuck in a bootloop. All kernels compiled with sys-devel/gcc-8.3.0-r1 Are you able to do a git bisect between the last working kernel and the first on working kernel? http://www.reactivated.net/weblog/archives/2006/01/using-git-bisect-to-find-buggy-kernel-patches/ Yes, I'll get right to work. :-) 496cf984a60edb5534118a596613cc9971e406e8 is the first bad commit (commit 16cfacc8085782dab8e365979356ce1ca87fd6cc upstream). https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=496cf984a60edb5534118a596613cc9971e406e8 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=16cfacc8085782dab8e365979356ce1ca87fd6cc Upstream patch: bf03d4f9334728bf7c8ffc7de787df48abd6340e Will be in next stable kernels. I can confirm the fix works with 4.19.82. |