Virtualbox on FC22

[Adrian]

Does anyone have Virtualbox working
on FC22 ?

Adrian ... vk4tux

[Joachim Backes]

On 05/09/2015 03:30 PM, Adrian wrote:
> Does anyone have Virtualbox working
> on FC22 ?
>
> Adrian ... vk4tux

I'm running VirtualBox-5.0-5.0.0_BETA3_100143_fedora18-1.x86_64
from virtualbox.org (not that from rpmfusion!)

Joachim Backes

[Sérgio Basto]

On Sáb, 2015-05-09 at 23:30 +1000, Adrian wrote:
> Does anyone have Virtualbox working
> on FC22 ?

yes now we got  on rpmfusion :

VirtualBox-4.3.26-3.fc22.x86_64.rpm

* Mon May 04 2015 Sérgio Basto  - 4.3.26-3
- Added diff_smap_4.patch from https://www.virtualbox.org/ticket/13961 ,
  may fix problems for kernel >= 3.19 , I still need disable 3D to run
plasma 5

( https://forums.virtualbox.org/viewtopic.php?f=6&t=64452&start=15#p32... )

[Adrian]

On 09/05/15 23:38, Sérgio Basto wrote:
> On Sáb, 2015-05-09 at 23:30 +1000, Adrian wrote:
> > Does anyone have Virtualbox working
> > on FC22 ?
>
> yes now we got  on rpmfusion :
>
> VirtualBox-4.3.26-3.fc22.x86_64.rpm
> Mon May 04 2015 Sérgio Basto  - 4.3.26-3
> Added diff_smap_4.patch from https://www.virtualbox.org/ticket/13961 ,
>  may fix problems for kernel >= 3.19 , I still need disable 3D to run
>
> plasma 5
>
> ( https://forums.virtualbox.org/viewtopic.php?f=6&t=64452&start=15#p32... )

Thankyou I am trying this one and get

Result Code:

NS_ERROR_FAILURE (0x80004005)

Component:

Machine

Interface:

IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

when starting a XPvdi

[Adrian]

On 09/05/15 23:47, Adrian wrote:
> Result Code:
>
> NS_ERROR_FAILURE (0x80004005)

Did

Konsole output
/etc/init.d/vboxdrv

get replaced by something in systemd ?

Adrian ... vk4tux

[František Zatloukal]

Hi,
running "sudo /etc/init.d/vboxdrv setup" should help. Command is same even
with systemd.

2015-05-09 16:05 GMT+02:00 Adrian :
> On 09/05/15 23:47, Adrian wrote:
>
> Result Code:
>
> NS_ERROR_FAILURE (0x80004005)
>
> Did
>
> /etc/init.d/vboxdrv
>
> get replaced by something in systemd ?
>
> Adrian ... vk4tux
>
> --
> test mailing list
> [e-mail]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test

[Adrian]

Yes, Below is why I asked the question ;

Konsole output
[root@fedora22desk ~]# /etc/init.d/vboxdrv setup
bash: /etc/init.d/vboxdrv: No such file or directory
[root@fedora22desk ~]#

Konsole output
root@fedora22desk ~]#rpm -qi VirtualBox
Name        : VirtualBox
Version     : 4.3.26
Release     : 3.fc22
Architecture: x86_64
Install Date: Sat 09 May 2015 23:43:00 AEST
Group       : Development/Tools
Size        : 61244411
License     : GPLv2 or (GPLv2 and CDDL)
Signature   : RSA/SHA1, Wed 06 May 2015 20:46:45 AEST, Key ID 
81c9b42397f4d1c1
Source RPM  : VirtualBox-4.3.26-3.fc22.src.rpm
Build Date  : Wed 06 May 2015 20:36:21 AEST
Build Host  : builder02.kwizart.net
Relocations : (not relocatable)
Packager    : kwizart
Vendor      : rpms.kwizart.net
URL         : http://www.virtualbox.org/wiki/VirtualBox
Summary     : A general-purpose full virtualizer for PC hardware
Description :
A general-purpose full virtualizer and emulator for 32-bit and
64-bit x86 based PC-compatible machines.
[root@fedora22desk ~]#

On 10/05/15 00:14, František Zatloukal wrote:
> Hi,
> running "sudo /etc/init.d/vboxdrv setup" should help. Command is same 
> even with systemd.
>
> 2015-05-09 16:05 GMT+02:00 Adrian <[e-mail] 
> >:
> On 09/05/15 23:47, Adrian wrote:
> > Result Code:
> >
> > 	
> >
> > NS_ERROR_FAILURE (0x80004005)
> Did
>
> /etc/init.d/vboxdrv
>
> get replaced by something in systemd ?
>
> Adrian ... vk4tux
>
> --
> test mailing list
> [e-mail] <mailto:[e-mail]>
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
>
>
>
> -- 
> *Best regards / S pozdravem,
>
> František Zatloukal*
> *Web:* frantisek.zatloukalu.eu http://frantisek.zatloukalu.eu

[Sérgio Basto]

On Dom, 2015-05-10 at 00:43 +1000, Adrian wrote:
> Yes, Below is why I asked the question ;
>
> [root@fedora22desk ~]#  /etc/init.d/vboxdrv setup 
> bash: /etc/init.d/vboxdrv: No such file or directory 
> [root@fedora22desk ~]#
>
> root@fedora22desk ~]# rpm -qi VirtualBox 
> Name        : VirtualBox 
> Version     : 4.3.26 
> Release     : 3.fc22 
> Architecture: x86_64 
> Install Date: Sat 09 May 2015 23:43:00 AEST 
> Group       : Development/Tools 
> Size        : 61244411 
> License     : GPLv2 or (GPLv2 and CDDL) 
> Signature   : RSA/SHA1, Wed 06 May 2015 20:46:45 AEST, Key ID
> 81c9b42397f4d1c1 
> Source RPM  : VirtualBox-4.3.26-3.fc22.src.rpm 
> Build Date  : Wed 06 May 2015 20:36:21 AEST 
> Build Host  : builder02.kwizart.net 
> Relocations : (not relocatable) 
> Packager    : kwizart 
> Vendor      : rpms.kwizart.net 
> URL         : http://www.virtualbox.org/wiki/VirtualBox 
> Summary     : A general-purpose full virtualizer for PC hardware 
> Description : 
> A general-purpose full virtualizer and emulator for 32-bit and 
> 64-bit x86 based PC-compatible machines. 
> [root@fedora22desk ~]#

