Bugzilla Bug 248776

Virtualbox 2.0.6 available at <http://www.virtualbox.org/wiki/Linux_Downloads>.

*** Bug 248920 has been marked as a duplicate of this bug. ***

Created an attachment (id=173532) [details]
virtualbox-bin, changes of ebuild 2.0.4 -> 2.0.6

Created an attachment (id=173534) [details]
kernel module source

simply need to copy virtualbox-module-2.0.4.ebuild to
virtualbox-module-2.0.6.ebuild

ebuilds commited on jokey's overlay[1]

Please report any issue here

Alessio

[1] http://overlays.gentoo.org/dev/jokey

No issue for me. 

(In reply to comment #4)
> ebuilds commited on jokey's overlay[1]
> 
> Please report any issue here
> 
> Alessio
> 
> [1] http://overlays.gentoo.org/dev/jokey
> 

virtualbox-bin / kernel-module / additions (2.0.6) tested and ok on my amd64
machine

bumped virtualbox-bin and virtualbox-modules

(In reply to comment #7)
> bumped virtualbox-bin and virtualbox-modules
> 

This creates a problem for app-emulation/virtualbox-ose users:

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

app-emulation/virtualbox-modules:0

  ('installed', '/', 'app-emulation/virtualbox-modules-2.0.4', 'nomerge')
pulled in by
    @world
    ('installed', '/', 'app-emulation/virtualbox-ose-2.0.4', 'nomerge')

  ('ebuild', '/', 'app-emulation/virtualbox-modules-2.0.6', 'merge') pulled in
by
    @world

(In reply to comment #8)
> (In reply to comment #7)
> > bumped virtualbox-bin and virtualbox-modules
> > 
> 
> This creates a problem for app-emulation/virtualbox-ose users:
> 
[snip]

ebuilds are ok, seems that a dependency (app-emulation/virtualbox-modules)
is currently listed in your world file[1], edit the world file and remove 
that entry, this will solve your problem.

Note: when you have to re-emerge app-emulation/virtualbox-modules, eg: after a
kernel update, remember to use the --oneshot (-1) switch to exclude it from the
world file

[1] /var/lib/portage/world

(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > bumped virtualbox-bin and virtualbox-modules
> > > 
> > 
> > This creates a problem for app-emulation/virtualbox-ose users:
> > 
> [snip]
> 
> ebuilds are ok, seems that a dependency (app-emulation/virtualbox-modules)
> is currently listed in your world file[1], edit the world file and remove 
> that entry, this will solve your problem.
> 
>

Actually, what is required is a version 2.0.6 of virtualbox-ose.
Do you *really* need another bug raised to do that?

Currently a very nasty bug exists on the .run binary distribution of
virtualbox.
On x86_64 with high network load sometimes you may run into the following
assertion:

!!Assertion Failed!!
Expression: i < 4096
Location  :
/home/vbox/tinderbox/2.0-lnx64-rel/src/VBox/Runtime/r3/linux/semevent-linux.cpp(201)
int RTSemEventSignal(RTSEMEVENTINTERNAL*)
iCur=0x1 pThis=0000000001890a60

The VM dies.

I reopened the corresponding ticket in the virtualbox bugtracker:
http://www.virtualbox.org/ticket/616

(In reply to comment #10)
> Actually, what is required is a version 2.0.6 of virtualbox-ose.
> Do you *really* need another bug raised to do that?
> 
no, i/we don't need another (bump virtualbox) bug.
As you can read on comment #4 atm bumped ebuilds are available on jokey's
overlay, sorry for that, but i'm a proxy maintainer, so i don't have write
access to the tree, ebuilds will be commited after a review done by
a developer.

If you can't wait for any reason you can use that ebuilds (eg: via layman)

After installing 2.0.6 from jokey's overlay, my Ubuntu-guest problems went away
- count this as a vote for the working ebuild.

(AMD64 here.)

I see that the 2.1.0 release has appeared.  How is it working so far?

Sorry, for some reason I couldn't find the actual 2.1.0 bug.  I'll follow
progress in bug #251335.  Thanks!

2.1.x is in the tree