From: Jeremy Fitzhardinge <jeremy@goop.org>
To: xming <xmingske@gmail.com>
Cc: linux-kernel@vger.kernel.org, Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Cannot boot xen DomU > 2.6.23.1
Date: Sun, 20 Jan 2008 10:37:13 -0800 [thread overview]
Message-ID: <479394D9.50104@goop.org> (raw)
In-Reply-To: <519a8b110801200508l1fb3dee9ha197f3fc76ccac69@mail.gmail.com>
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.
BTW, is it an SMP or UP domain? Does it make a difference?
>> OK, good. I Didn't Break It (tm) ;)
>>
>
> So no fix from you? :)
>
Maybe when I have nothing else to do.
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: xming <xmingske@gmail.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>, linux-kernel@vger.kernel.org
Subject: Re: Cannot boot xen DomU > 2.6.23.1
Date: Sun, 20 Jan 2008 10:37:13 -0800 [thread overview]
Message-ID: <479394D9.50104@goop.org> (raw)
In-Reply-To: <519a8b110801200508l1fb3dee9ha197f3fc76ccac69@mail.gmail.com>
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.
BTW, is it an SMP or UP domain? Does it make a difference?
>> OK, good. I Didn't Break It (tm) ;)
>>
>
> So no fix from you? :)
>
Maybe when I have nothing else to do.
J
next prev parent reply other threads:[~2008-01-20 18:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 16:13 Cannot boot xen DomU > 2.6.23.1 xming
2008-01-17 17:15 ` Jeremy Fitzhardinge
2008-01-17 19:13 ` xming
2008-01-18 7:32 ` Jeremy Fitzhardinge
2008-01-18 7:32 ` Jeremy Fitzhardinge
2008-01-18 12:38 ` xming
2008-01-18 16:19 ` Jeremy Fitzhardinge
2008-01-18 16:56 ` xming
2008-01-18 17:26 ` Jeremy Fitzhardinge
2008-01-20 13:08 ` xming
2008-01-20 18:37 ` Jeremy Fitzhardinge [this message]
2008-01-20 18:37 ` Jeremy Fitzhardinge
2008-01-20 19:29 ` xming
2008-01-20 23:52 ` Jeremy Fitzhardinge
2008-01-20 23:52 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=479394D9.50104@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
--cc=xmingske@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.