yum install akmod-VirtualBox kernel-devel-$(uname -r)

akmods

systemctl restart systemd-modules-load.service
> On 10/05/15 00:14, František Zatloukal wrote:
> > Hi,
> > running "sudo /etc/init.d/vboxdrv setup" should help. Command is
> > same even with systemd.
> >
> > 2015-05-09 16:05 GMT+02:00 Adrian :
> >     On 09/05/15 23:47, Adrian wrote:
> >
> >     > Result Code: 
> >     > 
> >     > 
> >     > NS_ERROR_FAILURE (0x80004005)
> >     > 
> >     > 
> >     Did
> >
> >     /etc/init.d/vboxdrv
> >
> >
> >     get replaced by something in systemd ? 
> >
> >     Adrian ... vk4tux
> >
> >
> >     --
> >     test mailing list
> >     [e-mail]
> >     To unsubscribe:
> >     https://admin.fedoraproject.org/mailman/listinfo/test
> >
> >
> >
> > -- 
> > Best regards / S pozdravem,
> >
> > František Zatloukal
> > Web: frantisek.zatloukalu.eu
>
> -- 
> test mailing list
> [e-mail]
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test

[Adrian]

On 10/05/15 00:49, Sérgio Basto wrote:
> On Dom, 2015-05-10 at 00:43 +1000, Adrian wrote:
> > Yes, Below is why I asked the question ;
> >
> > [root@fedora22desk ~]#  /etc/init.d/vboxdrv setup
> > bash: /etc/init.d/vboxdrv: No such file or directory
> > [root@fedora22desk ~]#
> >
> > root@fedora22desk ~]# rpm -qi VirtualBox
> > Name        : VirtualBox
> > Version     : 4.3.26
> > Release     : 3.fc22
> > Architecture: x86_64
> > Install Date: Sat 09 May 2015 23:43:00 AEST
> > Group       : Development/Tools
> > Size        : 61244411
> > License     : GPLv2 or (GPLv2 and CDDL)
> > Signature   : RSA/SHA1, Wed 06 May 2015 20:46:45 AEST, Key ID
> > 81c9b42397f4d1c1
> > Source RPM  : VirtualBox-4.3.26-3.fc22.src.rpm
> > Build Date  : Wed 06 May 2015 20:36:21 AEST
> > Build Host  : builder02.kwizart.net
> > Relocations : (not relocatable)
> > Packager    : kwizart
> > Vendor      : rpms.kwizart.net
> > URL         : http://www.virtualbox.org/wiki/VirtualBox
> > Summary     : A general-purpose full virtualizer for PC hardware
> > Description :
> > A general-purpose full virtualizer and emulator for 32-bit and
> > 64-bit x86 based PC-compatible machines.
> > [root@fedora22desk ~]#
>
> yum install akmod-VirtualBox kernel-devel-$(uname -r)
>
> akmods
>
> systemctl restart systemd-modules-load.service

