Virtualbox help

Just installed and updated 12.3 64bit, I installed gcc/make/kernel-dev. Downloaded and installed newest virtualbox 64bit rpm. Running /etc/init.d/vboxdrv setup fails. The /var/log/vbox-install .log doesn’t help. It looks like Chinese to me. Anyone know what failed?

Makefile:184: Warning: using /usr/src/linux as the source directory of your Linux kernel. If this is not correct, specify KERN_DIR=<directory> and run Make again.
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /usr/src/linux modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (        \
echo >&2;                            \
echo >&2 "  ERROR: Kernel configuration is invalid.";        \
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";    \
echo >&2 ;                            \
/bin/false

The /usr/src dir contains: linux linux-3.7.10-1.1 linux-3.7.10-1.1-obj linux-obj packages vboxhost-4.2.8

Did you install the kernel sources and such? I normally suggest you take the following action:

Open YaST / Software / Software Management - Select the View Button on the top left and pick Patterns. Now, you will see several Patterns listed and you want to select:

   Development

[X] Base Development
[X] Linux Kernel Development
[X] C/C++ Development

Then Press the Accept button on the bottom right and allow these applications to install. I have been able to install and run VirtualBox 4.2.8 (Downloaded directly from Oracle) in openSUSE 12.3 without issue after following my own advice.

Thank You,

I installed gcc/make/kernel-dev/kernel-syms. This has been enough in past releases. I will try your suggestion.

Please post:

zypper se -si kernel gcc make

You don’t say why you installed the developer tools along with VBox. I have 12.3 running within VBox, but on a OSX host. The developer tools are only required if you want to build the guest additions manually. You may need to add the openSUSE Virtualization repo so you can install the latest virtualbox-guest-kmp-desktop packages to work with the 12.3 kernel.

Additionally, you can’t compile anything without the kernel-source package.

The dev tools are need on openSUSE for virtualbox to compile it’s drivers on first run. I installed


[X] Base Development [X] Linux Kernel Development [X] C/C++ Development

with no change. It still complains about the kernel directory.

zypper se -si kernel gcc make
Loading repository data...
Reading installed packages...

S | Name                           | Type    | Version              | Arch   | Repository       
--+--------------------------------+---------+----------------------+--------+------------------
i | automake                       | package | 1.12.1-3.1.1         | noarch | openSUSE-12.3-Oss
i | gcc                            | package | 4.7-7.1.1            | x86_64 | openSUSE-12.3-Oss
i | gcc-c++                        | package | 4.7-7.1.1            | x86_64 | openSUSE-12.3-Oss
i | gcc-info                       | package | 4.7-7.1.1            | x86_64 | openSUSE-12.3-Oss
i | gcc47                          | package | 4.7.2_20130108-2.1.6 | x86_64 | openSUSE-12.3-Oss
i | gcc47-c++                      | package | 4.7.2_20130108-2.1.6 | x86_64 | openSUSE-12.3-Oss
i | gcc47-info                     | package | 4.7.2_20130108-2.1.6 | noarch | openSUSE-12.3-Oss
i | kernel-default-devel           | package | 3.7.10-1.1.1         | x86_64 | openSUSE-12.3-Oss
i | kernel-desktop                 | package | 3.7.9-1.1.2          | x86_64 | (System Packages)
i | kernel-desktop-devel           | package | 3.7.10-1.1.1         | x86_64 | openSUSE-12.3-Oss
i | kernel-devel                   | package | 3.7.10-1.1.1         | noarch | openSUSE-12.3-Oss
i | kernel-firmware                | package | 20130114git-1.2.1    | noarch | openSUSE-12.3-Oss
i | kernel-source                  | package | 3.7.10-1.1.1         | noarch | openSUSE-12.3-Oss
i | kernel-syms                    | package | 3.7.10-1.1.1         | x86_64 | openSUSE-12.3-Oss
i | kernel-xen-devel               | package | 3.7.10-1.1.1         | x86_64 | openSUSE-12.3-Oss
i | libgcc_s1                      | package | 4.7.2_20130108-2.1.6 | x86_64 | openSUSE-12.3-Oss
i | libgcc_s1-32bit                | package | 4.7.2_20130108-2.1.6 | x86_64 | openSUSE-12.3-Oss
i | make                           | package | 3.82-154.1.1         | x86_64 | openSUSE-12.3-Oss
i | makeinfo                       | package | 4.13a-32.1.1         | x86_64 | openSUSE-12.3-Oss
i | patterns-openSUSE-devel_kernel | package | 12.3-7.10.1          | x86_64 | openSUSE-12.3-Oss

Not if you have the following packages installed:

virtualbox-guest-kmp-desktop
virtualbox-guest-tools
virtualbox-guest-x11

Edit: I just thought of something. Where did your version of VBox come from?

It is straight from Oracle. I always assumed those packages were for the ose version.

Try as root:

zypper in -f kernel-desktop

because kernel-mismatch:

i | kernel-desktop | package | 3.7.9-1.1.2 | x86_64 | (System Packages)
i | kernel-desktop-devel | package | 3.7.10-1.1.1 | x86_64 | openSUSE-12.3-Oss

I also prefer the Virtualbox-Version from the Virtualbox-Homepage.
But I have insert the Repo from the Download-Site.

Bingo! Good catch. I didn’t notice the different versions. It is working great now. Thanks.

The problem about this is:

In openSUSE 12.3 RC multiversion for kernel is enabled in /etc/zypp/zypp.conf by default.
In older Versions of openSUSE it is disabled by default.

Therefor your desktop-kernel was not updated by

zypper up

If I disable this, will “zypper up” always pull in the newest kernel?

If I disable this, will "zypper up" always pull in the newest kernel? 

Yes, but if the new Kernel is broken, you cannot go into your SUSE.
Up to this you can run the old Kernel displayed in the Grub2.

I would wait until openSUSE 12.3 is released.

Newer kernel should still be installed using “zypper up” in this case; what may happen is that -devel packages get updated, so old kernel does not more have matching -devel package. I do not remember which packages are subject to multiversioning by default.

If new kernel was not installed, something went wrong.

zypper up” will only update to a package from the same vendor as the installed package. This means that it will not cross between openSUSE ( e.g. distribution, factory, and openSUSE Build Service – e.g. repositories/Kernel:/). To change vendors use “zypper dup --from”. But unless you are updating multiple installations, it is generally easier to use YaST for kernel updates.

From man zypper


       update (up) [options] [packagename] ...
              Update installed packages with newer versions, where possible.

              This command will not update packages which would require change of package vendor unless the vendor is
              specified  in  /etc/zypp/vendors.d, or which would require manual resolution of problems with dependen-
              cies. Such non-installable updates will then be listed in separate section of the summary as "The  fol-
              lowing package updates will NOT be installed:".

              To  update individual packages, specify one or more package names. You can use the '*' and '?' wildcard
              characters in the package names to specify multiple packages matching the pattern.

I didn’t run “zypper dup”, so it was probably using factory kernel, and 12.3 kernel-dev. I will wait and do a “zypper dup” after release day.

On 03/11/2013 12:36 PM, 67GTA wrote:
>
> I didn’t run “zypper dup”, so it was probably using factory kernel, and
> 12.3 kernel-dev. I will wait and do a “zypper dup” after release day.

If your repos are set to the 12.3 URLs, then you can zypper dup now. After RC2
comes GM (for Gold Master). That was set last Friday, and is the “final”
material for the release. The time between GM and the release is time for the
mirrors to catch up in time for the formal announcement.

Yeah, the 12.3 factory repo started throwing errors when updating. All is good.

Did you get it work? I followed your problem to try and fix mine but got nowhere :