[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: kernel panic with ipv6 in Xen

  • To: Chris Andrews <chris@xxxxxxxxxx>
  • From: Sam Johnston <samjie@xxxxxxxxx>
  • Date: Sat, 7 May 2005 13:52:39 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sat, 07 May 2005 12:52:14 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZpSkeF4Mcko168n4enur3GPowAnBrLc2E6lJavgAzbqoZVwgQS76OY/goNh4nvwp9Wh1cpxHgIz+260knbvm+HyYtb5DattlAewOFpsE263Vi75HgF/sKpSsxSKbTaxdgxt5pN1iz5qLMt90pf9Ouh2p2/dhnO9CXkzq/Ti/Yoc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> >> We have a kernel panic on boot under xen when loading the ipv6 module
> >> which was resolved by mounting the device under dom0 and moving the
> >> ipv6 module out of the way. Is this a known problem? Is it likely to
> >> be a xen issue? An ipv6 issue? PEBCAK?
> I've seen this after upgrading Xen and the dom0 kernel, then starting a
> domain with the old xenU kernel and modules. Once I ran the new xenU
> kernel and installed its modules in the domU fs I had no problems. This
> was probably around 2.0.3 or so.

Thanks for the feedback.

It would seem then that the best solution for us is to use the debian
kernel packaging tools to create a common kernel which would then be
installed into dom0 and domU along with the matching modules.
Alternatively we could make the dom0 modules available in the guest
domains by mounting /lib/modules read only (as block devices or via


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.