From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
Kathy Hadley <Kathy.Hadley@dornerworks.com>,
George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools)
Date: Thu, 24 Jun 2010 14:23:09 +0100 [thread overview]
Message-ID: <C8491ACD.18822%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <c18aa115-0e0d-4612-9dda-5852e8c129c4@default>
Yes, one possibility here is that somehow you do not have xenconsoled
running. You should 'ps auxw' in dom0 and check that xenstored and
xenconsoled are both running.
I now start xend with a little 'xenstored; xenconsoled; xend start' script.
:-)
-- Keir
On 24/06/2010 14:08, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:
> Just a thought...
>
> With all the recent tool layer changes (involving udev, xend,
> bridging etc), any chance that everything in the guest
> is working just fine and everything in the hypervisor
> is working just fine but the connections to the console
> in your distro/configuration are not playing nicely with
> the recent xen-unstable tool changes, so you just can't see
> that everything (else) is fine?
>
> (if so, please support my recent rant against changes that
> cause "unnecessary pain" ;-)
>
>> -----Original Message-----
>> From: Kathy Hadley [mailto:Kathy.Hadley@dornerworks.com]
>> Sent: Thursday, June 24, 2010 6:54 AM
>> To: Keir Fraser; George Dunlap
>> Cc: xen-devel@lists.xensource.com
>> Subject: RE: [Xen-devel] [PATCH 1/1] Xen ARINC 653 Scheduler (updated
>> to add support for CPU pools)
>>
>> We are using the following set-up:
>> Xen-unstable changeset 21650
>> Gentoo 2.6.29.6 with Xen patches for Dom0
>> Linux 2.6.18-Xen for DomU (downloaded from linux-2.6.18-xen.hg)
>>
>> Dom0 and DomU run fine with Xen-3.4.1 and Xen-4.0.0 (our scheduler or
>> the credit scheduler). Dom0 appears to run fine with xen-unstable, but
>> DomU "hangs" when our scheduler or the credit scheduler (as discussed
>> in
>> earlier e-mails). "xm list" shows that DomU is blocked.
>>
>> Do you have any suggestions for how I could troubleshoot this issue?
>> I'm still wondering about the warning I'm seeing issued from traps.c -
>> while it could have nothing to do with my issue, it is an interesting
>> coincidence.
>>
>> Thanks,
>> Kathy Hadley
>>
>>> -----Original Message-----
>>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
>>> Sent: Wednesday, June 23, 2010 6:36 PM
>>> To: Kathy Hadley; George Dunlap
>>> Cc: xen-devel@lists.xensource.com
>>> Subject: Re: [Xen-devel] [PATCH 1/1] Xen ARINC 653 Scheduler (updated
>>> to add support for CPU pools)
>>>
>>> I've just built latest xen-unstable.hg and linux-2.6.18-xen.hg and
>>> booted a
>>> domU just fine. All my builds are 64-bit though whereas yours are 32-
>>> bit. I
>>> suppose that could cause a difference (in particular, 32-bit
>> hypervisor
>>> is
>>> less tested by people).
>>>
>>> -- Keir
>>>
>>> On 23/06/2010 22:16, "Kathy Hadley" <Kathy.Hadley@dornerworks.com>
>>> wrote:
>>>
>>>> Keir,
>>>> I see this same behavior when I run the credit scheduler. It
>>> doesn't
>>>> look like it's localized to the scheduler I'm working on. I pulled
>>> the
>>>> latest code from http://xenbits.xensource.com/linux-2.6.18-xen.hg
>> and
>>>> rebuilt the kernel earlier today, with no effect.
>>>>
>>>> Note that I can successfully start the domain with Xen-3.4.1 and
>>>> Xen-4.0.0, using the same configuration file as I am using with
>>>> xen-unstable.
>>>>
>>>> Kathy
>>>>
>>>>> -----Original Message-----
>>>>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
>>>>> Sent: Wednesday, June 23, 2010 4:23 PM
>>>>> To: Kathy Hadley; George Dunlap
>>>>> Cc: xen-devel@lists.xensource.com
>>>>> Subject: Re: [Xen-devel] [PATCH 1/1] Xen ARINC 653 Scheduler
>>> (updated
>>>>> to add support for CPU pools)
>>>>>
>>>>> On 23/06/2010 20:57, "Kathy Hadley" <Kathy.Hadley@dornerworks.com>
>>>>> wrote:
>>>>>
>>>>>> Call Trace:
>>>>>> [<c01013a7>] hypercall_page+0x3a7 <--
>>>>>> [<c0109005>] raw_safe_halt+0xa5
>>>>>> [<c0104789>] xen_idle+0x49
>>>>>> [<c010482d>] cpu_idle+0x8d
>>>>>> [<c0404895>] start_kernel+0x3f5
>>>>>> [<c04041d0>] do_early_param+0x80
>>>>>>
>>>>>> Does this shed any light on the situation?
>>>>>
>>>>> Looks like you're in the idle loop. So, no, it doesn't really shed
>>>> much
>>>>> useful light.
>>>>>
>>>>> -- Keir
>>>>>
>>>>
>>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-06-24 13:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 15:04 [PATCH 1/1] Xen ARINC 653 Scheduler (updated to add support for CPU pools) Kathy Hadley
2010-06-16 15:50 ` George Dunlap
2010-06-16 16:00 ` Kathy Hadley
2010-06-16 16:13 ` Keir Fraser
2010-06-16 16:14 ` George Dunlap
2010-06-16 16:20 ` Keir Fraser
2010-06-16 16:25 ` Kathy Hadley
2010-06-16 16:31 ` Keir Fraser
2010-06-16 16:40 ` Kathy Hadley
2010-06-16 16:49 ` Keir Fraser
2010-06-16 18:03 ` Kathy Hadley
2010-06-17 7:04 ` Keir Fraser
2010-06-17 18:16 ` Kathy Hadley
2010-06-17 18:26 ` Keir Fraser
2010-06-18 17:35 ` Kathy Hadley
2010-06-18 17:49 ` Keir Fraser
2010-06-19 11:14 ` George Dunlap
2010-06-22 19:10 ` Kathy Hadley
2010-06-22 19:16 ` Keir Fraser
2010-06-23 19:57 ` Kathy Hadley
2010-06-23 20:23 ` Keir Fraser
2010-06-23 21:16 ` Kathy Hadley
2010-06-23 22:36 ` Keir Fraser
2010-06-24 12:53 ` Kathy Hadley
2010-06-24 13:08 ` Dan Magenheimer
2010-06-24 13:18 ` Kathy Hadley
2010-06-24 13:23 ` Keir Fraser [this message]
2010-06-24 13:32 ` Kathy Hadley
2010-06-30 20:44 ` Kathy Hadley
2010-06-30 20:54 ` Keir Fraser
2010-07-14 17:32 ` Kathy Hadley
2010-07-14 18:04 ` Keir Fraser
2010-06-16 16:25 ` George Dunlap
2010-06-17 5:02 ` Juergen Gross
2010-06-17 6:09 ` Keir Fraser
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=C8491ACD.18822%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Kathy.Hadley@dornerworks.com \
--cc=dan.magenheimer@oracle.com \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).