VirtualBox 2.1.2 has been released here are ebuilds for virtualbox-bin and virtualbox-modules. Reproducible: Always Steps to Reproduce: 1. get new ebuild 2. 'digest' 3. emerge virtualbox-bin && emerge virtualbox-modules Actual Results: VirtualBox 2.1.2 will be installed
Created attachment 179621 [details] ebuild for virtualbox-bin-2.1.2
Created attachment 179622 [details] ebuild for virtualbox-modules-2.1.2
Wasn't much to it other than changing the version numbers and the 'PV'.
ah - you lucky man ;) a lot of users (me included) are getting the following error: NS_ERROR_ABORT (0x80004004) I also get this when installing it manually any workaround for that ?
Hmm, are you getting this with the OSE version or bin version? If it's the OSE one I plan on putting that on my other machine later today, I will post my results with that and let you know.
it's the bin-version which shows these symptoms thanks
Hi all, virtualbox 2.1.2 are already available on jokey's overlay[1], i bumped all the ebuild on 01/23/09, please use (or test) the ebuild on overlay. Thanks [1] http://overlays.gentoo.org/dev/jokey
Please create EAPI 2 ebuilds to overcome the fetch restrictions. (Actually, EAPI 2 isn't really necessary - just depends on a higher portage version, because in newer stable portage versions, portage finally uses the "-O" parameter of wget)
(In reply to comment #4) > ah - you lucky man ;) > > a lot of users (me included) are getting the following error: > > NS_ERROR_ABORT (0x80004004) > > > I also get this when installing it manually > > any workaround for that ? > This is caused by not modprobing vboxnetflt. Run modprobe vboxnetflt as root. Jokey's ebuilds work fine for me.
(In reply to comment #8) > Please create EAPI 2 ebuilds to overcome the fetch restrictions. (Actually, > EAPI 2 isn't really necessary - just depends on a higher portage version, > because in newer stable portage versions, portage finally uses the "-O" > parameter of wget) > Converted all the ebuilds to EAPI=2 (only 1.6.6 was excluded)
(In reply to comment #9) Actually, for me it was hal not running...(/etc/init.d/hald start) > (In reply to comment #4) > > ah - you lucky man ;) > > > > a lot of users (me included) are getting the following error: > > > > NS_ERROR_ABORT (0x80004004) > > > > > > I also get this when installing it manually > > > > any workaround for that ? > > > > This is caused by not modprobing vboxnetflt. Run modprobe vboxnetflt as root. > Jokey's ebuilds work fine for me. >
I also had NS_ERROR_ABORT (0x80004004). Looks like it happens only when dbus is started, but hal not. So either you start hal or stop dbus. Than VBox works fine. Dbus-monitor [without hal] shows this: signal sender=org.freedesktop.DBus -> dest=(null destination) path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string ":1.2" string "" string ":1.2" signal sender=org.freedesktop.DBus -> dest=(null destination) path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string ":1.2" string ":1.2" string "" I don't have hal [don't like it, don't need it], so for now I'm stuck with 2.1.0 or have to stop dbus before using VB.
I'm getting a major performance downgrade after upgrading to this version. It appears others are as well: http://www.virtualbox.org/ticket/3172 Also, I accidentally commented in the duplicate ticket instead of this one: virtualbox-ose has a dependence on libcap: Checking for libcap library: libcap not found at -lcap or libcap headers not found This causes emerge to abort during the configure step. After emerging libcap, installation of virtualbox-ose proceeded correctly.
(In reply to comment #13) [..] > This causes emerge to abort during the configure step. After emerging libcap, > installation of virtualbox-ose proceeded correctly. > well added back the dependency on sys-libs/libcap, upstream added extra code to to prevent the dependency on libcap but the check in the configure script is still there (see changset 15871). So "virtually" is possible to build without it (but i wasn't able to). Thanks for pointing this out.
(In reply to comment #11) > (In reply to comment #9) > > Actually, for me it was hal not running...(/etc/init.d/hald start) > that worked for me ! there seem to be 2 ways to solve this (both involve dbus and/or hald) 1) dbus and hald disabled (often not an option) 2) dbus and hald running thanks ! :)
(In reply to comment #12) [cut] > I don't have hal [don't like it, don't need it], so for now I'm stuck with > 2.1.0 or have to stop dbus before using VB. > (In reply to comment #15) [cut] > there seem to be 2 ways to solve this (both involve dbus and/or hald) > > 1) dbus and hald disabled (often not an option) > > 2) dbus and hald running Not sure if this can help both but.. if you are using virtualbox-ose you can disable the hal/dbus support at build time via the hal USE flag (USE="-hal"), indeed this workaround is not working for the -bin edition.
The performance issues have been fixed in 2.1.4 we just need a tarball for virtualbox-modules-2.1.4 to get the new version.
Duplicate of bug #251335 ?
virtualbox-2.1.4 version bump http://bugs.gentoo.org/show_bug.cgi?id=259688
(In reply to comment #17) [..] (In reply to comment #19) [..] Hi, version 2.1.4 was bumped and is available on jokey's overlay[1] [1] http://overlays.gentoo.org/dev/jokey
I'm using jokey's overlay and I'm getting: >>> Downloading 'http://download.virtualbox.org/virtualbox/2.1.4/VirtualBox-2.1.4-OSE.tar.bz2' --2009-03-02 17:57:19-- http://download.virtualbox.org/virtualbox/2.1.4/VirtualBox-2.1.4-OSE.tar.bz2 Resolving download.virtualbox.org... 72.5.124.114 Connecting to download.virtualbox.org|72.5.124.114|:80... connected. HTTP request sent, awaiting response... 302 Moved Temporarily Location: http://dlc-cdn.sun.com/virtualbox/2.1.4/VirtualBox-2.1.4-OSE.tar.bz2 [following] --2009-03-02 17:57:20-- http://dlc-cdn.sun.com/virtualbox/2.1.4/VirtualBox-2.1.4-OSE.tar.bz2 Resolving dlc-cdn.sun.com... 87.248.208.6, 87.248.208.7 Connecting to dlc-cdn.sun.com|87.248.208.6|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://dlc-cdn-rd.sun.com/c1/virtualbox/2.1.4/VirtualBox-2.1.4-OSE.tar.bz2?e=1236016936&h=31e1af0b715c4794a732311dd1079847 [following] --2009-03-02 17:57:20-- http://dlc-cdn-rd.sun.com/c1/virtualbox/2.1.4/VirtualBox-2.1.4-OSE.tar.bz2?e=1236016936&h=31e1af0b715c4794a732311dd1079847 Resolving dlc-cdn-rd.sun.com... 87.248.210.190, 87.248.211.227 Connecting to dlc-cdn-rd.sun.com|87.248.210.190|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 47896348 (46M) [application/x-tar] Saving to: `/usr/portage/distfiles/VirtualBox-2.1.4-OSE.tar.bz2' 100%[===================================================================================================================>] 47,896,348 705K/s in 59s 2009-03-02 17:58:19 (791 KB/s) - `/usr/portage/distfiles/VirtualBox-2.1.4-OSE.tar.bz2' saved [47896348/47896348] ('Filesize does not match recorded size', 47896348L, 47895473) !!! Fetched file: VirtualBox-2.1.4-OSE.tar.bz2 VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 47896348 !!! Expected: 47895473 Has vbox got smaller?
(In reply to comment #21) > I'm using jokey's overlay and I'm getting: [..] as reported on bug 259688 (comment 21, 22, 23) upstream silently updated tarballs and binaries, just updated Manifests and ebuild on jokey's overlay
2.1.4 is in the tree
