I'll give it a try.
On Wed, 2007-02-07 at 11:59 -0600, Hollis Blanchard wrote:
I use a vmlinux as dom0, but it's a stripped vmlinux. A vmlinux with
full debug symbols is 55MB here, which probably explains this problem.
Could you see how easy it would be to catch this problem at runtime and
If the problem were that dom0 was only partially transferred, we would
see dom0 start to boot and fail. The boot_of_alloc_init message happens
way before that point.
The early boot code only tracks the first 32M of memory, and I believe
that is the problem here: we're overflowing the bitmap we're
On Feb 7, 2007, at 5:38 PM, Hollis Blanchard wrote:
If the problem were that dom0 was only partially transferred, we would
see dom0 start to boot and fail. The boot_of_alloc_init message
happens
way before that point.
Thats not really true, dom0 is in .data, there are actually
