Advanced search

Forums : Technical Support : client_state.xml keeps getting rewritten
Message board moderation

To post messages, you must log in.

AuthorMessage
Tim Kelley

Send message
Joined: 1 Jul 18
Posts: 24
Credit: 1,646,084
RAC: 7,548
Message 22014 - Posted: 17 Dec 2018, 17:35:37 UTC

I frequently get camb_legacy tasks, even though I have virtual machine stuff set up etc. The problem is that the line "<p_vm_extensions_disabled>" keeps showing up in client_state.xml, no matter how many times I delete it. I read somewhere that the program rewrites this file.

Today I got very determined about it and kept deleting the line over and over again, trying to download VM tasks. (The queue may be empty because of server issues, but that isn't the point.) The line would reappear almost immediately, as if the act of updating the project and asking for tasks caused the file to be rewritten. On one occasion, I deleted the line and resaved the file several times within a single minute! I tried making the file read-only, but within a couple of minutes, VM was disabled again and the file was read-write.

Help! How do I keep BOINC from perpetually disabling VM extensions and preventing me from downloading proper C@H tasks?
ID: 22014 · Report as offensive     Reply Quote
xii5ku

Send message
Joined: 1 May 17
Posts: 36
Credit: 37,446,791
RAC: 236,562
Message 22015 - Posted: 17 Dec 2018, 22:37:27 UTC - in response to Message 22014.  
Last modified: 17 Dec 2018, 22:59:12 UTC

For the time being, Cosmology@home does not generate new tasks. If you want to test your host for VirtualBox functionality right now, consider to run the VB based subprojects of LHC@home.

At LHC@home, study Yeti's "Checklist Version 3 for Atlas@Home (and other VM-based Projects) on your PC".

At Cosmology@home, study the FAQ.

Note, client_state.xml contains just this: Client state. It is not a configuration file. Normally this file is "write only", written by the client. AFAIU the only time that the client reads this file is when it starts. In other words, (a) don't edit this file unless you know exactly what you are doing, (b) edit this file only while the client is not running.

Deleting a tag from one of BOINC's xml files does not reset the pertaining setting to a default state. You need to keep the tag and edit it explicitly to the desired default value, instead of merely deleting the tag, if you want the client to go back to the default.

So:

  1. Reboot and go into the BIOS. Check that hardware extensions for virtualization are enabled (Intel VT-x or AMD-v).
  2. Boot into the OS. If the BOINC client was auto-started, shut it down.
  3. If you have Hyper-v, Docker, KVM, or Xen installed, deinstall them.
  4. In BOINC's client_state.xml, change the line <p_vm_extensions_disabled>1</p_vm_extensions_disabled> to <p_vm_extensions_disabled>0</p_vm_extensions_disabled>.
  5. Start the client.

ID: 22015 · Report as offensive     Reply Quote
Tim Kelley

Send message
Joined: 1 Jul 18
Posts: 24
Credit: 1,646,084
RAC: 7,548
Message 22019 - Posted: 19 Dec 2018, 17:34:32 UTC - in response to Message 22015.  

That last point, editing the line instead of deleting it, was the key! Thanks. Since setting p_vm_extensions_disabled to 1, the file has stayed unchanged. VM was working with C@H work units previously, so I know the rest of my system is set up correctly. I'll try LHC@home anyway, looks interesting.

One new "feature" since editing the file. I now get these errors frequently in my BOINC log:

12/19/18 09:32:08 | | Can't delete previous state file; Access is denied. (0x5)
12/19/18 09:32:14 | | Can't rename current state file to previous state file; Access is denied. (0x5)

The file isn't read-only, according to Windows. When I edited it previously and deleted the line, it had no trouble overwriting it. Is this a problem?

Thanks!
ID: 22019 · Report as offensive     Reply Quote

Forums : Technical Support : client_state.xml keeps getting rewritten