Virtual box not working

Aggiungo che dopo aver tolto e installato nuovamente virtualbox e fatto reboot l’errore diventa

ma gli altri comandi descritti sopra danno sempre stesso errore

La versione del kernel-devel è la stessa precisa di quella del kernel?

Sì, questo è essenziale. Può entrambi o inviare l’output completo (come codice) di:

# rpm -qa | grep kernel

Che risponderà a questo e ci dica anche quale versione di intestazioni del kernel hai.

Modifica: sto traduendo dall’inglese all’italiano con il traduttore S3. Spero di sapere meglio italiano che io!

Alangea abbiamo bisogno di questo per sapere quale versione di VirtualBox hai, ma anche dobbiamo sapere se hai ‘dkms-virtualbox’ installato per andare avanti con questo.

I have the same problem.
[root@localhost Production]# rpm -qa | grep virtualbox

Uno di voi deve presentare un report di bug il più presto possibile. Inserisci informazioni e dettagli sufficienti per qualcun altro per capire il problema e cercare di risolverlo. Non dimenticare [this.] (Bug report tool for OpenMandriva Lx)

One of you needs to file a bug report as soon as possible. Please include enough information and detail for someone else to understand the problem and try to solve it. Don’t forget this.

I’vgot IDENTICAL diagnostics for the SAME commands typed by alblpanig.

root@localhost alangea]# /usr/lib64/virtualbox/ setup Stopping VirtualBox services. Building VirtualBox kernel modules. failed: Look at /var/log/vbox-install.log to find out what went wrong.

[root@localhost alangea]# more /var/log/vbox-install.log
/usr/lib64/virtualbox/ riga 392: /usr/lib64/virtualbox/src/vboxhost/build_in_tmp: File o directory non esistente

[root@localhost alangea]# rpm -qa | grep virtualbox

[root@localhost alangea]# rpm -qa | grep kernel

I cannot update the kernel-headers package because of a conflict with the installed one. The latter is not unistallable, because of a lot of dependencies: I don’t know how to do it.

Lord have mercy. This should have been mentioned at the very beginning. That package is way to old for Y’all to be using it. That package is so old developers removed it from repository. Open Konsole, become root and run:

# urpme kernel-headers

Write down (copy and paste) any other packages removed. Now run this:

# urpmi kernel-release-headers kernel-release-desktop-devel kernel-release-desktop-devel-latest

That should readd any packages that were removed. But to be safe check and see if there are any packages in your removed list that weren’t installed with that command and use ‘urpmi’ in Konsole to install them back. See, that just isn’t that hard to do.

Now reboot and when you do remove any and all virtualbox and dkms packages. Now reinstall them.

Let us know what happens. Ask if you have any questions or problems. But you really, really need to do this.

Post edit: If removing dkms removes any other kernel modules then you want to reinstall them with the new kernel-release-headers. Just follow same procedures above. Copy and paste somewhere all removed packages and then reinstall them.

Installation (50.8 KB)

[root@localhost alangea]# urpmi kernel-release-headers kernel-release-desktop-devel kernel-release-desktop-devel-latest >report.log

You have to remove the other package first.

Edit: Do it exactly like I posted. You first must:

# urpme kernel-headers

but some of the packages are just kernel packages !
If I try to unistall the conflicting kernel-headers package, it also remove the kernel itself !

Again do it exactly like I said. The packages being removed are kernel devel packages not the kernel itself. urpmi will not let you remove a working kernel.

If you continue to use such an outdated kernel headers package you are asking for problems with anything requiring a kernel module.

No it doesn’t. Do you know how many times I have done this? urpmi will not remove a working kernel. The packages being removed are kernel devel packages only. Read the error message.

Edit: If nothing else post like you did above the complete output when you run:

# urpme -v kernel-headers

or even safer:

# urpme -v kernel-headers --test

Seems OK now_

root@localhost alangea]# !rpm
rpm -qa | grep kernel

Thank you very much. Now I have still that problem with VirtualBox. Have I to unistalla dkms-virtualbox, reinstalla and reboot ?

uname -a riporta

Linux albertolx3-pc 4.11.3-desktop-2omv #1 SMP PREEMPT Wed May 31 21:33:09 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux



come richiesto

rpm -qa | grep kernel

this is my bug report
omv-bug-report.log.xz (72,0 KB)

  1. To be safe run this in Konsole as root:

# grub2-mkconfig -o /boot/grub2/grub.cfg

All that does is rebuild your grub boot menu. I prefer to do this after installing kernel headers and kernel devel packages.

  1. Then reboot.

  2. Now remove virtualbox and dkms-virtualbox packages.

# urpme -v virtualbox dkms-virtualbox


# urpmi -v virtualbox dkms-virtualbox

copy and paste the output of this and save it to a file in case there is a problem or if the same problem persists. ‘dkms-virtualbox’ builds the virtualbox kernel modules. The error reported indicates that may not have been done correctly before. So we are hoping the up to date kernel headers corrects this.

  1. Then reboot again and check virtualbox however you normally do.

Um, no it isn’t. That is a xz compressed bug report log. It is something that is to be attached to a bug report.

And you are showing an up to date kernel headers package:

so if have had this all along and are still seeing this problem then I’m afraid a bug report is necessary.

In attach you can see the kernel update and the virtualbox uninstall and re-install bue after the reboot nothing change
vbox.txt (42,8 KB)

1 Like