[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] Re: Cannot boot xen DomU > 126.96.36.199
- To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
- 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
- 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=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
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