I got

Konsole output
[root@fedora22desk ~]#yum install akmod-VirtualBox kernel-devel-$(uname -r)
Yum command has been deprecated, redirecting to '/usr/bin/dnf install 
akmod-VirtualBox kernel-devel-4.0.1-300.fc22.x86_64'.
See 'man dnf' and 'man yum2dnf' for more information.
To transfer transaction metadata from yum to DNF, run:
'dnf install python-dnf-plugins-extras-migrate && dnf-2 migrate'

Last metadata expiration check performed 1:08:35 ago on Sun May 10 
00:16:35 2015.
Package akmod-VirtualBox-4.3.26-2.fc22.x86_64 is already installed, 
skipping.
Package kernel-devel-4.0.1-300.fc22.x86_64 is already installed, skipping.
Dependencies resolved.
Nothing to do.
Complete!
[root@fedora22desk ~]#akmods
Checking kmods exist for 4.0.1-300.fc22.x86_64             [ OK ]
[root@fedora22desk ~]#
[root@fedora22desk ~]#systemctl restart systemd-modules-load.service
Job for systemd-modules-load.service failed. See "systemctl status 
systemd-modules-load.service" and "journalctl -xe" for detai
ls.
[root@fedora22desk ~]#systemctl status systemd-modules-load.service
●systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; 
static; vendor preset: disabled)
   Active: failed(Result: exit-code) since Sun 2015-05-10 01:25:33 AEST; 
20s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 5599 ExecStart=/usr/lib/systemd/systemd-modules-load 
(code=exited, status=1/FAILURE)
Main PID: 5599 (code=exited, status=1/FAILURE)

May 10 01:25:33 fedora22desk systemd[1]: Starting Load Kernel Modules...
May 10 01:25:33 fedora22desk systemd-modules-load[5599]: Failed to 
insert 'vboxdrv': Exec format error
May 10 01:25:33 fedora22desk systemd-modules-load[5599]: Failed to 
insert 'vboxnetflt': Exec format error
May 10 01:25:33 fedora22desk systemd-modules-load[5599]: Failed to 
insert 'vboxnetadp': Exec format error
May 10 01:25:33 fedora22desk systemd[1]: systemd-modules-load.service: 
main process exited, code=exited, status=1/FAILURE
May 10 01:25:33 fedora22desk systemd[1]: Failed to start Load Kernel 
Modules.
May 10 01:25:33 fedora22desk systemd[1]: Unit 
systemd-modules-load.service entered failed state.
May 10 01:25:33 fedora22desk systemd[1]: systemd-modules-load.service 
failed.

[Sérgio Basto]

