[fedora-virt] libvirtd crashes host when autostarting

[Ján ONDREJ (SAL)]

On Wed, Jan 06, 2010 at 10:23:16AM +0000, Adam Huffman wrote:
> On Tue, Dec 15, 2009 at 3:04 PM, Adam Huffman <adam.huffman at gmail.com> wrote:
> > On Mon, Dec 14, 2009 at 2:04 AM, Dale Bewley <dlbewley at lib.ucdavis.edu> wrote:
> >> On Fri, 2009-10-09 at 10:39 -0400, Rich Mahn wrote:
> >>> > On Fri, 2009-10-09 at 09:45 -0400, Rich Mahn wrote:
> >>> > > Summary:
> >>> > >    My host crashes when I use the autostart function in
> >>> > > libvirtd.
> >>> > >
> >>> > > This command sequence works fine:
> >>> > >
> >>> > > service libvirtd stop
> >>> > > virsh autostart mydomain --disable
> >>> > > service lib virtd start
> >>> > > virsh start mydomain
> >>> > >
> >>> > > This command sequence will crash the host:
> >>> > >
> >>> > > service libvirtd stop
> >>> > > virsh autostart mydomain
> >>> > > service libvirtd start
> >>> > >
> >>> > >
> >>> > > I can't find any error messages related to this.  The host system
> >>> > > freezes, the keyboard starts blinking the caps-lock and scroll-lock,
> >>> > > and as best I can tell, the kernel has stopped running.
> >>>
> >>> > Ouch, that's really bad. This is a 2.6.30 kernel, right? Is it still
> >>> > reproducible with an older 2.6.29 kernel or a 2.6.31 kernel from
> >>> > rawhide?
> >>>
> >>> okay, it works correctly on 2.6.29.  I'm trying to figure out how to
> >>> install 2.6.31 from rawhide without having dozens/hundreds of other
> >>> packages modified as well.  Is there some option to 'yum' that will do
> >>> what I need?
> >>
> >> 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.
> >>
> >> 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
> >> PGD 209d9d067 PUD 214dfa067 PMD 0
> >> Oops: 0002 [#1] SMP
> >> last sysfs
> >> file: /sys/devices/pci0000:00/0000:00:09.0/0000:01:00.0/0000:02:02.0/0000:05:00.0/0000:06:00.0/irq
> >> CPU 0
> >> Modules linked in: tun bridge stp llc xt_physdev ipt_LOG xt_limit
> >> xt_comment xt_multiport ip6t_REJECT nf_conntrack_ipv6 ip6table_filter
> >> ip6_tables ipv6 dm_multipath kvm_amd kvm bnx2 amd64_edac_mod shpchp
> >> edac_core i2c_piix4 serio_raw dcdbas raid1 raid10 mptsas mptscsih
> >> mptbase sata_svw scsi_transport_sas radeon ttm drm_kms_helper drm
> >> i2c_algo_bit i2c_core [last unloaded: freq_table]
> >> Pid: 1962, comm: qemu-kvm Not tainted 2.6.31.6-166.fc12.x86_64 #1
> >> PowerEdge 2970
> >> RIP: 0010:[<ffffffff8139aad7>]  [<ffffffff8139aad7>] destroy_conntrack
> >> +0x82/0x11f
> >>
> >> 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
> >>
> >> What can I do to help further diagnose this problem?
> >>
> >> _______________________________________________
> >> Fedora-virt mailing list
> >> Fedora-virt at redhat.com
> >> https://www.redhat.com/mailman/listinfo/fedora-virt
> >>
> >
> > For what it's worth I've been seeing very similar crashes.  I reported it as:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=545851
> >
> > and on the KVM list.  They thought it was a fault in the networking
> > stack, so people are now looking into it there.
> >
> > On my hardware, if I disable VT-d in the BIOS, the crashes don't happen.
> >
> > Adam
> >
> 
> As I've noted in the bug report, if I disable IPv6, the system is stable.

For me it's enough to disable iptables for bridge by adding:

net.bridge.bridge-nf-call-ip6tables = 0

to /etc/sysctl.conf

				SAL