16:26:23 <natefoo> Hey all, I have a bhyve vm that I just cannot get to boot if I increase the memory over ~20G or so
16:27:05 <natefoo> I read that vmadm tends not to calculate the capped-memory values in the zonecfg high enough, but even after adjusting those it won't boot
16:28:00 <natefoo> No VNC and I can't find boot failure logs (maybe I'm not looking in the right place? It's been a while)
16:33:11 <natefoo> Ah right /zones/<uuid>/logs/platform.log
16:33:43 <natefoo> { "time": "2023-11-01T16:18:29.085306000Z", "v": 0, "hostname": "smart1", "name": "zoneadmd","pid": 86440, "level": 30, "msg":"Unable to allocate memory (25769803776), retrying in 1 second\n", "stream":"stderr" }
17:08:51 <natefoo> Well it's working now, I can't say exactly why though. More memory was in use on the GZ than processes added up to, so with a 24GB VM it was a few GB shy of the actual amount of physical memory. Since it was also running a fairly old release from 2020, I went ahead and rebooted into a 2023 release, and it's working now.
17:39:29 <pjustice> jperkin: the apache package today seems to have broken module ini files
17:42:35 <pjustice> er, scuse, php 5
17:42:41 <pjustice> sorry, brain
17:43:22 <jperkin> pjustice: ouch, can you file a ticket? thanks
17:43:43 <pjustice> yes, working on that
17:50:30 <pjustice> #367
18:00:02 <jperkin> ok, I see the problem, over-zealous cleanup by a different developer