On Dom, 2015-05-10 at 01:27 +1000, Adrian wrote:
> On 10/05/15 00:49, Sérgio Basto wrote:
> > On Dom, 2015-05-10 at 00:43 +1000, Adrian wrote:
> > > Yes, Below is why I asked the question ;
> > >
> > > [root@fedora22desk ~]#  /etc/init.d/vboxdrv setup 
> > > bash: /etc/init.d/vboxdrv: No such file or directory 
> > > [root@fedora22desk ~]#
> > >
> > > root@fedora22desk ~]# rpm -qi VirtualBox 
> > > Name        : VirtualBox 
> > > Version     : 4.3.26 
> > > Release     : 3.fc22 
> > > Architecture: x86_64 
> > > Install Date: Sat 09 May 2015 23:43:00 AEST 
> > > Group       : Development/Tools 
> > > Size        : 61244411 
> > > License     : GPLv2 or (GPLv2 and CDDL) 
> > > Signature   : RSA/SHA1, Wed 06 May 2015 20:46:45 AEST, Key ID
> > > 81c9b42397f4d1c1 
> > > Source RPM  : VirtualBox-4.3.26-3.fc22.src.rpm 
> > > Build Date  : Wed 06 May 2015 20:36:21 AEST 
> > > Build Host  : builder02.kwizart.net 
> > > Relocations : (not relocatable) 
> > > Packager    : kwizart 
> > > Vendor      : rpms.kwizart.net 
> > > URL         : http://www.virtualbox.org/wiki/VirtualBox 
> > > Summary     : A general-purpose full virtualizer for PC hardware 
> > > Description : 
> > > A general-purpose full virtualizer and emulator for 32-bit and 
> > > 64-bit x86 based PC-compatible machines. 
> > > [root@fedora22desk ~]#
> >
> > yum install akmod-VirtualBox kernel-devel-$(uname -r)
> >
> > akmods
> >
> > systemctl restart systemd-modules-load.service
>
> I got
>
> [root@fedora22desk ~]# yum install akmod-VirtualBox
> kernel-devel-$(uname -r) 
> Yum command has been deprecated, redirecting to '/usr/bin/dnf install
> akmod-VirtualBox kernel-devel-4.0.1-300.fc22.x86_64'. 
> See 'man dnf' and 'man yum2dnf' for more information. 
> To transfer transaction metadata from yum to DNF, run: 
> 'dnf install python-dnf-plugins-extras-migrate && dnf-2 migrate'
>
> Last metadata expiration check performed 1:08:35 ago on Sun May 10
> 00:16:35 2015. 
> Package akmod-VirtualBox-4.3.26-2.fc22.x86_64 is already installed,
> skipping. 
> Package kernel-devel-4.0.1-300.fc22.x86_64 is already installed,
> skipping. 
> Dependencies resolved. 
> Nothing to do. 
> Complete! 
> [root@fedora22desk ~]# akmods 
> Checking kmods exist for 4.0.1-300.fc22.x86_64             [  OK  ] 
> [root@fedora22desk ~]#  
> [root@fedora22desk ~]# systemctl restart systemd-modules-load.service 
> Job for systemd-modules-load.service failed. See "systemctl status
> systemd-modules-load.service" and "journalctl -xe" for detai
> ls. 
> [root@fedora22desk ~]# systemctl status systemd-modules-load.service 
> ● systemd-modules-load.service - Load Kernel Modules 
>   Loaded: loaded
> (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor
> preset: disabled) 
>   Active: failed (Result: exit-code) since Sun 2015-05-10 01:25:33
> AEST; 20s ago 
>     Docs: man:systemd-modules-load.service(8) 
>           man:modules-load.d(5) 
>  Process: 5599 ExecStart=/usr/lib/systemd/systemd-modules-load
> (code=exited, status=1/FAILURE) 
> Main PID: 5599 (code=exited, status=1/FAILURE)
>
> May 10 01:25:33 fedora22desk systemd[1]: Starting Load Kernel
> Modules... 
> May 10 01:25:33 fedora22desk systemd-modules-load[5599]: Failed to
> insert 'vboxdrv': Exec format error 
> May 10 01:25:33 fedora22desk systemd-modules-load[5599]: Failed to
> insert 'vboxnetflt': Exec format error 
> May 10 01:25:33 fedora22desk systemd-modules-load[5599]: Failed to
> insert 'vboxnetadp': Exec format error 
> May 10 01:25:33 fedora22desk systemd[1]: systemd-modules-load.service:
> main process exited, code=exited, status=1/FAILURE 
> May 10 01:25:33 fedora22desk systemd[1]: Failed to start Load Kernel
> Modules. 
> May 10 01:25:33 fedora22desk systemd[1]: Unit
> systemd-modules-load.service entered failed state. 
> May 10 01:25:33 fedora22desk systemd[1]: systemd-modules-load.service
> failed.

