WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: Cannot boot xen DomU > 2.6.23.1

To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Subject: [Xen-devel] Re: Cannot boot xen DomU > 2.6.23.1
From: xming <xmingske@xxxxxxxxx>
Date: Sun, 20 Jan 2008 20:29:47 +0100
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx
Delivery-date: Tue, 22 Jan 2008 10:00:07 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Xrv92xZoQfAmiOw6QHBd+kBOXSvxhDs4VaB3d/2hI5Y=; b=xDIcSLcvs8DCdc23d8aT1EhvAmG36ErKco9GzLm5tP+tFOrNp691GKdFmq8SG0hWfkLzzEwTLsz+y0EXc6uaYhnNn3eecDSsKIw8V9GbiGqPeWT6sPsTkxsQSsAmSRvVVkeYe9/p+/hUUAFfI1/EreMGgdi0t2/jydX1DilEXJc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Z+mfzcllcY/wPadD5JFh8D/nVipDzDy2eL67QFhxlX5u8Rhm6vCSTAFAoFORRP8C7wvy6ARCFJAQce5GLgBQV4K5sKghij+MakJCtgk+RoAZsrKcWduDlYvBKvC25Jm7SgXdeWUKUEv1XeGzIgdALECCyTBRgSjicAUJ84z62Wk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <479394D9.50104@xxxxxxxx>
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: <519a8b110801170813h96b8f2by795e6d8b72a00ba4@xxxxxxxxxxxxxx> <478F8D22.60004@xxxxxxxx> <519a8b110801171113y20a3bedfg446e29a30712a26d@xxxxxxxxxxxxxx> <4790561E.9040508@xxxxxxxx> <519a8b110801180438l389ec1d6t7b888b8c78d59dd8@xxxxxxxxxxxxxx> <4790D187.8050000@xxxxxxxx> <519a8b110801180856o7757889as47106fd3eabcc0de@xxxxxxxxxxxxxx> <4790E13D.5040603@xxxxxxxx> <519a8b110801200508l1fb3dee9ha197f3fc76ccac69@xxxxxxxxxxxxxx> <479394D9.50104@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Jan 20, 2008 7:37 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> xming wrote:
> > ok I have done some of them, but I still don't know what I should be looking
> > at. Do you mean code related to xen or code related to 
> > have_vcpu_info_placement?
> > Please be patient with me :)
> >
> > I just paste some of the result (around those addresses) here:
> >
>
> Thanks, that answers that particular question; the vcpu is blocked
> waiting for something to happen, which probably means it missed the
> event which was supposed to wake it up.  Why is another question.  At
> least there's a workaround, and that workaround gives me some clue where
> to look.

Want me to test it?

> BTW, is it an SMP or UP domain?   Does it make a difference?

It doesn't matter, I tried vcpu=1 and vcpu=2, unless you want me to try
to recompile a UP kernel?

> >> OK, good.  I Didn't Break It (tm) ;)
>
> > So no fix from you? :)
>
> Maybe when I have nothing else to do.

I'll wait, or should I poke xen-devel?

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel