Version 2.01 with VirtualBox 5.1 support


Advanced search

Message boards : News : Version 2.01 with VirtualBox 5.1 support

Author Message
David Cameron
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 13 May 14
Posts: 248
Credit: 2,026,552
RAC: 390
      
Message 4905 - Posted: 4 Aug 2016, 11:46:21 UTC

We have released v2.01 of ATLAS@Home (single-core) with updated vboxwrappers to support VirtualBox 5.1. This should help with the large number of STATUS_ACCESS_VIOLATION errors that happen with v2.00. Please let us know if you still have problems running with VirtualBox 5.1.

MARCOTE, ERNESTO DANIEL
Send message
Joined: 25 Jun 14
Posts: 1
Credit: 148,714
RAC: 0
    
Message 4910 - Posted: 4 Aug 2016, 17:34:31 UTC - in response to Message 4905.

Great news. I hope multicore versiĆ³n be released soon.

Profile MAGIC Quantum Mechanic
Avatar
Send message
Joined: 4 Jul 14
Posts: 329
Credit: 485,372
RAC: 0
    
Message 4915 - Posted: 4 Aug 2016, 22:45:55 UTC - in response to Message 4905.
Last modified: 4 Aug 2016, 23:28:52 UTC

We have released v2.01 of ATLAS@Home (single-core) with updated vboxwrappers to support VirtualBox 5.1. This should help with the large number of STATUS_ACCESS_VIOLATION errors that happen with v2.00. Please let us know if you still have problems running with VirtualBox 5.1.


Ok David, I am starting to update to VB 5.1.2 on the hosts that have had the most Invalids (including Extension Pack) as usual my DSL will take about 30mins each and then I will find out if that made a difference.

Not sure why I have a couple hosts with no problem since they are basically all the same including OS and memory as the others.

Edit: same old thing.......suspended all the different tasks that use VB and after installing the update they all got trashed so I had to start the vLHC's over again and the vLHC-dev I tied to run wouldn't even get past *computer error* and have to d/l new Atlas tasks to see if they will start running.

vLHC-dev just keep crashing and saying "no log file found"

Still waiting for new Atlas tasks to d/l since for some reason I have to d/l that .vdi again too.

So far the regular vLHC 261.97 are running
____________

Juha
Send message
Joined: 3 Jun 16
Posts: 5
Credit: 0
RAC: 0
Message 4931 - Posted: 5 Aug 2016, 19:58:23 UTC

You need to correct rsc_memory_bound to match memory_size_mb. Right now you are sending tasks with rsc_memory_bound=2000000000=1907 MB and memory_size_mb=2241.

VirtualBox runs VMs in such a way that BOINC client can't always tell how much memory the VM is using. Because of this, since 7.2.24, the client is using rsc_memory_bound as the amount of RAM a vbox task is using.

The 300 MB difference you have now is enough to make BOINC run more tasks than one's host has RAM installed.

I sent a message worded similarly as this one to boinc_projects mailing list last week. Guess it didn't reach you. If you haven't subscribed to the mailing list yet you should. Among other things it is used to send important announcements, like announcements of fixed vulnerabilities, to projects admins.

Profile MAGIC Quantum Mechanic
Avatar
Send message
Joined: 4 Jul 14
Posts: 329
Credit: 485,372
RAC: 0
    
Message 4934 - Posted: 5 Aug 2016, 23:08:12 UTC

My first task with 5.1.2 ran 20hrs 45mins to get to 97% so I had to finally abort it and will try again.


____________

David Cameron
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 13 May 14
Posts: 248
Credit: 2,026,552
RAC: 390
      
Message 4951 - Posted: 8 Aug 2016, 10:16:15 UTC - in response to Message 4931.

You need to correct rsc_memory_bound to match memory_size_mb. Right now you are sending tasks with rsc_memory_bound=2000000000=1907 MB and memory_size_mb=2241.

VirtualBox runs VMs in such a way that BOINC client can't always tell how much memory the VM is using. Because of this, since 7.2.24, the client is using rsc_memory_bound as the amount of RAM a vbox task is using.

The 300 MB difference you have now is enough to make BOINC run more tasks than one's host has RAM installed.


Thanks for the notice, I've changed rse_memory_bound=2400000000 = 2288MB for new tasks.

I sent a message worded similarly as this one to boinc_projects mailing list last week. Guess it didn't reach you. If you haven't subscribed to the mailing list yet you should. Among other things it is used to send important announcements, like announcements of fixed vulnerabilities, to projects admins.


Can you provide some more info on how to sign up to this mailing list?

Juha
Send message
Joined: 3 Jun 16
Posts: 5
Credit: 0
RAC: 0
Message 4956 - Posted: 8 Aug 2016, 13:46:42 UTC - in response to Message 4951.

Thanks for the notice, I've changed rse_memory_bound=2400000000 = 2288MB for new tasks.


Thank you.

Can you provide some more info on how to sign up to this mailing list?


Sure. You can sign up here. There are also other lists/groups.

Profile Tasrif
Send message
Joined: 9 Aug 16
Posts: 1
Credit: 0
RAC: 0
Message 4988 - Posted: 11 Aug 2016, 12:38:03 UTC - in response to Message 4905.

Can not find the download link.

Profile Yeti
Avatar
Send message
Joined: 20 Jul 14
Posts: 696
Credit: 22,597,832
RAC: 5,020
      
Message 4989 - Posted: 11 Aug 2016, 12:39:13 UTC - in response to Message 4988.

Can not find the download link.

for what ?

aafische
Send message
Joined: 28 Sep 16
Posts: 1
Credit: 261,473
RAC: 828
      
Message 5415 - Posted: 30 Sep 2016, 0:03:56 UTC - in response to Message 4905.

Hi.
My Atlas tasks were running, but now consistently fail.
Error log has: "Vbox app stderr indicates CPU VM extensions disabled"

Even though I've confirmed that my CPU VM extensions are turned on.

"Hyper-V - VM monitor Mode Extensions"
"Hyper-V - Second Level Address Translation Extensions"
"Hyper-V - Virtualization Enabled in Firmware"
"Hyper-V - Data Execution Protection"
... all set to true.

I've upgraded to the latest VirtualBox (5.1.6) with Extension Packs.

I've also tried installing and also removing Hyper-V (this is on a Windows machine).

Any guidance?

Profile Yeti
Avatar
Send message
Joined: 20 Jul 14
Posts: 696
Credit: 22,597,832
RAC: 5,020
      
Message 5417 - Posted: 30 Sep 2016, 10:45:57 UTC - in response to Message 5415.

Hi.
My Atlas tasks were running, but now consistently fail.
Error log has: "Vbox app stderr indicates CPU VM extensions disabled"

Even though I've confirmed that my CPU VM extensions are turned on.

"Hyper-V - VM monitor Mode Extensions"
"Hyper-V - Second Level Address Translation Extensions"
"Hyper-V - Virtualization Enabled in Firmware"
"Hyper-V - Data Execution Protection"
... all set to true.

I've upgraded to the latest VirtualBox (5.1.6) with Extension Packs.

I've also tried installing and also removing Hyper-V (this is on a Windows machine).

Any guidance?


Make shure you uninstalled all Hyper-V modules

Then work through this checklist: http://atlasathome.cern.ch/forum_thread.php?id=581

WIth Point 5 you should find help you are looking for

Message boards : News : Version 2.01 with VirtualBox 5.1 support