FYI, I just pushed a patch that properly allocates domain memory from
Xen's allocator. Before, we were simply scribbling over memory without
consulting the allocator. As it turns out, the hang I was experiencing
when starting the first domU was caused by this scribbling: we were
overwriting (at least) part of the 'heap' data structure.

I haven't changed the hardcoded domain=64MB, but this patch removes the
assumption from the DOM0_GETMEMLIST code, so that's goodness.

One other note... all domains now start with 64MB (the RMA). The domain
builders then try to add more memory, which goes over the maxmem limit
they set, and you'll see some error messages about that. Should be
harmless, but we'll need to figure out the right fix to push into the
tools (i.e. xend).

I won't push this into the -merge tree until other people have tested it
a little. I will be out tomorrow and Friday, so if I have broken you and
you're not interested in debugging, please:
a) open a bug (with lots of details, console logs, etc) at and assign it to me
b) back off to a previous changeset so you can continue to work happily.
In this case, you can get the previous changeset by running 'hg update

Hollis Blanchard
IBM Linux Technology Center

Xen-ppc-devel mailing list

Reply via email to