Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 22 Dec 2018 12:13:17 -0700
From:      "Dale Scott" <dalescott@shaw.ca>
To:        "'Kevin Oberman'" <rkoberman@gmail.com>, <emulation@freebsd.org>
Subject:   RE: Instant crash starting VBox on 12.0-Stable
Message-ID:  <006b01d49a2a$666e8510$334b8f30$@shaw.ca>
In-Reply-To: <CAN6yY1sUvQU-uJEGDTgK-nbPvqhbbYzqNS%2Bhc6=wTjb5B2Mm5A@mail.gmail.com>
References:  <CAN6yY1saUuMhXDxDoW1TnOakWhGM5J_EyHjx1KVn5KrOsXW9xA@mail.gmail.com> <CAN6yY1sUvQU-uJEGDTgK-nbPvqhbbYzqNS%2Bhc6=wTjb5B2Mm5A@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Fwiw, I am running virtualbox-ose-nox11-5.2.22 on FreeBSD 11.2 with (almost)
no issues. I installed virtualbox-ose-nox11 using pkg, then compiled
virtualbox-ose-kmod from ports (compiling kmod on the box was required about
a year ago or the system would crash at boot, and I follow the same
procedure after pkg upgrade).

I use phpvirtualbox for a UI, which reports an error if I try to snapshot
(so I don't snapshot). The only time vbox has crashed was once when I tried
running two vms, and I assumed it was due to insufficient memory or some
other system issue, and not virtualbox per se.

Dale

> -----Original Message-----
> From: owner-freebsd-emulation@freebsd.org [mailto:owner-freebsd-
> emulation@freebsd.org] On Behalf Of Kevin Oberman
> Sent: Saturday, December 22, 2018 11:19 AM
> To: freebsd-emulation@freebsd.org
> Subject: Re: Instant crash starting VBox on 12.0-Stable
> 
> On Wed, Dec 19, 2018 at 10:26 PM Kevin Oberman <rkoberman@gmail.com>
> wrote:
> 
> > After updating my system to 12 and re-installing all ports, the system
is
> > panicing when I try to run VirtualBox. There have been several bugs
> opened
> > where VBox crashes the system instantly when started. Not the virtual
> > system, but the GUI to start (or manage) virtual systems.
> >
> > I have two slightly different crashes, one failing from vboxnetadp.ko
and
> > the other crashing in ifindex_alloc in if.c called from vboxnetadp.ko.
In
> > both cases, the panic was triggered in vboxNetAdpOsCreate.
> >
> > I'll admit that I was surprised to see these happen even before any VM
was
> > started or touched.
> >
> > With possibly three tickets on this, I see no responses to any of them.
I
> > will add my report of one of them. They really should be merged, though,
> > and I am not sure which one will be the final one. I do have both full
> > dumps and can make them available.
> >
> > I really need to resolve this rather soon or fall back to 11.2. Even
> > though I have backups, it will be quite  pain!\
> >
> 
> I have confirmed that the problem exists prior to the branch of 12-STABLE.
> 
> Can anyone confirm running VirtualBox on head after 11.0-Release? Moving
> back in time in SVN is tricky, and, in this case, sometimes requires
> rolling back ports. Any aid in narrowing the failure window would help.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkoberman@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> _______________________________________________
> freebsd-emulation@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> To unsubscribe, send any mail to "freebsd-emulation-
> unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?006b01d49a2a$666e8510$334b8f30$>