Message boards :
Number crunching :
LHC@home and pc shutdown (vbox)
Message board moderation
Author | Message |
---|---|
Send message Joined: 20 May 06 Posts: 2 Credit: 1,473 RAC: 0 |
Hi i have a laptop (at work) where is installed BOINC and everyday i shut down the notebook when i go home. I think vbox doesn't like the pc shutdown, because sometime (the next morning) i got a "computational error", only in the LHC vbox project. I have to do something before shutdown pc? In 8-9 hours it doesn't finish and i can't let pc "on" all time. PS Sometime, when shutting down, laptop says "VBOX is connected and can't shutdown"... i wait, but after 3-4 mins i force shutdown. Thanks |
Send message Joined: 18 Dec 15 Posts: 1686 Credit: 100,455,829 RAC: 103,299 |
Which subproject are you crunching? CMS tasks take minimum about 12 hours (or more), ATLAS between 6 and 8 hours (with a fairly decent processor). And yes, VBox doesn't like automatic shutdowns. With manual shutdowns ("VBOX is connected and can't shutdown"), this normally is not a problem. |
Send message Joined: 20 May 06 Posts: 2 Credit: 1,473 RAC: 0 |
I enabled all subproject, but i have other 6 BOINC project running (like Einstein, Asteroid, etc) Normally i shutdown manually my laptop, but that message appears only when are active LHC tasks that requires Vbox. I don't use automatic shutdown. Till now errors are only on LHCb and Theory Simulation (after 35790 sec of CPU time) so I think sometimes something goes wrong with shutdown. |
Send message Joined: 18 Dec 15 Posts: 1686 Credit: 100,455,829 RAC: 103,299 |
I think vbox doesn't like the pc shutdown, because sometime (the next morning) i got a "computational error", only in the LHC vbox project. Normally, this should not happen - but in general, I think vbox doesn't like too much interrupted operation (by shutdown and switch on later). |
Send message Joined: 29 Aug 05 Posts: 998 Credit: 6,264,307 RAC: 71 |
I think vbox doesn't like the pc shutdown, because sometime (the next morning) i got a "computational error", only in the LHC vbox project. We've tried to make the VMs (CMS at least) fairly resilient to interruptions, but it really should be a managed interruption. Shutdown BOINC (either via boincmgr or the ./boinccmd --quit command), and then watch in Task Manager or similar (top/htop on Linux or Mac) to make sure that all VBox instances have shut down cleanly, which involves writing their memory state to disk and could take a minute or two. |
Send message Joined: 2 Sep 04 Posts: 453 Credit: 193,369,412 RAC: 10,065 |
When I have time to shutdown I open my BOINC and force "shutdown connected client". This gives my VB-Projects a lit bit more time to shut down gracefully. The more VB-Projects are running, the more time it needs to save all to disc. A second way would be to make a short script that first shuts down the BOINC-Client, waits a little bit and then shuts down your Laptop Supporting BOINC, a great concept ! |
©2024 CERN