VirtualBox 2.0.0 for Linux Release: Major Revision bump Reproducible: Always Steps to Reproduce:
Please do not file 0'day requests. When the maintainer doesn't react within a week, it's early enough to do so.
As Alessio is moving atm, I bet he welcomes any help with this, so feel free to contact him about helping out
Created attachment 164685 [details] app-emulation/virtualbox-bin-2.0.0.ebuild this is the 1.6.4 ebuild updated to 2.0.0 changes: src package name change permissions of VirtualBox VBoxSDL VBoxHeadless to 4711 as requred by the new security system introduced with 2.0.0 only copy virtualbox-modules 1.6.4 to 2.0.0
(In reply to comment #3) > Created an attachment (id=164685) [edit] > app-emulation/virtualbox-bin-2.0.0.ebuild > > this is the 1.6.4 ebuild updated to 2.0.0 > changes: > src package name > change permissions of VirtualBox VBoxSDL VBoxHeadless to 4711 as requred by the > new security system introduced with 2.0.0 > > only copy virtualbox-modules 1.6.4 to 2.0.0 > tks, it can work.
(In reply to comment #3) > change permissions of VirtualBox VBoxSDL VBoxHeadless to 4711 as requred by the > new security system introduced with 2.0.0 > scanelf: rpath_security_checks(): Security problem with DT_RPATH='$ORIGIN' in /var/tmp/portage/app-emulation/virtualbox-bin-2.0.0/image/opt/VirtualBox/VirtualBox with mode set of 4711 scanelf: rpath_security_checks(): Security problem with DT_RPATH='$ORIGIN' in /var/tmp/portage/app-emulation/virtualbox-bin-2.0.0/image/opt/VirtualBox/VBoxSDL with mode set of 4711 scanelf: rpath_security_checks(): Security problem with DT_RPATH='$ORIGIN' in /var/tmp/portage/app-emulation/virtualbox-bin-2.0.0/image/opt/VirtualBox/VBoxHeadless with mode set of 4711
I'm just working on an ebuild for virtualbox-ose and I'm wondering how to get bruce evan's c compiler (bcc).
I have bcc as part of sys-devel/dev86.
Created attachment 164843 [details] app-emulation/virtuabox-ose-2.0.0 simply copy virtualbox-modules-1.6.6 to 2.0.0 reuse needed files from the files directory please test - this is my first larger ebuild, so please be kind ;)
Created attachment 164852 [details] Alternative VirtualBox-ose-2.0.0 ebuild I've created an alternative ebuild based on the virtualbox-ose-1.6.6 ebuild which removes the included tools and uses the system ones as described by bug #232775. The changes are exporting KBUILD_PATH so the modifies .kmk files are used rather than the kBuild defaults and adding a dependency for Qt4.
Created attachment 164854 [details, diff] Updated version of 1.6.6 patch, required by above ebuild
Created attachment 164935 [details] Update to my ebuild above The above ebuild doesn't install usable links for the graphical management tool as they've changed the name of the QT3 version and my previous ebuild didn't build the QT4 version. This version also adds a hardened USE flag so that you're not forced to run VirtualBox as root.
Created attachment 164937 [details] Updated wrapper script to add new name for QT3 GUI Updated wrapper script to add support for VirtualBox3, the new name for the QT3 GUI.
Created attachment 164985 [details] app-emulation/virtuabox-ose-2.0.0 Added John Keeping's src_unpack, including the remove-unused patch. changed the configure part - same effect, less code, making the ebuild a little clearer.
Created attachment 165003 [details] "hybrid" ebuild of the above ones Thanks to John Keeping I hope I did it right using EAPI=1 using my inherits, as they are satisfying using John Keeping's SRC_URI because it's used in all the other vbox ebuilds, too IUSE: just +qt4, not +qt3 as qt4 is newer, keeping python flag; as long as python is not disabled in src_compile, vbox depends on it. DEPEND: splitting into RDEPEND and DEPEND. libXt is not needed, libX11, libXext and probably sdl-ttf are needed, according to configure. keeping glibc, pthread.h is requested in configure and belongs to glibc. alsa and pulseaudio are needed on runtime, keeping them in RDEPEND. actually just yasm-0.6 is needed, using john keeping's 0.6.2 anyway as I assume he had reasons to choose it. pkg_setup problems with gcc-4.3 are still not fixed, my bad. Adding <sys-devel-gcc-4.3 to DEPEND, to keep older versions of the compiler installed, as long as build dependencies are not removed. using John_Keeping's pkg_setup, it's better src_compile no need to subordinate qt3 and qt4 to headless, the configure script handles that internally adopting John Keepings changes to src_install pkg_postinst: infos about how to start Vbox are useful, but bear in mind that vbox can be compiled both with qt3 _and_ qt4. VBoxHeadless also works when not compiled with --build-headless
Actually, I didn't have a reason for >=yasm-0.6.2, my ebuild was just changing the existing 1.6.6 ebuild as little as possible to cover the changes, so if something before that definitely works, I'd recommend changing it, but then I assume whoever originally put that requirement in had a reason for it! You haven't mentioned it explicitly, but I assume you're using my updated virtualbox-ose-wrapper? Probably a good idea to state explicitly which files are needed. Only thing I'd change about your ebuild is that you have two versions of pkg_postinst! Once that's fixed, consider mine deprecated in favour of yours.
Created attachment 165059 [details] app-emulation/virtuabox-ose-2.0.0 you are absolutely right, I have 2 pkg_postinst! I copied yours to modify it but I forgot to remove mine. and, yes, I am using your wrapper script. thanks for the great teamwork, we seem to be done. let's wait for a dev to check the ebuild and put it in the tree. needed files for this ebuild are: virtualbox-ose-wrapper virtualbox-ose-2.0.0-remove-unused.patch
*** Bug 237306 has been marked as a duplicate of this bug. ***
Created attachment 165160 [details] virtualbox-bin-2.0.0.ebuild Fixed the download, now we can fetch the file using the ebuild.
Created attachment 165162 [details] virtualbox-modules-2.0.0.ebuild bumped the version of the kernel module to 2.0.0
please someone deprecate the old files
Created attachment 165166 [details] virtualbox-bin-2.0.0.ebuild Submitting this ebuild, but I'm a ebuild newbie. This ebuild installs the source to compile the kernel module, so we can use the /etc/init.d/vboxdrv script to recompile the kernel module. I'm not sure why there was the original decision to separate the virtualbox-modules package, except to share between virtualbox-bin and -ose Tested on x86. Note: I did not test the headless or web interface.
Hi, sorry for the delay but as Markus said in comment #2 last week i was moving, furthermore the upcoming 2.0.0 release needed a massive rewrite/testing as many changes were introduced. I just committed to jokey's overlay[1] my current work with virtualbox ebuilds feel free to test and report here issues and questions. A brief and incomplete list of Changes (full Changelog in overlay): -- app-emulation/virtualbox-ose: - qt3 support was dropped, upstream moved the main frontend (VirtualBox) to qt4, the old qt3 frontend is deprecated and unmaintained starting with this release. - new prefix, files are now installed under /usr/lib (/usr/lib/virtualbox-ose;/usr/share/virtualbox/ose) it's now possible to customize this. app-emulation/virtualbox-bin: - added support for the new sdk - new wrapper <still in progress> app-emulation/virtualbox-guest-additions: - added VBoxControl command line utility app-emulation/virtualbox-ose-additions: - additions are now installed under /usr/share (/usr/share/virtualbox-ose); x11-drivers/xf86-input-virtualbox: x11-drivers/xf86-video-virtualbox: app-emulation/virtualbox-modules: - Version Bump Notes: -- - Support for GCC 4.3.1 is still missing (OSE) - Problems with http://download.virtualbox.org and wget (reported upstream[2]), many files are donwloaded with a string appended to the original name, due to the redirect implemented to the Sun Download Center. (In reply to comment #5) > scanelf: rpath_security_checks(): Security problem with DT_RPATH='$ORIGIN' in > /var/tmp/portage/app-emulation/virtualbox-bin-2.0.0/image/opt/VirtualBox/VirtualBox > with mode set of 4711 > scanelf: rpath_security_checks(): Security problem with DT_RPATH='$ORIGIN' in > /var/tmp/portage/app-emulation/virtualbox-bin-2.0.0/image/opt/VirtualBox/VBoxSDL > with mode set of 4711 > scanelf: rpath_security_checks(): Security problem with DT_RPATH='$ORIGIN' in > /var/tmp/portage/app-emulation/virtualbox-bin-2.0.0/image/opt/VirtualBox/VBoxHeadless > with mode set of 4711 Due to the new hardened system (binaries start as root and then drop privileges) the so called "starters" are installed suid root, in addition as you reported this binaries (virtualbox-bin only issue) are shipped with an RPATH (RPATH=$ORIGIN), if i'm not wrong ORIGIN could mean "current working directory" and is not secure i'm currently working to fix this issue. (In reply to comment #21) [..] > I'm not sure why there was the original decision to separate the > virtualbox-modules package, except to share between virtualbox-bin and -ose [..] since both the editions (PUEL,OSE) can share the same kernel module, the packages was splitted and mantained (in the last releases upstream started again not releasing it as a separate package), this approach save time and simplify the life for users that want to jump between OSE and PUEL editions, when the kernel driver (vboxdrv) has a bug or simply you switch to a new kernel. (In reply to comment #15) > Actually, I didn't have a reason for >=yasm-0.6.2 [..] starting with this release (dev-lang/yasm-0.6.2) yasm is known to work, in the last releases a modified by upstream yasm-0.6.0 binary was used to build virtualbox. [1] http://overlays.gentoo.org/dev/jokey [2] http://www.virtualbox.org/ticket/2148
Hi, what version of Qt does VB need now? I have qt-4.4.1-r1 installed but VB doesn't want to play well with my theme. It shows to the ugly windows95 one. Thanks, Norberto
please add <sys-devel/gcc-4.1.2 to DEPEND. It's annoying to not be able to do a proper depclean.
oops, I got confused by my gcc-versions. Of course I wanted to say: please add <sys-devel/gcc-4.3.1 do DEPEND.
Hello all. I'm trying to buld virtualbox-bin-2.0.0, using Cristi Magherusan ebuilds of bin and modules. I've placed them to local portage dir. The error I recieve is --------------------8>---------------------------------- TYPE PAX FILE ET_EXEC PemRxS /var/tmp/portage/app-emulation/virtualbox-bin-2.0.0/image//opt/VirtualBox/VirtualBox cp: cannot stat `/usr/local/portage/app-emulation/virtualbox-bin/files/virtualbox-bin-wrapper': No such file or directory * * ERROR: app-emulation/virtualbox-bin-2.0.0 failed. * Call stack: * ebuild.sh, line 49: Called src_install * environment, line 2639: Called die * The specific snippet of code: * newexe "${FILESDIR}/${PN}-wrapper" "VBox.sh" || die; * The die message: * (no error message) --------------------8>---------------------------------- What's this wrapper?
> cp: cannot stat > `/usr/local/portage/app-emulation/virtualbox-bin/files/virtualbox-bin-wrapper': You can get it from /usr/portage/app-emulation/virtualbox-bin/files/ > What's this wrapper? I have no idea, but it works this way. Cristi.
(In reply to comment #27) > > cp: cannot stat > > `/usr/local/portage/app-emulation/virtualbox-bin/files/virtualbox-bin-wrapper': > You can get it from /usr/portage/app-emulation/virtualbox-bin/files/ > > > What's this wrapper? > I have no idea, but it works this way. > > Cristi. > Thx, it did work for me too. But after installation I got error: Could not find VirtualBox installation. Please reinstall. I inspected /usr/bin/VirtaulBox and saw that it points to lrwxrwxrwx 1 0 0 23 2008-09-12 15:43 /usr/bin/VirtualBox -> /opt/VirtualBox/VBox.sh . So there is a string in VBox.sh, that looks like PATH="/usr/bin:/bin:/usr/sbin:/sbin" CONFIG="/etc/vbox/vbox.cfg" if [ ! -r "$CONFIG" ]; then echo "Could not find VirtualBox installation. Please reinstall." exit 1 fi So, this vbox.cfg really does not exist. But anyway, VirtualBox is started with no problems, using full path to /opt/VirtualBox/VirtualBox. I'm not sure, that's a bug, but that's what I got. And one more. I tried to build Virtual-Box ose, and I says emerge -pv virtualbox-ose These are the packages that would be merged, in order: Calculating dependencies \ emerge: there are no ebuilds to satisfy "~app-emulation/virtualbox-ose-additions-2.0.0". (dependency required by "app-emulation/virtualbox-ose-2.0.0" [ebuild]) So, this also has to be handled in some way.
about the 2.0.0 ebuilds in jokey's overlay: virtualbox-ose-2.0.0 compiles fine, GUI starts fine, but running a VM aborts with this log-entry: VBox.log.2:00:48:41.609 REM: failed loading '/usr/lib/virtualbox-ose/VBoxREM2.rel', rc=VERR_FILE_NOT_FOUND I tested -bin and it worked. So I copied VBoxREM2.rel from the -bin installation to the path above, reinstalled -ose, and after setting the right permissions, VMs started again.
Here comes 2.0.2 http://dlc.sun.com/virtualbox/2.0.2/
Also in the public folder, http://download.virtualbox.org/virtualbox/2.0.2/ (In reply to comment #30) > Here comes 2.0.2 > http://dlc.sun.com/virtualbox/2.0.2/ >
(In reply to comment #29) [..] > I tested -bin and it worked. So I copied VBoxREM2.rel from the -bin > installation to the path above, reinstalled -ose, and after setting the right > permissions, VMs started again. Hi thanks for your report, are you using an amd64 or x86 host?
(In reply to comment #30) > Here comes 2.0.2 > http://dlc.sun.com/virtualbox/2.0.2/ > updated ebuilds for the 2.0.2 release are available on jokey's overlay[1], fixed the issue reported by Christian Authmann too (in comment #29), seems to occur only in amd64 hosts. [1] http://overlays.gentoo.org/dev/jokey
(In reply to comment #33) > updated ebuilds for the 2.0.2 release are available on jokey's overlay I tried to install virtualbox-bin from that overlay but cannot find the VirtualBox binary.
hmm. sorry, i was confused by the 'headless' use flag
> fixed the issue reported by Christian Authmann too (in comment #29), > seems to occur only in amd64 hosts. yes, it's an amd64 machine. The 2.0.2 ebuild works. Thank you.
The vboxwebsrv init script finds it's executable in /usr/bin/vboxwebsrv, however it is in /opt/VirtualBox/vboxwebsrv. I'm using jokey's virtualbox-bin-2.0.2 on 64bit. I changed the init script and checked out in my browser, but I only saw an xml file.
(In reply to comment #37) > The vboxwebsrv init script finds it's executable in /usr/bin/vboxwebsrv, > however it is in /opt/VirtualBox/vboxwebsrv. > > I'm using jokey's virtualbox-bin-2.0.2 on 64bit. > thanks for your report, there was a missing symbolic link (i just fixed it). > I changed the init script and checked out in my browser, > but I only saw an xml file. this happens because vboxwebsrv acts as a HTTP server but accepts SOAP connections, so unless you use a client from the samples shipped with virtualboxSDK (USE="sdk" emerge app-emulation/virtualbox-bin ) you need to write a client application, it's not a webapp but a webservice. (more infos in the SDKRef.pdf shipped with the VirtualBox sdk)
Whops, overlooked this, VirtualBox 2.0.2 InCVS meanwhile