Re: Test results on Unisys ES7000 64x 256gb using unstable c/s 16693 on 3.2.0 Release Candidate

[Bill Burns <bburns@redhat.com>]

Carb, Brian A wrote:
> Test results on Unisys ES7000 64x 256gb using unstable c/s 16693 on
> 3.2.0 Release Candidate
>  
> HOST:
> Unisys ES7000/one, x86_64, 64 processors, 256gb memory
> unstable changeset 16693 compiled with max_phys_cpus=64 and booted with
> dom0_mem=4096M, numa=on, and xenheap_megabytes=64
> from http://xenbits.xensource.com/staging/xen-unstable.hg pulled on
> 20080108:
>  

<snip>

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.

Thanks,
 Bill