[opensuse-factory] factory/M7 and VirtualBox ?

newer
[opensuse-factory] M7: How do I...

older
[opensuse-factory] dbus and amarok

Per Jessen

4 Jun 2010 4 Jun '10

07:19

Yesterday I did a 'zypper up' to get my test system on the latest and greatest - and now I can no longer run VirtualBox. Of course it could be plain operator error, but I had no problems running VirtualBox only two days ago. I run it the usual way - get vboxdrv loaded, chgrp on /dev/vboxdrv, then start ./VirtualBox from the build directory (I haven't installed it permanently). I get the standard error "kernel driver not accessible". Has anyone else noticed any issue wrt VirtualBox ? -- Per Jessen, Zürich (13.5°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Show replies by date

Andrea Florio

4 Jun 4 Jun

08:17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Il 04/06/2010 09:19, Per Jessen ha scritto:

...

Yesterday I did a 'zypper up' to get my test system on the latest and greatest - and now I can no longer run VirtualBox. Of course it could be plain operator error, but I had no problems running VirtualBox only two days ago. I run it the usual way - get vboxdrv loaded, chgrp on /dev/vboxdrv, then start ./VirtualBox from the build directory (I haven't installed it permanently). I get the standard error "kernel driver not accessible". Has anyone else noticed any issue wrt VirtualBox ?

if you upgraded the kernel, most probably you just need to rebuild the drivers (kernel modules) Andrea - -- - ------------------------------------------ Andrea Florio QSI International School of Brindisi Sys Admin CISCO CCNA Certified openSUSE-Education Administrator openSUSE Official Member (anubisg1) Email: andrea@opensuse.org Packman Packaging Team Email: andrea@links2linux.de Web: http://packman.links2linux.org/ Cell: +39-328-7365667 - ------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkwItpwACgkQyCZT87TFPujtGwCgwN4YgBOBxJxtGuFA03HVEWcP H30AmwWn4cCl0h0N5FH/7PARaaWh6DQM =2+gg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Per Jessen

08:27

Andrea Florio wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Il 04/06/2010 09:19, Per Jessen ha scritto:

...
Yesterday I did a 'zypper up' to get my test system on the latest and greatest - and now I can no longer run VirtualBox. Of course it could be plain operator error, but I had no problems running VirtualBox only two days ago. I run it the usual way - get vboxdrv loaded, chgrp on /dev/vboxdrv, then start ./VirtualBox from the build directory (I haven't installed it permanently). I get the standard error "kernel driver not accessible". Has anyone else noticed any issue wrt VirtualBox ?

if you upgraded the kernel, most probably you just need to rebuild the drivers (kernel modules)

Sure. Been there, done that - anyway, I've just now found the problem. The /dev/vboxdrv device did not have group rw permissions. I have not had to add those previously, so _something_ changed, but what? -- Per Jessen, Zürich (14.6°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Michal Seben

13:28

On Friday 04 June 2010 08:27:09 Per Jessen wrote:

...

Andrea Florio wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Il 04/06/2010 09:19, Per Jessen ha scritto:

...
Yesterday I did a 'zypper up' to get my test system on the latest and what was your previous system ? And what is your tested vbox version ? greatest - and now I can no longer run VirtualBox. Of course it could be plain operator error, but I had no problems running VirtualBox only two days ago. I run it the usual way - get vboxdrv loaded, chgrp on /dev/vboxdrv, then start ./VirtualBox from the build directory (I haven't installed do you have installed also virtualbox-ose-kmp package from factory/11.3 bs repo on your new system ? it permanently). I get the standard error "kernel driver not accessible". Has anyone else noticed any issue wrt VirtualBox ?

if you upgraded the kernel, most probably you just need to rebuild the drivers (kernel modules)

Sure. Been there, done that - anyway, I've just now found the problem. The /dev/vboxdrv device did not have group rw permissions. I have not had to add those previously, so _something_ changed, but what?

I dropped vboxusers group (on /dev/vboxdrv) year ago but in this case you are affected only if you have virtualbox-ose-kmp installed and your previous system was <11.2 : #Thu May 7 17:36:37 CEST 2009 - mseben@suse.cz # #- fixed ose-init-scripts.diff : don't use vboxusers group for # /dev/vboxdrv (bnc#429725) ... hm .. why didn't you install virtualbox-ose directly using zypper from build service repo ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Per Jessen

5 Jun 5 Jun

07:26

Michal Seben wrote:

...

On Friday 04 June 2010 08:27:09 Per Jessen wrote:

...
Andrea Florio wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Il 04/06/2010 09:19, Per Jessen ha scritto:

...
Yesterday I did a 'zypper up' to get my test system on the latest and what was your previous system ? And what is your tested vbox version ?

11.3 M7 - vbox 3.1.8, now 3.2.2.

...

...
...
...
greatest - and now I can no longer run VirtualBox. Of course it could be plain operator error, but I had no problems running VirtualBox only two days ago. I run it the usual way - get vboxdrv loaded, chgrp on /dev/vboxdrv, then start ./VirtualBox from the build directory (I haven't installed

do you have installed also virtualbox-ose-kmp package from factory/11.3 bs repo on your new system ?

No, I don't have any virtualbox pakcages installed.

...

...
...
...
it permanently). I get the standard error "kernel driver not accessible". Has anyone else noticed any issue wrt VirtualBox ?

if you upgraded the kernel, most probably you just need to rebuild the drivers (kernel modules)

Sure. Been there, done that - anyway, I've just now found the problem. The /dev/vboxdrv device did not have group rw permissions. I have not had to add those previously, so _something_ changed, but what?

I dropped vboxusers group (on /dev/vboxdrv) year ago but in this case you are affected only if you have virtualbox-ose-kmp installed and your previous system was <11.2 : #Thu May 7 17:36:37 CEST 2009 - mseben@suse.cz # #- fixed ose-init-scripts.diff : don't use vboxusers group for # /dev/vboxdrv (bnc#429725) ... hm .. why didn't you install virtualbox-ose directly using zypper from build service repo ?

No particular reason. I just downloaded and built Vbox like I always have. -- Per Jessen, Zürich (16.4°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Sid Boyce

4 Jun 4 Jun

12:21

On 04/06/10 09:17, Andrea Florio wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Il 04/06/2010 09:19, Per Jessen ha scritto:

...
Yesterday I did a 'zypper up' to get my test system on the latest and greatest - and now I can no longer run VirtualBox. Of course it could be plain operator error, but I had no problems running VirtualBox only two days ago. I run it the usual way - get vboxdrv loaded, chgrp on /dev/vboxdrv, then start ./VirtualBox from the build directory (I haven't installed it permanently). I get the standard error "kernel driver not accessible". Has anyone else noticed any issue wrt VirtualBox ?

if you upgraded the kernel, most probably you just need to rebuild the drivers (kernel modules)

Andrea

- --

"/etc/init.d/vboxdrv setup" does it for me every time. I use the Sun version because of USB support - latest is VirtualBox-3.2-3.2.0_61806_openSUSE112-1.x86_64.rpm for 64-bit, upgraded with "rpm -Uvh" and when I build a new kerenel or an updated kernel comes along, "setup" is all I do. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Vahis

19:27

On 06/04/2010 03:21 PM, Sid Boyce wrote:

...

"/etc/init.d/vboxdrv setup" does it for me every time. I use the Sun version because of USB support - latest is VirtualBox-3.2-3.2.0_61806_openSUSE112-1.x86_64.rpm for 64-bit,

A bit OT, but this caused some confusion in my system: I hadn't noticed that my version is not quite up-to-date, mine (in 11.2) is 3.1.8_61349_openSUSE111-1 So I too tried the normal way:

...

upgraded with "rpm -Uvh" and when I build a new kerenel or an updated kernel comes along, "setup" is all I do.

but I got Failed dependencies: libpython2.5.so.1.0()(64bit) is needed by VirtualBox-3.2-3.2.2_62298_openSUSE110-1.x86_64 That's strange my libpython is 2.6.2-6.4.1 What am I missing? Vahis -- http://waxborg.servepics.com openSUSE 11.2 (x86_64) 2.6.31.12-0.2-default 21:48pm up 31 days 2:00, 11 users, load average: 1.57, 1.28, 1.26 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Michal Šebeň

20:45

New subject: [opensuse-factory] factory/M7 and VirtualBox ?

...

On 06/04/2010 03:21 PM, Sid Boyce wrote:

...
"/etc/init.d/vboxdrv setup" does it for me every time. I use the Sun version because of USB support - latest is VirtualBox-3.2-3.2.0_61806_openSUSE112-1.x86_64.rpm for 64-bit,

A bit OT, but this caused some confusion in my system: I hadn't noticed that my version is not quite up-to-date, mine (in 11.2) is 3.1.8_61349_openSUSE111-1

So I too tried the normal way:

...
upgraded with "rpm -Uvh" and when I build a new kerenel or an updated kernel comes along, "setup" is all I do.

but I got Failed dependencies: libpython2.5.so.1.0()(64bit) is needed by VirtualBox-3.2-3.2.2_62298_openSUSE110-1.x86_64

That's strange my libpython is 2.6.2-6.4.1 check what provides you python package rpm -q -provides libpython2_6-1_0 ... libpython2.6.so.1.0()(64bit) ... and check what need your virtualbox : rpm -q --requires -p ./VirtualBox-3.2-3.2.2_62298_openSUSE110-1.x86_64.rpm | grep python

On Fri, Jun 4, 2010 at 9:27 PM, Vahis wrote: libpython2.5.so.1.0()(64bit) and libpython2.6.so.1.0()(64bit) != libpython2.5.so.1.0()(64bit)

...

What am I missing?

if I understand correctly you are trying to install VirtualBox-3.2-3.2.2_62298_*openSUSE110*-1.x86_64 package builded for 11.0 and you have openSUSE 11.2 ... so you should update to http://download.virtualbox.org/virtualbox/3.2.2/VirtualBox-3.2-3.2.2_62298_o... package (yes this package should be used also for 11.2) ---- but I would suggest you to add vbox puel repo for 11.2 (see links in http://www.virtualbox.org/wiki/Linux_Downloads bottom part) and use zypper : zypper ar http://download.virtualbox.org/virtualbox/rpm/opensuse/11.2/virtualbox.repo zypper dup -r <reponum> (mayby you will need also remove your old vbox package) ---- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Vahis

5 Jun 5 Jun

03:39

New subject: [opensuse-factory] factory/M7 and VirtualBox ?

On 06/04/2010 11:45 PM, Michal Šebeň wrote:

...

...
On 06/04/2010 03:21 PM, Sid Boyce wrote:

...
"/etc/init.d/vboxdrv setup" does it for me every time. I use the Sun version because of USB support - latest is VirtualBox-3.2-3.2.0_61806_openSUSE112-1.x86_64.rpm for 64-bit,

A bit OT, but this caused some confusion in my system: I hadn't noticed that my version is not quite up-to-date, mine (in 11.2) is 3.1.8_61349_openSUSE111-1

So I too tried the normal way:

...
upgraded with "rpm -Uvh" and when I build a new kerenel or an updated kernel comes along, "setup" is all I do.

but I got Failed dependencies: libpython2.5.so.1.0()(64bit) is needed by VirtualBox-3.2-3.2.2_62298_openSUSE110-1.x86_64

That's strange my libpython is 2.6.2-6.4.1 check what provides you python package rpm -q -provides libpython2_6-1_0 ... libpython2.6.so.1.0()(64bit) ... and check what need your virtualbox : rpm -q --requires -p ./VirtualBox-3.2-3.2.2_62298_openSUSE110-1.x86_64.rpm | grep python

On Fri, Jun 4, 2010 at 9:27 PM, Vahis wrote: libpython2.5.so.1.0()(64bit)

and libpython2.6.so.1.0()(64bit) != libpython2.5.so.1.0()(64bit)

...
What am I missing?

if I understand correctly you are trying to install VirtualBox-3.2-3.2.2_62298_*openSUSE110*-1.x86_64 package builded for 11.0 and you have openSUSE 11.2 ... so you should update to http://download.virtualbox.org/virtualbox/3.2.2/VirtualBox-3.2-3.2.2_62298_o... package (yes this package should be used also for 11.2)

That seems to have been the reason. Picked wrong package...

...

---- but I would suggest you to add vbox puel repo for 11.2 (see links in http://www.virtualbox.org/wiki/Linux_Downloads bottom part) and use zypper : zypper ar http://download.virtualbox.org/virtualbox/rpm/opensuse/11.2/virtualbox.repo zypper dup -r <reponum> (mayby you will need also remove your old vbox package)

...

----

The funny thing is that I had that repo added all the time. It was not showing the new version. Anyway, I installed the correct version with rpm. The kernel module got created automagically as before: (And yes, the old VBox version needed to be removed, there were conflicts) ------------------------------------- No precompiled module for this kernel found -- trying to build one. Messages emitted during module compilation will be logged to /var/log/vbox-install.log. Success! ------------------------------------- Thanks :) Vahis -- http://waxborg.servepics.com openSUSE 11.2 (x86_64) 2.6.31.12-0.2-default 06:35am up 32 days 10:47, 12 users, load average: 0.18, 0.12, 0.10 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

5076

Age (days ago)

5077

Last active (days ago)

List overview

Download

8 comments

6 participants

participants (6)

Andrea Florio
Michal Seben
Michal Šebeň
Per Jessen
Sid Boyce
Vahis