Message boards : Questions and problems : Unrecognized tag in cc_config.xml
Message board moderation
Author | Message |
---|---|
![]() ![]() Send message Joined: 12 Feb 12 Posts: 6 ![]() |
BOINC client version 7.12.1 for windows_x86_64 Windows 10 Pro Version: 1803 Build: 17134.320 BOINC is not installed as a service. 2 CPUs used. (Out of 4.) I'm running: climateprediction.net Cosmology@Home Einstein@Home Milkyway@Home SETI@home Today I restarted BOINC Manager after making the changes needed to get Cosmology@Home to use VirtualBox. The first line in the event log after restarting BOINC Manager reads: Unrecognized tag in cc_config.xml: <dont_use_wsl> Line 15 in the log reads: No WSL found. Line 16 reads: VirtualBox version 5.2.18 Can anyone tell me what changes I need to make, to correct this? If any. BigDave67 |
![]() Send message Joined: 28 Jun 10 Posts: 2842 ![]() |
I have had this on one of my boxes but can't remember if it is my Windows client and manager running under WINE or the native Linux version of BOINC. (I swap between the two, using native Linux when CPDN has work for it.) I have just ignored it. Alternatively you could edit the cc_config file to remove the offending line. But unless you are more familiar with BOINC and this file than I am, I would wait till one of the more knowledgeable people on the forum comes along before doing so. |
Send message Joined: 5 Oct 06 Posts: 5149 ![]() |
It's a small, harmless, bug. Don't bother to try to fix it - it'll just come back again. WSL stands for Windows System for Linux - a sort of reverse WINE. It's a new feature in Windows 10 only. One of the projects was experimenting with it, so one of our volunteer developers added support code so it could be used like VBox by other projects too. Unfortunately, he missed one of the places where it needed handling: that was fixed within a couple of days, but sod's law dictated that v7.12.1 was prepared for release between the bug and the fix, and the fix wasn't carried over (I say with feeling, because I wrote the fix). But you've reminded me to check that the fix works in v7.14.0, and it does. So one way to eliminate the message is to join the v7.14.0 testing programme. |
![]() Send message Joined: 28 Jun 10 Posts: 2842 ![]() |
That might explain why I only saw it on one box? One has WINE emulating WIN10 and one XP. As I don't have a real Win10, I won't be able to get the code to try running WSL under WINE to emulate Linux. - Could be fun for someone with a dual boot system? |
Send message Joined: 5 Oct 06 Posts: 5149 ![]() |
I think the BOINC code is designed only to run the WSL detection tests under 64-bit versions of Windows - that will rule out all but a tiny minority of XP users. It does run under Windows 7/64 (my preferred OS), but it - obviously - always finds that WSL is not installed, and sets the 'don't use' tag, so that projects can set their servers not to send WSL work to hosts incapable of processing it. (it actually uses a slightly different tag for that purpose - <WSL_available> 1|0 at the bottom of <host info> in the sched_request) |
![]() ![]() Send message Joined: 12 Feb 12 Posts: 6 ![]() |
Thanks, guys So, I don't need to worry about it right now, not until I decide to change the cc_config.xml file anyway. That also explains why I get the line "No WSL found." in the log file on my Windows 7 machine. Thanks too for the info on WSL, I may want to check it out. BigDave67 |
Copyright © 2025 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.