Date: Sat, 22 Dec 2018 21:13:57 -0800 From: Kevin Oberman <rkoberman@gmail.com> To: Per Hedeland <per@hedeland.org> Cc: "freebsd-emulation@freebsd.org" <emulation@freebsd.org> Subject: Re: Instant crash starting VBox on 12.0-Stable Message-ID: <CAN6yY1sF3ZnJL96rKhfQidDCXDuixwH1AWcAB48O2=d4kSfvGg@mail.gmail.com> In-Reply-To: <401db2b8-9831-7419-a675-357e41bf24f9@hedeland.org> References: <CAN6yY1saUuMhXDxDoW1TnOakWhGM5J_EyHjx1KVn5KrOsXW9xA@mail.gmail.com> <CAN6yY1sUvQU-uJEGDTgK-nbPvqhbbYzqNS%2Bhc6=wTjb5B2Mm5A@mail.gmail.com> <401db2b8-9831-7419-a675-357e41bf24f9@hedeland.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 22, 2018 at 3:58 PM Per Hedeland <per@hedeland.org> wrote:
> On 2018-12-22 19:19, Kevin Oberman wrote:
> >
> > Can anyone confirm running VirtualBox on head after 11.0-Release?
>
> Apparently you meant to ask "after 12.0-RELEASE", though I'm not sure
> about the "after" - anyway *on* 12.0-RELEASE, I'm running
> virtualbox-ose-5.2.18_1 (from package) with
> virtualbox-ose-kmod-5.2.22_1 (from port) without problems. Pretty
> light usage though, a single VM running Linux, started "directly" with
> "VirtualBox --startvm xxx" and only access via ssh. Starting the
> "manager application" i.e. plain "VirtualBox", works fine too, though.
>
> But, I'm not loading any vboxnet* modules (seems to be more than one
> these days), only vboxdrv - and that via kld_list in rc.conf, i.e. I
> have no vbox* variables set there. After fighting with the networking
> setup (in more complex cases, that I don't currently use) with first
> vmware and then qemu I decided to do as little as possible of that
> with VirtualBox itself - only bridge to a tapN device, and do the rest
> ("actual" bridging/routing) with the standard FreeBSD functionality.
>
> --Per Hedeland
>
No, I actually meant "be4fore", but I guess it depends on your point of
view.. The issue was first reported on RC2, and I have now tested to before
the branch of 12 from head. I am about to test on head from August. It has
worked on 11.2 all the way through Dec. 17, so it is something that changed
some time ago. Your experience tells me that, as I had suspected, that the
issue is with the network module which you do not use. So I am just hoping
that someone who was testing head and used VirtualBox with networking.
Thanks for the report. It certainly help a bit. Now to boot the August 2018
kernel and see what happens.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1sF3ZnJL96rKhfQidDCXDuixwH1AWcAB48O2=d4kSfvGg>