Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1693622 - Can not start images in Virtualbox 5.2.24_RPMFusion r128122
Summary: Can not start images in Virtualbox 5.2.24_RPMFusion r128122
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: akmods
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-28 10:58 UTC by Michal Špondr
Modified: 2019-03-28 16:53 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-28 12:35:17 UTC


Attachments (Terms of Use)
akmod-VirtualBox fail log (deleted)
2019-03-28 10:58 UTC, Michal Špondr
no flags Details

Description Michal Špondr 2019-03-28 10:58:40 UTC
Created attachment 1548969 [details]
akmod-VirtualBox fail log

Description of problem:
It is not possible to start any Virtualbox image. Message "Kernel driver not installed (rc=-1908)" appear.
I've tried this first:
# dnf install akmod-VirtualBox kernel-devel-$(uname -r)
followed by running akmods. This failed during building and installing phase.

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


How reproducible:
always


Steps to Reproduce:
1. dnf install akmod-VirtualBox kernel-devel-$(uname -r)
2. akmods

Actual results:
# LC_ALL=C akmods
Checking kmods exist for 5.0.3-200.fc29.x86_64             [  OK  ]
Building and installing VirtualBox-kmod                    [FAILED]
Building rpms failed; see /var/cache/akmods/VirtualBox/5.2.24-1-for-5.0.3-200.fc29.x86_64.failed.log for details


Expected results:
akmods should work and thus Virtualbox should be able to start images.

Additional info:
Attached akmod-VirtualBox fail log contains akmods fail log.

Comment 1 leigh scott 2019-03-28 12:35:17 UTC
The vbox code needs fixing for kernel-5.0.0.

https://bugzilla.rpmfusion.org/show_bug.cgi?id=5202

Comment 2 Sergio Monteiro Basto 2019-03-28 16:53:52 UTC
Thanks for the report problems with Virtualbox_RPMFusion version (Virtualbox 5.2.24_RPMFusion) please report in rpmfusion Buzilla [1]

A new version of Vbox is on updates-testing, anyway don't update kernel to new kernel (kernel-5.0.4-200.fc29) will break again, due [2] for that you need new updates of VirtualBox-kmod ( 6.0.4-4 ) 


[1]
https://bugzilla.rpmfusion.org/enter_bug.cgi?product=Fedora&component=VirtualBox

[2]
https://bugzilla.redhat.com/show_bug.cgi?id=1689750


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