VirtualBox

Opened 6 years ago

Closed 6 years ago

#18104 closed defect (invalid)

Impossible de lancer une machine virtuelle après upgrade vers Ubuntu 18.04.1 -> configuration problem

Reported by: Mhady Owned by:
Component: other Version: VirtualBox 5.2.20
Keywords: Vboxdrv ne se lance pas Cc:
Guest type: Linux Host type: Linux

Description

Bonjour tout le monde suis nouveau ici. J'ai vraiment un problème avec le kernel de VirtualBox. Depuis mon upgrade vers Ubuntu 18.04.1 mon virtualbox ne lance plus les machines virtuelles. J'ai réinstallé fatigués(avec les dépôts de ubuntu et les dépôts de Oracle) mais ça marche toujours pas.

voici le message quand je lance une machine virtuelle:

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/sbin/vboxconfig'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. 

voici un resultat après réinstallation

vboxdrv:
Running module version sanity check.
Error! Module version 5.2.10_Ubuntu for vboxdrv.ko
is not newer than what is already found in kernel 4.15.0-38-generic (5.2.20).
You may override by specifying --force.

vboxnetadp.ko:
Running module version sanity check.

Good news! Module version 5.2.10_Ubuntu for vboxnetadp.ko
exactly matches what is already found in kernel 4.15.0-38-generic.
DKMS will not replace this module.
You may override by specifying --force.

vboxnetflt.ko:
Running module version sanity check.
Error! Module version 5.2.10_Ubuntu for vboxnetflt.ko
is not newer than what is already found in kernel 4.15.0-38-generic (5.2.20).
You may override by specifying --force.

vboxpci.ko:
Running module version sanity check.
Error! Module version 5.2.10_Ubuntu for vboxpci.ko
is not newer than what is already found in kernel 4.15.0-38-generic (5.2.20).
You may override by specifying --force.

depmod..........

DKMS: install completed.
root@mhady:/home/mhady# /sbin/vboxconfig --force
Bad argument --force
root@mhady:/home/mhady# /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.

J'ai utilisé toute les solutions que j'ai trouvé sur le net pour l'instant. Svp j'ai vraiment besoin d'aide.

Change History (2)

in reply to:  description comment:1 by Socratis, 6 years ago

Replying to Mhady:

J'ai utilisé toute les solutions que j'ai trouvé sur le net pour l'instant. Svp j'ai vraiment besoin d'aide.

  1. The bugtracker is for bugs. For aid/discussion, you should go to the VirtualBox forums, where the issue has been discussed many, many times before. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.
  1. For example, yours is not a bug and someone from the developers has to deal with it and close it as "Invalid".
  1. You have a mix of Oracle (original) and Ubuntu (fork) versions. You can either ask them for help, or completely remove/uninstall/delete/purge their version and install the official version from the Linux Downloads section of VirtualBox.
  1. If that doesn't work, open a new thread in the VirtualBox on Linux Hosts section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.

comment:2 by Michael Thayer, 6 years ago

Resolution: invalid
Status: newclosed
Summary: Impossible de lancer une machine virtuelle après upgrade vers Ubuntu 18.04.1Impossible de lancer une machine virtuelle après upgrade vers Ubuntu 18.04.1 -> configuration problem
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use