Bug 21475 - The virtualbox start but impossible to start guests
Summary: The virtualbox start but impossible to start guests
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-09 00:58 CEST by Jan Pihlgren
Modified: 2017-08-14 22:51 CEST (History)
3 users (show)

See Also:
Source RPM: virtualbox 5.1.26, vboxadditions-kernel-4.9.40-desktop-1-mga6 5.1.26 and so on
CVE:
Status comment:


Attachments
Picture of errormessage when trying to start VirtualBox's guest (40.64 KB, image/png)
2017-08-09 01:05 CEST, Jan Pihlgren
Details

Description Jan Pihlgren 2017-08-09 00:58:56 CEST
Description of problem:
After I had updated VirtualBox it is possible to start VirtualBox but it is impossible to start guests.
Error messages:
Misslyckades med att öppna en session för den virtuella maskinen Mageia 6.

The virtual machine 'Mageia 6' has terminated unexpectedly during startup with exit code 1 (0x1).

Resultatkod: NS_ERROR_FAILURE (0x80004005)
Komponent: MachineWrap
Gränssnitt: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}



Version-Release number of selected component (if applicable):
virtualbox 5.1.26,

How reproducible:


Steps to Reproduce:
1. Start VirtualBox
2. Try to star a guest
3.

Conclussion:
Before this problem I couldn't start VMware Vorkstation after upgrade to MGA6.
After this update of VirtualBox I can't use VirtualBox
So this is very serius problem for me.
Comment 1 Jan Pihlgren 2017-08-09 01:05:13 CEST
Created attachment 9576 [details]
Picture of errormessage when trying to start VirtualBox's guest

Picture of errormessage
Comment 2 Frédéric "LpSolit" Buclin 2017-08-09 01:20:36 CEST
What's your output of: rpm -qa | grep virtualbox

Do you have virtualbox-kernel-4.9.40-desktop-1.mga6-5.1.26-1.mga6 installed?
Comment 3 Jan Pihlgren 2017-08-09 05:20:41 CEST
Yes, I have virtualbox-kernel-4.9.40-desktop-1.mga6-5.1.26-1.mga6 installed.
rpm -qa | grep virtualbox
Result:
virtualbox-doc-5.1.26-1.mga6
virtualbox-kernel-4.4.59-desktop-1.mga5-5.1.22-1.mga5
virtualbox-kernel-4.4.36-desktop-2.mga5-5.1.10-2.1.mga5
virtualbox-kernel-4.4.22-desktop-1.mga5-5.1.2-6.mga5
virtualbox-kernel-4.4.65-desktop-1.mga5-5.1.22-2.mga5
virtualbox-kernel-3.19.8-desktop-3.mga5-5.0.2-2.mga5
virtualbox-kernel-4.4.39-desktop-1.mga5-5.1.10-3.1.mga5
virtualbox-kernel-4.4.50-desktop-2.mga5-5.1.18-1.mga5
virtualbox-kernel-4.4.74-desktop-1.mga5-5.1.22-7.mga5
virtualbox-kernel-4.4.59-server-1.mga5-5.1.22-1.mga5
virtualbox-kernel-4.4.68-desktop-1.mga5-5.1.22-3.mga5
virtualbox-kernel-4.4.32-desktop-1.mga5-5.1.10-1.1.mga5
virtualbox-kernel-4.4.30-desktop-2.mga5-5.1.2-10.mga5
virtualbox-kernel-desktop-latest-5.1.26-1.mga6
virtualbox-guest-additions-5.1.26-1.mga6
virtualbox-kernel-4.1.8-desktop-1.mga5-5.0.8-1.mga5
virtualbox-kernel-server-latest-5.1.26-1.mga6
virtualbox-kernel-4.1.15-desktop-1.mga5-5.0.12-1.mga5
virtualbox-kernel-4.4.32-server-1.mga5-5.1.10-1.1.mga5
virtualbox-kernel-4.4.50-server-2.mga5-5.1.18-1.mga5
virtualbox-kernel-4.1.12-desktop-1.mga5-5.0.8-2.mga5
virtualbox-kernel-4.4.36-server-2.mga5-5.1.10-2.1.mga5
virtualbox-kernel-4.4.74-server-1.mga5-5.1.22-7.mga5
virtualbox-kernel-4.4.39-server-1.mga5-5.1.10-3.1.mga5
virtualbox-kernel-4.4.68-server-1.mga5-5.1.22-3.mga5
virtualbox-kernel-4.4.65-server-1.mga5-5.1.22-2.mga5
virtualbox-kernel-4.1.15-desktop-2.mga5-5.0.16-3.mga5
virtualbox-kernel-4.4.16-desktop-1.mga5-5.1.2-2.mga5
virtualbox-5.1.26-1.mga6
virtualbox-kernel-4.9.35-server-1.mga6-5.1.22-20.mga6
virtualbox-kernel-4.9.40-desktop-1.mga6-5.1.26-1.mga6
virtualbox-kernel-4.4.26-desktop-1.mga5-5.1.2-8.mga5
virtualbox-kernel-4.4.55-server-1.mga5-5.1.18-2.mga5
virtualbox-kernel-4.4.55-desktop-1.mga5-5.1.18-2.mga5
virtualbox-kernel-4.1.13-desktop-2.mga5-5.0.10-1.mga5
virtualbox-kernel-4.9.35-desktop-1.mga6-5.1.22-20.mga6
virtualbox-kernel-4.9.40-server-1.mga6-5.1.26-1.mga6
virtualbox-kernel-4.4.13-desktop-1.mga5-5.1.2-1.mga5
Comment 4 James Kerr 2017-08-09 08:53:43 CEST
What is the result of executing:

