From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sam Johnston Subject: Re: Re: kernel panic with ipv6 in Xen Date: Sat, 7 May 2005 13:52:39 +0100 Message-ID: References: <9a83839538b51564881df9d95d3bf5d3@nodnol.org> Reply-To: Sam Johnston Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <9a83839538b51564881df9d95d3bf5d3@nodnol.org> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Chris Andrews Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > >> 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? >=20 > 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 NFS). Sam