Xen devel - Aug 2008 - Not enough RAM for domain 0 allocation.

Hi all,
 I have been trying to use Xen with a diskless workstation.
My system has 3G of RAM. I have built a ramdisk (whose size is 450M)  and
I''m trying to load everything in memory (Xen,Dom0 and the ramdisk).

In the file arch/x86/domain_build.c the function alloc_domheap_pages
is invoked page=alloc_domheap_pages(d,order,MEMF_bit(30);  // in my case
order =17

This function returns a NULL pointer, which generates the error "Not enough
RAM for domain 0 allocation"
It seems that if the total size of hypervisor+dom0+ramdisk is less than 256M
everything works, if it is bigger than that I got that  problem.
Is there anything I have to set? I have tried playing with dom0_mem but
nothing worked.
Any hint on how to proceed would really help me a lot.

Thanks,
  Luca


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

Are you using 64-bit Xen? In that case we can fix this probably quite
easily. For 32-bit Xen it is harder.

 -- Keir

On 12/8/08 20:37, "Luca" <lucarx76@gmail.com> wrote:
> Hi all,
>  I have been trying to use Xen with a diskless workstation.
> My system has 3G of RAM. I have built a ramdisk (whose size is 450M)  and
I''m
> trying to load everything in memory (Xen,Dom0 and the ramdisk).
> 
> In the file arch/x86/domain_build.c the function alloc_domheap_pages
> is invoked page=alloc_domheap_pages(d,order,MEMF_bit(30);  // in my case
order
> =17
> 
> This function returns a NULL pointer, which generates the error "Not
enough
> RAM for domain 0 allocation"
> It seems that if the total size of hypervisor+dom0+ramdisk is less than
256M
> everything works, if it is bigger than that I got that  problem.
> Is there anything I have to set? I have tried playing with dom0_mem but
> nothing worked.
> Any hint on how to proceed would really help me a lot.
> 
> Thanks,
>   Luca
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel



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

I''m using a 32-bit Xen. But I could switch to a 64-bit if fixing that
problem is easier.
So, how can I fix the problem with a 64-bit Xen?

Thanks,
 Luca


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

Replace MEMF_bit(30) with 0 and let us know how that works.

 -- Keir

On 12/8/08 22:28, "Luca" <lucarx76@gmail.com> wrote:
> I''m using a 32-bit Xen. But I could switch to a 64-bit if fixing
that problem
> is easier. 
> So, how can I fix the problem with a 64-bit Xen?
> 
> Thanks,
>  Luca
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel



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

It worked. I didn''t even have to change it because the code had already
''0''
instead of ''MEMF_bit(30)''

Thanks


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