Bug 545851
| Summary: | KVM/networking-related crash? | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Huffman <bloch> | ||||||
| Component: | kernel | Assignee: | Justin M. Forbes <jforbes> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 12 | CC: | cyberrider, dougsland, gansalmon, itamar, jcm, jforbes, kernel-maint, ondrejj, ruben | ||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-02-02 17:31:44 UTC | Type: | --- | ||||||
| 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: | 546327 | ||||||||
| Attachments: |
|
||||||||
|
Description
Adam Huffman
2009-12-09 14:01:32 UTC
Created attachment 378558 [details] kernel oops http://www.redhat.com/archives/fedora-virt/2009-December/msg00041.html I am seeing a kernel oops and panic on a host running 2.6.31.6-166.fc12.x86_64 (and also at least 2.6.31.6-145) when I autostart a f12-x86_64 qemu-kvm guest. I'm running on a quad core AMD with: qemu-kvm-0.11.0-12.fc12.x86_64 kernel-2.6.31.6-166.fc12.x86_64 libvirt-0.7.1-15.fc12.x86_64 If I flag a guest as autoboot and reboot the host then the host starts, the guest starts, and some seconds later (presumably when the guest is fully up or just before) the host OOPs and hangs. The full error log is attached, it begins as: BUG: unable to handle kernel paging request at 0000000000200200 IP: [<ffffffff8139aad7>] destroy_conntrack+0x82/0x11f Thanks for the report. In my case, it seems to be related to IPv6. If I switch off the ip6tables service and ensure the relevant modules aren't loaded, the system seems stable. Same problem for me. For me it's enough to disable ip6tables for bridge by adding: net.bridge.bridge-nf-call-ip6tables = 0 to /etc/sysctl.conf No need to remove ip6tables firewall completelly. That rule alone do not fix it for me, and they are set by default it would seem on this box. I can reproduce this 100% reliably with recent F12 kernels and upstream 2.6.32 and 2.6.33-rc5. Do the crashes happen if you blacklist the ipv6/ip6tables modules as well? People, you may want to check out https://bugzilla.redhat.com/show_bug.cgi?id=533087 too, as there is similar and potentially relevant information there. I spent the whole weekend learning the netfilter code and SLUB debugging to find this problem: http://lkml.org/lkml/2010/2/2/272 There should be a patch soon. *** This bug has been marked as a duplicate of bug 533087 *** |