vpar not booting because system memory is only 384 MByte

[Thomas Glanzmann]

Hello,
I have a rx7620 with two naprs. Each has 8192 MByte of memory. When I
create a vpar on both npars using this script:

rm /stand/vpdb
boot_device=$(lvlnboot -v | grep 'Boot:' | awk '{print $NF}' | sed -e 's/_p2//' -e 's/disk/rdisk/' -e 's/s2//' -e 's/dsk/rdsk/')
cell=$(ioscan -funC disk | grep 'disk' | awk '{print $3}' | cut -c 1 | sort -u)
bootdisk=$(dmesg | grep -i boot | awk {' print $NF}')
vparcreate -p vpar0 \
-a io:${cell}.0.0 -a io:${cell}.0.1 \
-a io:${bootdisk}:BOOT \
-a cpu::1 \
-a mem::2048:base \
-g ilm:256:y -g clm:256:y >/dev/null 2>&1
mkboot -a "boot vpmon -a" $boot_device
vparenv -m vpars
vparefiutil -u
shutdown -ry 0

The first npar comes up, but the second does not come up with the
following error message:

Press Any Key to interrupt Autoboot
\EFI\HPUX\AUTO ==> boot vpmon -a
Seconds left till autoboot - 0
AUTOBOOTING...> System Memory = 335 MB
loading section 0
... (complete)
loading section 1
......................................................................................................... (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
......Launching /stand/vpmon
SIZE: Text:1514K + Data:53301K + BSS:10761K = Total:65577K
Console is on virtual console - via PCDP
Database has changed as resource request could not be satisfied.
Look into the log file for more information.
Booting the partitions will alter the database on disk.
The original database will be saved as /stand/vpdb.orig
on the partition that owns the monitor boot disk.
If you want to retain the database, reboot the monitor
using the database file /stand/vpdb.orig.
MON> Launching all vPars with autoboot attribute set
[MON] Booting vpar0...
Error loading partition: Partition has zero base memory.

The first npar comes up correctly and also reports 8G of system memory
the second one only reports 335 MByte which is too less (the minimum
configuration is 1 GByte). However when running machinfo on the npar
(with vpar disabled) it reports also 8 GByte of memory. Any idea what is
going wrong?

Cheers,
Thomas