What build are you upgrading from?
Is this during the "attach -u" portion of the upgrade for each zone?
Can you gather any core files (or pstacks of core files)? These might
be at <zonepath>/root/
My "guess" is that init (in the zone) is starting using a downrev libc
(aka libc not upgraded yet), and is making a system call that has
changed. 12 is SIGSYS.
On 11/18/10 11:14 AM, Ian Collins wrote:
I run through the upgrade process on a system with half a dozen zones
and on restart, they all get locked into a core dump/restart loop:
Nov 19 07:57:50 i7 genunix: [ID 729207 kern.warning] WARNING: init(1M)
for zone webhost (pid 3094) core dumped on signal 12: restarting
They all run through this cycle in tight loops.
zones-discuss mailing list