uname -a

and, as root:

dkms status -m virtualbox

CC: (none) => jim

Comment 5 Jan Pihlgren 2017-08-09 10:05:05 CEST
[root@Humlan jan]# uname -a
Linux Humlan.localdomain 4.4.74-desktop-1.mga5 #1 SMP Mon Jun 26 07:50:58 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[root@Humlan jan]# 


[root@Humlan jan]# dkms status -m virtualbox
virtualbox, 5.1.10-1.1.mga5, 4.4.39-desktop-1.mga5, x86_64: installed-binary from 4.4.39-desktop-1.mga5
virtualbox, 5.1.18-1.mga5, 4.4.55-desktop-1.mga5, x86_64: installed-binary from 4.4.55-desktop-1.mga5
virtualbox, 5.1.10-1.1.mga5, 4.4.32-server-1.mga5, x86_64: installed-binary from 4.4.32-server-1.mga5
virtualbox, 5.0.8-1.mga5, 4.1.8-desktop-1.mga5, x86_64: installed-binary from 4.1.8-desktop-1.mga5
virtualbox, 5.1.22-1.mga5, 4.4.65-desktop-1.mga5, x86_64: installed-binary from 4.4.65-desktop-1.mga5
virtualbox, 5.1.2-1.mga5, 4.4.13-desktop-1.mga5, x86_64: installed-binary from 4.4.13-desktop-1.mga5
virtualbox, 5.1.18-1.mga5, 4.4.50-desktop-2.mga5, x86_64: installed-binary from 4.4.50-desktop-2.mga5
virtualbox, 5.1.18-1.mga5, 4.4.50-server-2.mga5, x86_64: installed-binary from 4.4.50-server-2.mga5
virtualbox, 5.1.2-1.mga5, 4.4.22-desktop-1.mga5, x86_64: installed-binary from 4.4.22-desktop-1.mga5
virtualbox, 5.1.2-1.mga5, 4.4.16-desktop-1.mga5, x86_64: installed-binary from 4.4.16-desktop-1.mga5
virtualbox, 5.0.8-1.mga5, 4.1.12-desktop-1.mga5, x86_64: installed-binary from 4.1.12-desktop-1.mga5
virtualbox, 5.1.10-1.1.mga5, 4.4.39-server-1.mga5, x86_64: installed-binary from 4.4.39-server-1.mga5
virtualbox, 5.1.22-1.mga5, 4.4.59-server-1.mga5, x86_64: installed-binary from 4.4.59-server-1.mga5
virtualbox, 5.1.26-1.mga6, 4.9.40-server-1.mga6, x86_64: installed-binary from 4.9.40-server-1.mga6
virtualbox, 5.0.2-2.mga5, 3.19.8-desktop-3.mga5, x86_64: installed-binary from 3.19.8-desktop-3.mga5
virtualbox, 5.0.16-1.mga5, 4.1.15-desktop-2.mga5, x86_64: installed-binary from 4.1.15-desktop-2.mga5
virtualbox, 5.0.10-1.mga5, 4.1.13-desktop-2.mga5, x86_64: installed-binary from 4.1.13-desktop-2.mga5
virtualbox, 5.1.18-1.mga5, 4.4.55-server-1.mga5, x86_64: installed-binary from 4.4.55-server-1.mga5
virtualbox, 5.1.22-1.mga5, 4.4.65-server-1.mga5, x86_64: installed-binary from 4.4.65-server-1.mga5
virtualbox, 5.1.2-1.mga5, 4.4.26-desktop-1.mga5, x86_64: installed-binary from 4.4.26-desktop-1.mga5
virtualbox, 5.0.12-1.mga5, 4.1.15-desktop-1.mga5, x86_64: installed-binary from 4.1.15-desktop-1.mga5
virtualbox, 5.1.22-1.mga5, 4.4.74-desktop-1.mga5, x86_64: installed-binary from 4.4.74-desktop-1.mga5
virtualbox, 5.1.22-1.mga5, 4.4.68-desktop-1.mga5, x86_64: installed-binary from 4.4.68-desktop-1.mga5
virtualbox, 5.1.22-1.mga6, 4.9.35-desktop-1.mga6, x86_64: installed-binary from 4.9.35-desktop-1.mga6
virtualbox, 5.1.2-1.mga5, 4.4.30-desktop-2.mga5, x86_64: installed-binary from 4.4.30-desktop-2.mga5
virtualbox, 5.1.22-1.mga5, 4.4.68-server-1.mga5, x86_64: installed-binary from 4.4.68-server-1.mga5
virtualbox, 5.1.10-1.1.mga5, 4.4.32-desktop-1.mga5, x86_64: installed-binary from 4.4.32-desktop-1.mga5
virtualbox, 5.1.10-1.1.mga5, 4.4.36-desktop-2.mga5, x86_64: installed-binary from 4.4.36-desktop-2.mga5
virtualbox, 5.1.26-1.mga6, 4.9.40-desktop-1.mga6, x86_64: installed-binary from 4.9.40-desktop-1.mga6
virtualbox, 5.1.22-1.mga5, 4.4.59-desktop-1.mga5, x86_64: installed-binary from 4.4.59-desktop-1.mga5
virtualbox, 5.1.22-1.mga6, 4.9.35-server-1.mga6, x86_64: installed-binary from 4.9.35-server-1.mga6
virtualbox, 5.1.10-1.1.mga5, 4.4.36-server-2.mga5, x86_64: installed-binary from 4.4.36-server-2.mga5
virtualbox, 5.1.22-1.mga5, 4.4.74-server-1.mga5, x86_64: installed-binary from 4.4.74-server-1.mga5
[root@Humlan jan]#
Comment 6 James Kerr 2017-08-09 11:07:32 CEST
You are running kernel 4.4.74-desktop but the only modules you have installed for virtualbox-5.1.26 are:

