Opened 7 years ago
Closed 7 years ago
#17156 closed defect (invalid)
Ubuntu 16.04 as host : Problem at startup, run vboxconfil
Reported by: | 4sStylZ | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.1.28 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
Hi people,
I use a 16.04 Ubuntu (in fact, Elementary OS based on Ubuntu 16.04). I have installed today the AMD64 build and I can start the vm manager. I have created a new WIN10 vm but she don’t start.
The message is this :
There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig
In fact the issue is the same when I launch the command as root.
root@xxx:/home/xxx# /sbin/vboxconfig vboxdrv.sh: Stopping VirtualBox services. vboxdrv.sh: Building VirtualBox kernel modules. 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.
That’s the dmesg result attached on the issue.
Attachments (4)
Change History (7)
by , 7 years ago
by , 7 years ago
Attachment: | failOnVMStart.jpeg added |
---|
by , 7 years ago
Attachment: | failOnVMStart.2.jpeg added |
---|
by , 7 years ago
Attachment: | failOnVMStart.3.jpeg added |
---|
comment:1 by , 7 years ago
May I suggest something? It's usually better and faster, if issues like this one (configuration, question) get first addressed in the VirtualBox forums. 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. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".
So, if you can, please 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 #.
comment:2 by , 7 years ago
Hi,
Ok Socratis.
Considere this issue closed (I don’t know how to close-it).
comment:3 by , 7 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
dmesg.log