I don't had problems [1] but my F22 is a vm guest, I don't have any F22
as host ... so is hard to tell .
you may try (although no much hope that will fix things) :

dnf remove kmod-VirtualBox-4.0.1-300.fc22.x86_64 
akmods
Checking kmods exist for 4.0.1-300.fc22.x86_64             [  OK  ]
 Building and installing VirtualBox-kmod (*again* with latest
sources ... )

and show what gives dmesg or /var/log/messages after : 
modprobe vboxdrv 
modprobe vboxnetflt 
modprobe vboxnetadp

Thanks for reporting , I will try test it my self ! 
Anyway the better any is one a bug report on :
https://bugzilla.rpmfusion.org/enter_bug.cgi?product=Fedora&component=Vi...

Best Regards ,

[1] 
systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service;
static; vendor preset: disabled)
   Active: active (exited) since Ter 2015-05-05 23:20:42 WEST; 3 days
ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 456 ExecStart=/usr/lib/systemd/systemd-modules-load
(code=exited, status=0/SUCCESS)
 Main PID: 456 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/systemd-modules-load.service

Mai 05 23:20:41 vmdev_f22 systemd-modules-load[456]: Inserted module
'vboxguest'
Mai 05 23:20:42 vmdev_f22 systemd-modules-load[456]: Inserted module
'vboxsf'
Mai 05 23:20:42 vmdev_f22 systemd-modules-load[456]: Inserted module
'vboxvideo'
Mai 05 23:20:42 vmdev_f22 systemd[1]: Started Load Kernel Modules.

[Adrian]

On 10/05/15 00:14, František Zatloukal wrote:
> Hi,
> running "sudo /etc/init.d/vboxdrv setup" should help. Command is same 
> even with systemd.

The vboxdrv command would not be translated in systemd, as it is the 
init.d service file executed directly & not a 'service' cmd.
.
Even if systemd had vboxdrv.service the above command would not 
translate to starting it.

Konsole output
[root@fedora22desk ~]#cd /lib/systemd/system

Konsole output
[root@fedora22desk system]#ls | grep virt
libvirtd.service
libvirtd.socket
libvirt-guests.service
virtlockd.service
virtlockd.socket
[root@fedora22desk system]#ls | grep vbox
[root@fedora22desk system]#

[Adrian]

On 10/05/15 00:05, Adrian wrote:
> On 09/05/15 23:47, Adrian wrote:
> > Result Code:
> >
> > NS_ERROR_FAILURE (0x80004005)
>
> Did
>
> Konsole output
> /etc/init.d/vboxdrv
>
> get replaced by something in systemd ?
>
> Adrian ... vk4tux

Anyhow I installed the akmod etc with dependencies as suggested, but 
still have the issue and cannot use it.

[Ed Greshko]

On 05/09/15 21:47, Adrian wrote:
> Thankyou I am trying this one and get
>
> Result Code:
>
> NS_ERROR_FAILURE (0x80004005)
>
> Component:
>
> Machine
>
> Interface:
>
> IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
>
> when starting a XPvdi

I've seen this error before....a long time ago....so my memory may be faulty....

Isn't this the error one gets when the user is not part of the vboxusers group?

[Thomas Gilliard]

On 05/09/2015 03:15 PM, Ed Greshko wrote:
> On 05/09/15 21:47, Adrian wrote:
> > Thankyou I am trying this one and get
> >
> > Result Code:
> >
> > NS_ERROR_FAILURE (0x80004005)
> >
> > Component:
> >
> > Machine
> >
> > Interface:
> >
> > IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
> >
> > when starting a XPvdi
>
> I've seen this error before....a long time ago....so my memory may be faulty....
>
> Isn't this the error one gets when the user is not part of the vboxusers group?

This procedure works in f22 Workstation TC-3 install x86_64
http://wiki.sugarlabs.org/go/Fedora_22_VirtualBox

Tom Gilliard
satellit

[Adrian]

> >
>
> This procedure works in f22 Workstation TC-3 install x86_64
> http://wiki.sugarlabs.org/go/Fedora_22_VirtualBox
>
> Tom Gilliard
> satellit

Tom, Thankyou very much, that worked a treat * all good here now.

Adrian ... vk4tux