From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Problems booting latest xen pv-ops linux kernel Date: Wed, 18 Nov 2009 10:08:56 -0500 Message-ID: <20091118150856.GG15585@phenom.dumpdata.com> References: <87zl6klp06.fsf@frosties.localdomain> <20091118071044.GO16033@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20091118071044.GO16033@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Cc: Xen Developers List , Goswin von Brederlow List-Id: xen-devel@lists.xenproject.org On Wed, Nov 18, 2009 at 09:10:44AM +0200, Pasi K=E4rkk=E4inen wrote: > On Wed, Nov 18, 2009 at 12:18:01AM +0100, Goswin von Brederlow wrote: > > Hi, > >=20 > > I followed http://wiki.xensource.com/xenwiki/XenParavirtOps > > to build a bleeding edge linux kernel with > >=20 > > git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.= git linux-2.6-xen > >=20 > > I build the kernel for amd64 and installed Debians > > xen-hypervisor-3.4-amd64 package and bootet. Xen comes up nicely and > > starts the kernel. It detects my SATA disk (sata_sil driver) but then > > fails to read block 0. Something in xen breaks the sata_sil driver. > >=20 > > Booting the kernel as bare-metal works fine. > >=20 > > Anyone an idea what is wrong? The wiki lists a few problems (e.g. on > > 32bit use CONFIG_HIGHPTE=3Dn) but nothing for 64bit. Anything config > > option known to have sideeffects? > >=20 >=20 > You could try my .config: >=20 > cd linux-2.6-xen > cp -a .config .config-old > wget -O .config http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2= .6.31.4-pvops_dom0-x86_64 > make oldconfig > Pasi, The idea of the Wiki and people using it has been quite a good one. Do yo= u think it would make sense to include a checklist of things to when things don't= work. As in: 1). Try this .config. 2). Get serial console ('dmesg + xm dmesg') output to Xen-devel. To get = this via the serial console follow these steps: ...blah blah 3) and so on.