freebsd stable - May 2017 - FreeBSD Vagrant Box Kernel Panic

I was reading the previous thread about the current Vagrant box for FreeBSD
11.0-STABLE on atlas.hashicorp.com. The broken box is still not updated.
Who is the maintainer of these boxes?

On a side note, the reason freebsd/FreeBSD-11.0-RELEASE is revoked is there
is a newer -p1 box:
https://atlas.hashicorp.com/freebsd/boxes/FreeBSD-11.0-RELEASE-p1

It appears that the maintainer of the boxes should create a
11.0-RELEASE-p10 box and revoke the -p1 box.

Hello,
> Am 10.05.2017 um 21:24 schrieb Robert Simmons <rsimmons0 at
gmail.com>:
> It appears that the maintainer of the boxes should create a
> 11.0-RELEASE-p10 box and revoke the -p1 box.
The official Hashicorp boxes have been invoking freebsd-update on startup
for a while, now. So every box automatically updates itself to the latest
patchlevel.

We have started to roll our own boxes, so I'm not perfectly up-to-date.

Patrick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP
URL:
<http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20170511/381e458c/attachment.sig>