KZ with MRP failed to boot because not all the memory is allocated from MRP
(Doc ID 2823393.1)
Last updated on DECEMBER 19, 2023
Applies to:
Solaris Operating System - Version 11.4 and laterInformation in this document applies to any platform.
All the allocations for KZ do not come from MRP. The result is that when the machine is booted the KZs can be started just fine (and fill up the MRP).
But if the KZs are started on demand, while the main memory (non MRP) become filled with ZFS and others, it stops working at some point.
Symptoms
The results are:
Progress being logged to /var/log/zones/zoneadm.20200316T141434Z.admin...<kzname>.install
2020-03-16 15:14:51 error: request failed: Failed to create VM: Not enough space ERROR: failed to boot zone for install. zoneadm: zone 'admin...<kzname>': ERROR: installation failed: zone switching to configured state
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |