Re: [Xen-ia64-devel] PATCH: xencomm [2]

Akio Takebe wrote:  [Fri Sep 29 2006, 11:41:57AM EDT]
> Hmmm... But this issue was happened on x86-PAE.
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201796
> 
> Actually with dom0_mem=512M on FC6-ia64,
> we can success installing blkbk on rare occasions.

On PAE the problem was "fixed" by loading blkbk/netbk in
/etc/init.d/xend.  This moves the module load early enough in the
system boot to fix it on that arch.

However on ia64 this isn't sufficient.  We need either for the modules
to load *earlier* (such as in the initramfs) or we need to use
dom0_mem=1G (for example)

I have some questions, though:

1. On x86, all of the memory is assigned to dom0, then it balloons to
   give memory to unpriv'd domains.  Why does ia64 give only 512M to
   dom0 instead of doing the same as x86?

2. Juan says that he can boot x86 xen with only 128M of memory, and
   there's still enough physically contiguous to load blkbk and netbk
   when xend loads.  So why does ia64 need 8x the memory to do avoid
   fragmentation?  It seems like we must be doing something wrong for
   memory to fragment so quickly...!

Thanks,
Aron

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

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

[Xen-devel] [PATCH 5/6] xen, tools: add nr_cpus field to fix nr_cpus calc, Ryan Harper

Previous by Thread:

Re: [Xen-ia64-devel] PATCH: xencomm [2], Aron Griffis

Next by Thread:

[Xen-ia64-devel] PATCH: do not export XSI_BASE, use set_shared_info_va, Tristan Gingold

Indexes:

[Date] [Thread] [Top] [All Lists]