Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Apr 2013 13:43:52 -0400
From:      Mark Johnston <markjdb@gmail.com>
To:        Glen Barber <gjb@FreeBSD.org>
Cc:        Viren Shah <virenshah@gmail.com>, freebsd-current@freebsd.org
Subject:   Re: Virtualbox addition in FreeBSD -current guest OS?
Message-ID:  <20130426174352.GA33054@gloom.sandvine.com>
In-Reply-To: <20130426150735.GG1617@glenbarber.us>
References:  <CAJa23VM-YNhifaWULzeT_meh0bPjE8aqeRgMfZaG0mfmHjfFeQ@mail.gmail.com> <20130426144955.GF1617@glenbarber.us> <20130426150210.GA29463@gloom.sandvine.com> <20130426150735.GG1617@glenbarber.us>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 26, 2013 at 11:07:35AM -0400, Glen Barber wrote:
> On Fri, Apr 26, 2013 at 11:02:10AM -0400, Mark Johnston wrote:
> > On Fri, Apr 26, 2013 at 10:49:55AM -0400, Glen Barber wrote:
> > > On Fri, Apr 26, 2013 at 10:45:19AM -0400, Viren Shah wrote:
> > > > I was having problems compiling the virtualbox guest additions  on a FBSD
> > > > -current  (Apr 23 20:30 EDT) system. I changed all the VM_OBJECT_LOCKs to
> > > > VM_OBJECT_WLOCKs (and same for the UNLOCKS) and added rwlock.h to the
> > > > includes. That enabled it to compile but I'm having problems getting X
> > > > started (it just hangs) using those vbox modules for xorg. Log msg (see
> > > > attached) says "failed to initialize VirtualBox device (rc=-102)"
> > > > 
> > > > Anyone having recently compiled the vbox ose-additions on a -current system
> > > > and had it work? I'm just trying to figure out if this is a
> > > > -current-related issue or a vbox related one.
> > > > 
> > > 
> > > This was fixed months ago, I think.  Is your ports tree updated?
> > 
> > As far as the compilation issue goes, the virtualbox-ose-kmod port is
> > indeed fixed but virtualbox-ose-additions is still broken on current
> > with the latest ports tree.
> 
> *sigh*...  Is this broken "again" or broken "still" ?

Looks like the latter based on the port's revision history. It was just
never fixed when the lock changed to a rwlock.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130426174352.GA33054>