virtualbox, 5.1.26-1.mga6, 4.9.40-server-1.mga6, x86_64: installed-binary from 4.9.40-server-1.mga6

virtualbox, 5.1.26-1.mga6, 4.9.40-desktop-1.mga6, x86_64: installed-binary from 4.9.40-desktop-1.mga6

You need to boot to either 4.9.40-desktop or 4.9.40-server



You have a great many kernels installed. Do you really need them all? It's unusual to have both the desktop and server flavours installed in the same system.
Comment 7 Frédéric "LpSolit" Buclin 2017-08-09 12:44:05 CEST
If you are running Mageia 6, you should uninstall all mga5-related packages too. They are now useless. And James is right, you don't need both server and desktop packages.
Comment 8 Jan Pihlgren 2017-08-09 16:48:17 CEST
(In reply to James Kerr from comment #6)
> You are running kernel 4.4.74-desktop but the only modules you have
> installed for virtualbox-5.1.26 are:
> 
> virtualbox, 5.1.26-1.mga6, 4.9.40-server-1.mga6, x86_64: installed-binary
> from 4.9.40-server-1.mga6
> 
> virtualbox, 5.1.26-1.mga6, 4.9.40-desktop-1.mga6, x86_64: installed-binary
> from 4.9.40-desktop-1.mga6
> 
> You need to boot to either 4.9.40-desktop or 4.9.40-server
> 
> 
> 
> You have a great many kernels installed. Do you really need them all? It's
> unusual to have both the desktop and server flavours installed in the same
> system.

I cant't use kernel-4.9.40. My computer will not start at kernel-4.9.40.
Comment 9 Thomas Backlund 2017-08-09 17:20:12 CEST
If you want to use new virtualbox with old kernel, you need to install dkms-virtualbox and the kernel-devel package matching your running kernel, in this case kernel-desktop-devel-4.4.74-1.mga5

Have you filed a bug regarding 4.9.40 not working ? does 4.9.35 work ?

CC: (none) => tmb

Comment 10 Jan Pihlgren 2017-08-09 18:21:12 CEST
Have you filed a bug regarding 4.9.40 not working ?
No
 does 4.9.35 work ?
No

Reason: As long kernel 4.4.74-desktop-1.mga5 works I have been waiting for updates. Earlier I had same problem wich was solved with new update.
Comment 11 Frédéric "LpSolit" Buclin 2017-08-09 18:29:32 CEST
duplicate of bug 20086?
Comment 12 Thomas Backlund 2017-08-09 18:38:37 CEST
(In reply to Frédéric Buclin from comment #11)
> duplicate of bug 20086?

nope, this is simply a missing matching kernel module for older kernel, and the way to fix is in comment 9
Comment 13 Thomas Backlund 2017-08-09 18:40:48 CEST
(In reply to Jan Pihlgren from comment #10)
> Have you filed a bug regarding 4.9.40 not working ?
> No
>  does 4.9.35 work ?
> No
> 
> Reason: As long kernel 4.4.74-desktop-1.mga5 works I have been waiting for
> updates. Earlier I had same problem wich was solved with new update.

Ok, so it might never get fixed then depending on the bug ...
Well, whatever makes you happy :)
Comment 14 Jan Pihlgren 2017-08-10 05:58:07 CEST
"dkms-virtualbox"
Installing dkms-virtualbox 5.1.26 1.mga6 did it!
Thanks Thomas!
Comment 15 Marja Van Waes 2017-08-14 21:43:33 CEST
@ Thomas (tmb),

Can this bug be closed, now that Jan is happy again?

(I haven't used vbox enough to understand the report)

CC: (none) => marja11

Comment 16 Thomas Backlund 2017-08-14 22:51:23 CEST
Yep

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.