Need help installing VirtualBox under 13.1

I’m having problems getting VBox to run after upgrading to openSUSE 13.1.
The machines involved are an older 32 bit Toshiba Satellite and a new HP
Envy H8 desktop. Both were running VBox under 12.3. The lappy is marginal
for VMs but it struggles along, the HP (Core I7, 12GB ram) hardly notices
the load.

I decided to try the repo packages. I’ve been just going to virtualbox.org
and installing their packages but thought I’d give the repos a try as it
simplifies updates. Yast presents the first problem.

Both systems are running the desktop kernel but Yast wants to install the
default kernel when I select “virtualbox” to install. I did determine that
I can get it kernel dependency straight by specifically selecting the kmp-
desktop host module but either way results in the familiar “you need to run
/etc/init.d/vboxdrv” message when I try to start. Of course, that just tells
me it won’t run because the module is pre-compiled… Dead end.

If I let Yast install the default kernel then boot to that kernel, I get
slightly further but as soon as the actual virtual machine tries to open I
get a bunch of configuration errors and the process aborts even trying to
create a whole new VM.

I sure could use some help from someone who has VBox running under 13.1.

Is it just me or has 13.1 been a real PITA to get running smoothly? Here,
it’s been one pissant issue after another.


Will Honea

Will Honea wrote:
> I’m having problems getting VBox to run after upgrading to openSUSE 13.1.
> The machines involved are an older 32 bit Toshiba Satellite and a new HP
> Envy H8 desktop. Both were running VBox under 12.3. The lappy is marginal
> for VMs but it struggles along, the HP (Core I7, 12GB ram) hardly notices
> the load.
>
> I decided to try the repo packages. I’ve been just going to virtualbox.org
> and installing their packages but thought I’d give the repos a try as it
> simplifies updates. Yast presents the first problem.
>
> Both systems are running the desktop kernel but Yast wants to install the
> default kernel when I select “virtualbox” to install. I did determine that
> I can get it kernel dependency straight by specifically selecting the kmp-
> desktop host module but either way results in the familiar “you need to run
> /etc/init.d/vboxdrv” message when I try to start. Of course, that just tells
> me it won’t run because the module is pre-compiled… Dead end.
>
> If I let Yast install the default kernel then boot to that kernel, I get
> slightly further but as soon as the actual virtual machine tries to open I
> get a bunch of configuration errors and the process aborts even trying to
> create a whole new VM.
>
> I sure could use some help from someone who has VBox running under 13.1.
>
> Is it just me or has 13.1 been a real PITA to get running smoothly? Here,
> it’s been one pissant issue after another.
>
Installed vbox qt from the virtual box repo yesterday on 13.1 GNOME YaST
did correctly choose “virtualbox-host-kmp-desktop”

Welcome relief as it did try to install “virtualbox-host-kmp-default”
and “kernel-default” on 12.3

Next added myself(user) to vboxusers in YAST==>User… and restart machine

VBOX does work very well on 13.1.On another note GNOME-boxes also works
well on 13.1


GNOME 3.10.1
openSUSE 13.1 (Bottle) (x86_64) 64-bit
Kernel Linux 3.11.6-4-desktop

You can only install virtualbox from openSUSE-Repo or Virtualbox from Oracle. Not both on the same time.

For Virtualbox from Oracle you need:
Kernel-devel, kernel-source, make and gcc.

Therefore please post:

zypper se -si kernel vbox virtual make gcc

Sauerland wrote:

> You can only install virtualbox from openSUSE-Repo or Virtualbox from
> Oracle. Not both on the same time.
>
> For Virtualbox from Oracle you need:
> Kernel-devel, kernel-source, make and gcc.
>
> Therefore please post:
>
> Code:
> --------------------
> zypper se -si kernel vbox virtual make gcc
> --------------------
>

Bingo! Cruft left over from past “adventures”. I was working from the
assumption that Yast would actually remove all the stuff left over from as
far back as 11.4 - but there is some really old junk left over as I have
basically just been updating these machines since I started with version
9.xx and updating release-to-release.

Removing the VBox 4.3 from virtualbox.org left files that apparently
confused the process. I keep a clean basic install just for such situations
and VBox installs/runs fine there with the existing virtual drives so I
guess it time to do some serious house cleaning using that as a model.

Thanks


Will Honea

On 2013-12-01 21:21, Will Honea wrote:
> Bingo! Cruft left over from past “adventures”. I was working from the
> assumption that Yast would actually remove all the stuff left over from as
> far back as 11.4 - but there is some really old junk left over as I have
> basically just been updating these machines since I started with version
> 9.xx and updating release-to-release.

Run this query:


rpm -q -a --queryformat "%{INSTALLTIME};%{INSTALLTIME:day}; \
%{BUILDTIME:day}; %{NAME};%{VERSION}-%-7{RELEASE};%{arch}; \
%{VENDOR};%{PACKAGER};%{DISTRIBUTION};%{DISTTAG}
" \
| sort | cut --fields="2-" --delimiter=\; \
| tee rpmlist.csv | less -S

(for importing to spreadsheet)

or

rpm -q -a --queryformat "%{INSTALLTIME}	%{INSTALLTIME:day} \
%{BUILDTIME:day} %-30{NAME}	%15{VERSION}-%-7{RELEASE}	%{arch} \
%25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}
" \
| sort | cut --fields="2-" | tee rpmlist | less -S

It prints a list of all installed packages, sorted by date. One of the
fields is the distributions they came with, so that you can then go to
yast to erase or upgrade them manually.

I do that as a part of the tasks just after a system upgrade.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

Carlos E. R. wrote:

> Run this query:
>
>


> rpm -q -a --queryformat "%{INSTALLTIME};%{INSTALLTIME:day}; \
> %{BUILDTIME:day}; %{NAME};%{VERSION}-%-7{RELEASE};%{arch}; \
> %{VENDOR};%{PACKAGER};%{DISTRIBUTION};%{DISTTAG}
" \
> | sort | cut --fields="2-" --delimiter=\; \
> | tee rpmlist.csv | less -S
>
> (for importing to spreadsheet)
>
> or
>
> rpm -q -a --queryformat "%{INSTALLTIME}	%{INSTALLTIME:day} \
> %{BUILDTIME:day} %-30{NAME}	%15{VERSION}-%-7{RELEASE}	%{arch} \
> %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}
" \
> | sort | cut --fields="2-" | tee rpmlist | less -S
> 

>
>
> It prints a list of all installed packages, sorted by date. One of the
> fields is the distributions they came with, so that you can then go to
> yast to erase or upgrade them manually.
>
>
> I do that as a part of the tasks just after a system upgrade.
>

Thanks, Carlos. I was just getting up the energy to cobble up a script to
do this with a database to compair the different versions when you point out
a MUCH simpler way all ready and waiting!

(later) WOW! unbeleivable how much garbage has accumulated in just a few
years!


Will Honea

On 2013-12-01 22:19, Will Honea wrote:
> Carlos E. R. wrote:

>> I do that as a part of the tasks just after a system upgrade.
>>
>
> Thanks, Carlos. I was just getting up the energy to cobble up a script to
> do this with a database to compair the different versions when you point out
> a MUCH simpler way all ready and waiting!

:slight_smile:

It took me sometime to arrive at that concoction :slight_smile:

Previously I just click-clicked my way in yast, looking at all the
packages one by one. Red coloured ones are easy to spot, but they are
not the only ones.

> (later) WOW! unbeleivable how much garbage has accumulated in just a few
> years!

I know…

Have a look at this (unfinished) wiki page - most of the issues are
documented there:

http://en.opensuse.org/SDB:Offline_upgrade


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

Carlos E. R. wrote:

> It took me sometime to arrive at that concoction :slight_smile:
>
> Previously I just click-clicked my way in yast, looking at all the
> packages one by one. Red coloured ones are easy to spot, but they are
> not the only ones.
>

I got in a hurry and forgot to mention that the command runs MUCH better if
you omit the “;” delimiters you used in the format specs. At least on 12.3,
bash barfed on those but the problem was obvious and a lot quicker to fix
than figuring out the statement myself :wink:

Thanks again.


Will Honea

On 2013-12-02 05:43, Will Honea wrote:
> Carlos E. R. wrote:
>
>> It took me sometime to arrive at that concoction :slight_smile:
>>
>> Previously I just click-clicked my way in yast, looking at all the
>> packages one by one. Red coloured ones are easy to spot, but they are
>> not the only ones.
>>
>
> I got in a hurry and forgot to mention that the command runs MUCH better if
> you omit the “;” delimiters you used in the format specs. At least on 12.3,
> bash barfed on those but the problem was obvious and a lot quicker to fix
> than figuring out the statement myself :wink:

Notice that I posted two versions, one with the colons and one without,
using tabs and spaces instead. The version with colons is not for visual
inspection, but to produce a .csv file with can be imported in a
spreadsheet, with columns properly separated.

For visual inspection you have to use the second version.

:slight_smile:


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

Carlos E. R. wrote:

> Notice that I posted two versions, one with the colons and one without,
> using tabs and spaces instead. The version with colons is not for visual
> inspection, but to produce a .csv file with can be imported in a
> spreadsheet, with columns properly separated.
>
> For visual inspection you have to use the second version.
>

I’ve learned all sorts of interesting trivia these last few days :wink:


Will Honea