Fedora 20 and Virtualbox

Message boards : Questions and problems : Fedora 20 and Virtualbox
Message board moderation

To post messages, you must log in.

AuthorMessage
cigam

Send message
Joined: 20 Oct 14
Posts: 3
Hungary
Message 56843 - Posted: 20 Oct 2014, 13:43:19 UTC

I installed the latest boinc clien/manager, and virtualbox. I added the Atlas@Home, but in the log always write this message: Message from server: VirtualBox version 3.2 or later is required
But the VirtualBox version is 4.3.18
What do I wrong? Any idea?
ID: 56843 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15483
Netherlands
Message 56845 - Posted: 20 Oct 2014, 14:00:54 UTC - in response to Message 56843.  

Since it's a message from the Atlast@Home server, you best ask on their forums. Checking them, I see this thread stating the same as you see. If that isn't your thread already, best add to it.
ID: 56845 · Report as offensive
cigam

Send message
Joined: 20 Oct 14
Posts: 3
Hungary
Message 56849 - Posted: 20 Oct 2014, 14:23:31 UTC - in response to Message 56845.  
Last modified: 20 Oct 2014, 14:23:50 UTC

But the boinc client check the virtualbox version number, and the boinc client send this number to atlas server. Not?
ID: 56849 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15483
Netherlands
Message 56852 - Posted: 20 Oct 2014, 15:26:23 UTC - in response to Message 56849.  

Yes, but we don't know what their server does with that information, how it interprets it. For all we know it has a condition set that says 4.3 is lower than 3.2, therefore anything with "message from server" is a project problem.

You can check in your BOINC event log (or stdoutdae.txt) what version VirtualBox it detects.
ID: 56852 · Report as offensive
cigam

Send message
Joined: 20 Oct 14
Posts: 3
Hungary
Message 56853 - Posted: 20 Oct 2014, 15:52:36 UTC - in response to Message 56852.  
Last modified: 20 Oct 2014, 16:45:07 UTC

I found one little thing:
Virtualbox version: WARNING: The vboxdrv kernel module is not loaded. Either there is no module

But when Virtualbox install/configure, I use this command
service vboxdrv setup
and look like everithing ok:
Stopping VirtualBox kernel modules ok
Uninstalling old VirtualBox DKMS kernel modules ok
Trying to register the VirtualBox kernel modules using DKMS ok
Stating VirtualBox kernel module ok

lsmod | grep vbox command output:
vboxpci
vboxnetapi
vboxnetflt
vboxdrv
ID: 56853 · Report as offensive

Message boards : Questions and problems : Fedora 20 and Virtualbox

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.