From mboxrd@z Thu Jan 1 00:00:00 1970 From: Travis Cross Subject: Re: Unable to boot dom0 with 2.6.16-rc1 and xen-3.0-testing Date: Wed, 08 Feb 2006 15:38:16 -0500 Message-ID: <43EA56B8.40306@crosswirecorp.com> References: <43E51DE7.9040009@crosswirecorp.com> <43E64DD6.9060102@crosswirecorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > Have you tried using the tip of unstable for everything (Xen, dom0, tools, domU)? I had tried unstable for Xen and tools, but was using the linux-2.6-xen tree for the kernel builds. I just pulled the latest changes from the unstable tree (8793) and tried again, this time building the kernels from unstable as well. That worked nicely :) For kicks, I pulled and rebuilt kernels from the linux-2.6-xen tree (19848). Those kernels seemed to work as well. It appears that changes merged in the last few days have solved this issue (thanks!). > There's not much point in pulling kernels from other repositories Just curious, what is the branch philosophy on the linux-2.6-xen.hg tree? It appears to pull more recent changes than the testing tree, but not pull all the latest changes in the unstable tree. Cheers, -- Travis