From: Bill Burns <bburns@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, "Carb, Brian A" <Brian.Carb@unisys.com>
Subject: Re: Test results on Unisys ES7000 64x 256gb using unstable c/s 16693 on 3.2.0 Release Candidate
Date: Tue, 15 Jan 2008 11:15:36 -0500 [thread overview]
Message-ID: <478CDC28.8040706@redhat.com> (raw)
In-Reply-To: <C3B27765.1ACDA%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
> On 15/1/08 13:50, "Bill Burns" <bburns@redhat.com> wrote:
>
>> We have noticed problems with dom0 initialization when not
>> limiting the memory for dom0 when we reach 112GB. This is using
>> 3.1.2 and also appears in 3.1.3 as it stood last week. Note that
>> 3.1.0 had no such issue. The problem is definately a Hypervisor
>> change of some sort (as opposed to a dom0 kernel change).
>>
>> Wondering if anyone else sees this? And while it makes a lot
>> of sense to limit dom0 memory we have not in the past. And it's
>> somewhat problematic to know what to limit it too. We are in
>> the process of trying to determine what change set introduced
>> this regression.
>
> Have you tried 3.2.0 release candidates?
>
> I doubt any other developers are going to run into this as we're not
> overwhelmed with 128GB+ systems.
>
> -- Keir
>
>
No, I have not tried on 3.2.0. Will see if I can at some
point...
Bill
next prev parent reply other threads:[~2008-01-15 16:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 2:15 Test results on Unisys ES7000 64x 256gb using unstable c/s 16693 on 3.2.0 Release Candidate Carb, Brian A
2008-01-15 13:50 ` Bill Burns
2008-01-15 14:44 ` Keir Fraser
2008-01-15 16:15 ` Bill Burns [this message]
2008-01-15 16:29 ` Keir Fraser
2008-01-16 15:45 ` Bill Burns
2008-01-17 14:10 ` Test results on Unisys ES7000 64x 256gb using unstablec/s " Ian Pratt
2008-01-18 13:03 ` Bill Burns
2008-01-24 17:23 ` Bill Burns
2008-01-25 13:06 ` Bill Burns
2008-01-28 14:02 ` Bill Burns
2008-01-28 14:08 ` Keir Fraser
2008-01-28 20:38 ` Test results on Unisys ES7000 64x 256gb usingunstablec/s " Carb, Brian A
2008-01-28 21:12 ` Bill Burns
2008-01-29 8:44 ` Test results on Unisys ES7000 64x 256gbusingunstablec/s " Jan Beulich
2008-01-30 16:20 ` Test results on Unisys ES7000 64x 256gb using unstablec/s " Bill Burns
2008-01-30 16:45 ` Keir Fraser
2008-01-31 18:12 ` Bill Burns
2008-02-01 8:36 ` Keir Fraser
2008-02-01 12:40 ` Bill Burns
2008-02-01 20:10 ` Bill Burns
2008-02-08 13:49 ` Large system boot problems Bill Burns
2008-02-08 14:04 ` Keir Fraser
2008-02-08 15:10 ` Bill Burns
2008-02-08 15:14 ` Keir Fraser
2008-02-08 15:22 ` Bill Burns
2008-02-08 15:45 ` Keir Fraser
2008-02-12 16:34 ` Bill Burns
2008-02-12 16:54 ` 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=478CDC28.8040706@redhat.com \
--to=bburns@redhat.com \
--cc=Brian.Carb@unisys.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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 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.