This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] PageReserved ?

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] PageReserved ?
From: aq <aquynh@xxxxxxxxx>
Date: Sun, 17 Jul 2005 05:48:39 -0500
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 17 Jul 2005 10:47:17 +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=TQsNdBnqxj57I5C+71vGjHWUAUZBPzUOzEub5If+WV0Vy0B5LOH6MQlBdNk0ZDxM/Kc3sEbTBVI9c7YXI/mfXd65ontKJ2B8okFKowht3dtgyEjP0qP8b00fW20e3JHCU1kxaivoa2RdyB79Bdu8Zp5zZzJwGWFu7K/5Anb8buM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <d63ae47a2f19060e9d468b6528f210bf@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <9cde8bff050715112618053d6e@xxxxxxxxxxxxxx> <c3ae6fbfc08f789e717341235993fa03@xxxxxxxxxxxx> <9cde8bff050717003018101df2@xxxxxxxxxxxxxx> <68d0dfbc9997f39411120abbbb8f8c41@xxxxxxxxxxxx> <9cde8bff05071702403c9aadac@xxxxxxxxxxxxxx> <37caaad80708b68f9d608c83bb9bdbec@xxxxxxxxxxxx> <9cde8bff05071702497afeb2fa@xxxxxxxxxxxxxx> <d63ae47a2f19060e9d468b6528f210bf@xxxxxxxxxxxx>
Reply-to: aq <aquynh@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 7/17/05, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
> On 17 Jul 2005, at 10:49, aq wrote:
> >>> With xxx > 32M, domain always failed to boot.
> >>>
> >>> Any suggestion now?
> >>
> >> It's probably been broken by the 2.6.12 upgrade. I'll look into it.
> >
> > No, this is -testing tree (kernel
> I'd add xprintk's to the domU code (or turn printk into xprintk) and do
> a debug build of Xen. That'll get some early output from domU. Then you
> can work out how far it is getting and ultimately what line of code is
> failing.

ah, this is interesting. i will give it a try. lets see how to do that:

- you suggest adding xprintk to domU code - but exactly which code?
- or better redefine printk to xprintk in linux kernel of domU
- recompile xenU kernel (no need to recompile Xen and dom0 kernel).

is that correct?


Xen-devel mailing list