Date: Wed, 24 May 2017 15:45:33 +0000 From: Glen Barber <gjb@FreeBSD.org> To: jungle Boogie <jungleboogie0@gmail.com> Cc: Eric Badger <badger@freebsd.org>, David Boyd <David.Boyd49@twc.com>, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: FreeBSD as VirtualBox guest panics when starting VBoxService Message-ID: <20170524154533.GA93345@FreeBSD.org> In-Reply-To: <CAKE2PDu8Z7GtY0DWYVmsOPxeWm8zwWu8Y8=hy-k-JSo8iO%2BsTA@mail.gmail.com> References: <1493215268.4148.0.camel@twc.com> <7da4bfee-cf0c-70ff-3614-39415004ee67@FreeBSD.org> <CAKE2PDv1qr4pRygsyoDhfWWtALRmg1ysWeE99b5SM6AnUhn2Pg@mail.gmail.com> <20170524151912.GD80123@FreeBSD.org> <CAKE2PDu8Z7GtY0DWYVmsOPxeWm8zwWu8Y8=hy-k-JSo8iO%2BsTA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 24, 2017 at 08:28:37AM -0700, jungle Boogie wrote: > On 24 May 2017 at 08:19, Glen Barber <gjb@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 <badger@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 p= anic > >> >> 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=3D219146 > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219227 > >> > > > > Confirmed, this is resolved after r318743. > > >=20 > Great news! Then it's clearly something on my side. What's your host OS? >=20 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 --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlklqp0ACgkQAxRYpUeP 4pNf7g//Tm6ovzWx7zKke+08d9czoxVWigO9RuIYn1Qw1h94+Osz3/sM3+l7t+by 8VI5fZtr2nWs4+rQH+xEbC6BW6FWon1Z7TXsLwJ8HGT58BA+tlQvqk79UVvZxLlz OYph7723ofAbm8jaS0DgEfrXppqqtbJOdgsLzvYMmjh/n82GMFtyp/qVPeo/jLkt RohVykjA6RfuzpDPUSRDsA+NbMdsjQt4BqlqiUnL6lgDwV6DGqYOR+WseZX4OpPP roCimTdRO0gfR4pvU2YVHtXzgQ18H7PSb1+aQCoEAYNZMNf5klzcgloj2kM3Vlp5 lI4nYmb9Uvw8oiLSTv0TX/Q+FqetQkkigPdF9n3QUk7pOy+RiZUGyYUob0araXDE iLkv29W02IZd13sSB/0zrh0rjHtKFKpy9BIaqzzmJriGPhfcovHJAw6bR/L4K9f8 /SCyARsrbWX3VRb8+dxsZOYmujB4fcRHtyzUfTIur4OWTIwmPb1HufKWSLkejHMW qkPco2lzc2/H6wXRiCcES5nViciIFCgAKJz247ZmokhEq46s9UWbS6NeePYS/O9u TsrEuntBJTg2oezVPoVFfxMZmNxqteFGycwr4n66t2TQhnTMe1ROdAbxblWjbdAD +kqPooBREdRNPAOmyNZYB9Nx6y/7RzyKQCnZrI4i4h2LoFd+Kw8= =eO7Q -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170524154533.GA93345>