Virtualbox, OSE, Non OSE, extension pack questions and so on...

[melodie]

Hi,

Starting the non OSE version, I get a message stating that I can't use USB2 unless I install extension pack.
(id error : ExtPackNoEHSCI)

This is here:
http://www.oracle.com/technetwork/server-storage/virtualbox/downloads/index.html#extpack

I wonder if I would have better install this, ask for a package for it, or just install the OSE version ?

And also I wonder about the use of some of the related packages we have ?

=> task-virtualbox 3.1.4 : do we still need it ?

=> dkms 3.2.12 : the 2 packages (is that what is needed so to get vbox with the vbox additions working fine ?)

=> x11 drivers mouse and video : version number 3.2.12, works fine in virtualbox non OSE 4.0.4, Ok for me.

Now what are the possibilities ? I suppose with the extension pack for 4.0.4 (404 error ? ) we can have USB 2 controller working, which could be good to run a usb printer from within a virtual Windows when this printer has no driver available for linux.

And with the OSE version as we do have vbox addition, we can manager to share the mouse, and a folder between a host and a guest.

Please let me know if there is something missing in my statement, and if there are possibilities I didn't see, as well as telling me if the extension pack could be in the repos provided a request would be done, or if it should be installed independantly from the distribution.

Thanks,
Mélodie

[GermanTux]

Any of the packages in the repos are for the OSE version.  Just install 'get-virtualbox' from the repos, then run the script from the start menu.  It will take care of the rest. 

You can install the Virtualbox extensions on top of the non OSE version if you wish, but it is not mandatory.  They are only really needed if you want USB support from host->guest. 

[Old-Polack]

The extension pack for 4.0.4 has to be downloaded from The VirtualBox site; it can't be added to the repository for licensing reasons.

The instructions for installing the extension pack leave something to be desired, as they don't work as advertised if one already has existing VMs present. To install the extension pack in that case, first download it to a known location, then open VirtualBox.

Click on File --> Preferences --> Extensions, then on the far right, click the icon with the red/orange triangle



Navigate to the directory with the extension pack, in the pop up window, click on the extension pack and click the Open button.



A PUEL license agreement window will open.



Scroll to the bottom, to activate the I Agree button.



A new window will open in which to enter the root password.

Once done, the installation will proceed, and you will be presented with this final window.



Click the OK button, and enjoy.  

[melodie]

Old-Polack, thank you very much !!! You are the best !

I will try it this evening. Do you happen to also know if that brings in the equivalent of the Virtualbox-guest-additions, allowing to configure a shared directory between the host and the guest ?

Thank you very much again !

[kjpetrie]

Some of us like to use OSE on principle if we don't need the USB. Now the USB has become an extension, even for the non-OSE, it's unclear whether there is now a distinction between OSE and non-OSE for the basic application. I am too busy at present to experiment with packaging the OSE and then seeing whether the extension will work with it. If so, it would seem silly to keep getvirtualbox if everyone can use the OSE packaged and just add the extension if needed.

For the next couple of months I am simply too busy to package it and test, but I would hate to see the OSE disappear from the repo, as I am really committed to open source and don't want to see Oracle dropping it claiming lack of demand.

[Old-Polack]

Old-Polack, thank you very much !!! You are the best !

I will try it this evening. Do you happen to also know if that brings in the equivalent of the Virtualbox-guest-additions, allowing to configure a shared directory between the host and the guest ?

Thank you very much again !

If there is an existing version of guest additions present, they will work to some extent. Somewhere in the starting of a VM, a message may appear stating that the guest additions being run are an older version and the new version should be installed.

Installing the new version is the same as it's always been.



On the Windows VM I use for my scanner, the process is as follows;

[melodie]

Hi Kjpetrie,

I was not talking about OSE disappearing : I was just talking about the task package which is outdated. The rest is of a different version, that's all. 3.1.4 VS 3.2.12

[melodie]

If there is an existing version of guest additions present, they will work to some extent. Somewhere in the starting of a VM, a message may appear stating that the guest additions being run are an older version and the new version should be installed.

Therefore I should have at least the older version installed ?  (the OSE, in our repos is the only available)

[menotu]

Hi melodie,

I believe Oracle and/or outside developers may create more Extension Packs allowing further customization and enhancements.
 
Hopefully some interesting and worthwhile ones will come along............

[melodie]

Hi menotu,

I just decided to give the OSE edition a try. I am installing all  related packages.

[melodie]

]]=+°@!!![{#@@@ !!!! Machines !!

Figure out, PUEL version puts the user stuff in ~/Virtualbox VMs and OSE version puts them in .VirtualBox, with a different tree directory in each one !

Very stupid, isn't it ?

I don't even know how to make them match !

[Old-Polack]

]]=+°@!!![{#@@@ !!!! Machines !!

Figure out, PUEL version puts the user stuff in ~/Virtualbox VMs and OSE version puts them in .VirtualBox, with a different tree directory in each one !

Very stupid, isn't it ?

I don't even know how to make them match !

Don't know what is going on with that. My settings for all versions have always been in ~/.VirtualBox whether OSE or PUEL. Just checked again, having recently done the 4.0.4 upgrade and all is still the same; only ~/.VirtualBox present.

[Texstar]

Some of us like to use OSE on principle if we don't need the USB. Now the USB has become an extension, even for the non-OSE, it's unclear whether there is now a distinction between OSE and non-OSE for the basic application. I am too busy at present to experiment with packaging the OSE and then seeing whether the extension will work with it. If so, it would seem silly to keep getvirtualbox if everyone can use the OSE packaged and just add the extension if needed.

For the next couple of months I am simply too busy to package it and test, but I would hate to see the OSE disappear from the repo, as I am really committed to open source and don't want to see Oracle dropping it claiming lack of demand.

Virtualbox 4.0.4 without the expansion pack is now considered the OSE version. To make it the PUEL version you would download and install the expansion pack that enables USB support.

[Texstar]

]]=+°@!!![{#@@@ !!!! Machines !!

Figure out, PUEL version puts the user stuff in ~/Virtualbox VMs and OSE version puts them in .VirtualBox, with a different tree directory in each one !

Very stupid, isn't it ?

I don't even know how to make them match !

Don't know what is going on with that. My settings for all versions have always been in ~/.VirtualBox whether OSE or PUEL. Just checked again, having recently done the 4.0.4 upgrade and all is still the same; only ~/.VirtualBox present.

On my new system without any previous vdi's and using Virtualbox 4.0.4, any new guest OS's get installed into /home/texstar/VirtualBox VMs/

[menotu]

/home/texstar/VirtualBox VMs/

Ditto - the VirtualBox VMs folder.............