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: xming <xmingske@xxxxxxxxx>
Subject: [Xen-devel] Re: Cannot boot xen DomU > 2.6.23.1
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Sun, 20 Jan 2008 15:52:06 -0800
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx
Delivery-date: Sun, 20 Jan 2008 15:52:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <519a8b110801201129kd4347d5mf87920f69cf1821e@xxxxxxxxxxxxxx>
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> <519a8b110801201129kd4347d5mf87920f69cf1821e@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.9 (X11/20071115)
xming wrote:
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?

I'll probably look at this when my current batch of work is under control. In the meantime, I'll submit the workaround patch to keep people happy. The only downside is a small performance hit.

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?

It would be an interesting datapoint, but I don't think it will make a difference.

Maybe when I have nothing else to do.

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

Poke xen-devel.

   J

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