Hi MMN, you're doing everything right. The Hypervisor grabs 128MB for system use. You can visualize this with ldm list-devices -a memory.
Here's a sample from a machine with 64GB RAM:
# ldm list-devices -a memory
MEMORY
PA SIZE BOUND
0x0 512K _sys_
0x80000 1536K _sys_
0x200000 62M _sys_
0x4000000 8M _sys_
0x4800000 56M _sys_
0x8000000 16256M primary
0x400000000 16G ldom1
0x800000000 16G ldom2
0xc00000000 8G ldom3
0xe00000000 8G ldom4
If you add it all up, you'll see
128MB for _sys_ (the hypervisor)
16GB less 128MB for primary (yes, that's on purpose ;-) )
2x16GB for ldoms 1 and 2
2x8GB for ldoms 3 and 4
for a total of 64GB.
Your setup will look similar.
best regards,
stefan
On 09.06.10 07:59, MMN wrote:
> Hello,
>
> I have a T5120 with 16GB RAM. I have allocated 4 vcpus and 1GB RAM to the
> primary ldoms. So I was expecting to have 15GB RAM to be used by the guest
> OSs. I created two guest OSs and shared the remaining vcpus, RAM etc. When I
> try to bind it says memory not sufficient. If I reduce another GB, making the
> total RAM used by both guests to 14GB it works fine. So I am unable to use
> the full 16GB RAM.
>
> Can anyone please tell me what I could be doing wrong?
>
> Regards,
--
Stefan Hinker
Systems LOB - Systems & Performance
Sun Microsystems GmbH Tel: +49 6103 752-300
Brandenburger Str. 2-6 [email protected]
D-40880 Ratingen http://www.sun.de/
http://blogs.sun.com/cmt
http://blogs.sun.com/cmt/en
---------------------------------------------------------------------------
Sitz der Gesellschaft:
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht München: HRB 161028
Geschäftsführer: Jürgen Kunz
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ ldoms-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
