From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Unable to boot dom0 with 2.6.16-rc1 and xen-3.0-testing Date: Mon, 06 Feb 2006 09:37:00 +0100 Message-ID: <43E718BC.76F0.0078.0@novell.com> References: <43E51DE7.9040009@crosswirecorp.com> <43E64DD6.9060102@crosswirecorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <43E64DD6.9060102@crosswirecorp.com> 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: Travis Cross Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Try booting the kernel as uni-processor only; I would suspect the problem of booting SMP kernels (version 2.6.14 and later, cpu_possible_map getting set up too late) still hasn't been addressed ... Jan >>> Travis Cross 05.02.06 20:11:18 >>> > linux-2.6-xen.hg tracks xen-unstable, so it's newer than > 3.0-testing. Thanks for pointing that out. I started to suspect that might be the case after diff'ing both {xen-unstable,xen-3.0-testing}/linux-2.6-xen-sparse against linux-2.6-xen. So upon your suggestion, I installed xen and xen-tools from xen-unstable at 8758, to see if that might make the 2.6.16-rc1 kernel fly. The result was the same: 2.6.16-rc1 crashes promptly, 2.6.12.6 starts without a hitch. To check the sanity of my build options for the new kernel on this box, I built a vanilla 2.6.16-rc2 kernel without Xen, and started it without the hypervisor running (it worked). > It ought to work when rolled back to a suitable version, or just > use Linux 2.6.12 in the unstable repo. I can start the 2.6.12.6 kernel on any Xen build from xen-3.0.0 to xen-3.0-testing to the latest xen-unstable. I can't seem to get a late-model linux kernel to boot though (either as a dom0 or domU, actually). Is there a revision after 2.6.12.6 and before the tip that it might be useful to test? Cheers, -- Travis Keir Fraser wrote: > > On 4 Feb 2006, at 21:34, Travis Cross wrote: > >> I am unable to boot dom0 on a x86_64 (Pentium D dual core) >> machine using xen-3.0-testing at changeset 8738 and >> linux-2.6-xen at changeset 19827. Booting dom0 using the >> latest xen hypervisor and linux-2.6.12.6 seems to work. > > > Older guest on newer Xen should always work, but the same isn't > true for newer guest on older Xen. linux-2.6-xen.hg tracks > xen-unstable, so it's newer than 3.0-testing. > > It ought to work when rolled back to a suitable version, or just > use Linux 2.6.12 in the unstable repo. > > -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel