On Wed, May 24, 2017 at 08:28:37AM -0700, jungle Boogie wrote: > On 24 May 2017 at 08:19, Glen Barber <g...@freebsd.org> wrote: > > On Tue, May 23, 2017 at 01:14:56PM -0700, jungle Boogie wrote: > >> Hi Eric, > >> On 23 May 2017 at 05:47, Eric Badger <bad...@freebsd.org> wrote: > >> > On 04/26/2017 09:01 AM, David Boyd wrote: > >> >> > >> >> Using 11.0-STABLE VM image snapshots, since April 05, 2017, FreeBSD > >> >> panics when VBoxService starts. > >> >> > >> >> using snapshot FreeBSD-11.0-RELEASE-amd64.vmdk no panic occurs. > >> >> > >> >> using snapshot FreeBSD-11.0-STABLE-amd64-20170323-r315855.vmdk no panic > >> >> occurs. > >> >> > >> >> using snapshot FreeBSD-11.0-STABLE-amd64-20170405-r316498.vmdk panic > >> >> occurs (see attachment). > >> >> > >> >> using snapshot FreeBSD-11.0-STABLE-amd64-20170420-r317153.vmdk panic > >> >> occurs (see attachment). > >> >> > >> >> using snapshot FreeBSD-12.0-CURRENT-amd64.vmdk no panic occurs. > >> >> > >> >> I am prepared to submit a PR if that is the thing to do. > >> >> > >> >> Thanks, in advance, for your assistance in this matter. > >> >> > >> > > >> > Please try again after r318743. I believe it fixes this problem. > >> > > >> > >> This sounds like good news! Maybe when the next snapshots are created, > >> this will be fixed. > >> > >> There's a couple PR's opened on this issue, but neither of them have > >> any updates. Was this tracked under a different PR? > >> > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219146 > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219227 > >> > > > > Confirmed, this is resolved after r318743. > > > > Great news! Then it's clearly something on my side. What's your host OS? >
FreeBSD 12-CURRENT. One thing to note about the image I just used to test, it is not named 11.0-STABLE anymore. Try this: $ vagrant init freebsd/FreeBSD-11.1-PRERELEASE $ vagrant up Glen
signature.asc
Description: PGP signature
