RE: [Xen-devel] [timer/ticks related] dom0 hang during boot on large 1TB system

["Jan Beulich" <JBeulich@xxxxxxxxxx>]

>>> Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> 22.12.09 17:05 >>>
>> From: Jan Beulich [mailto:JBeulich@xxxxxxxxxx] 
>> 
>> >>> Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> 22.12.09 16:30 >>>
>> >Mukesh's work has been on a 32-bit dom0.
>> 
>> Which seems quite odd a combination - 1Tb of memory, but a 32-bit
>> Dom0 -, which is why initially I didn't even consider the 
>> possibility. I'm
>> afraid you're asking for more trouble with this.
>
>Indeed.  Oracle expects to move to a 64-bit dom0 in a "future"
>release, but we have to make the 32-bit dom0 work until then.
>
>Our default configuration specifies dom0_mem=xxx which I would
>assume would eliminate most or all of the "trouble" you are
>referring to, but, Mukesh, could you confirm what dom0_mem
>is set to?

No, that won't help. I'm referring to things like Dom0 accesses to the
M2P table it sees, which doesn't cover even nearly all memory. I can't
say whether that can go without problem, but without closely looking
at it I don't think you can assume this would work. Likewise I would
suspect tools issues (if you use the tools from xen-unstable et al),
though I have no precise pointer right now at specific issues.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel