Remote Desktop and CUDA

Questions and Answers : GPU applications : Remote Desktop and CUDA

Author	Message
JLConawayII Send message Joined: 2 Apr 02 Posts: 181 Credit: 2,630,328 RAC: 380	Message 996753 - Posted: 17 May 2010, 19:02:20 UTC
	I have recently run into this issue when setting up a remote boinc machine, whenever Remote Desktop is activated it kills any CUDA processing currently taking place on the remote machine, as well as killing every other CUDA WU in the queue. I understand that shutting down CUDA work is an expected behavior of Remote Desktop, however what I thought is that BOINC is supposed to STALL any CUDA processing until the CUDA driver returns, WITHOUT killing every single CUDA WU on the machine. I'm currently using boinc 6.10.18. Is this an issue that will be resolved in one of the newer implementations of the software? Or will I have to resort to using something like VNC in order to access my remote machine without killing my boinc applications?
	ID: 996753 ·

Sidewinder Send message Joined: 15 Nov 09 Posts: 64 Credit: 2,191,197 RAC: 0	Message 996823 - Posted: 17 May 2010, 23:07:21 UTC - in response to Message 996753. Last modified: 17 May 2010, 23:07:40 UTC
	BOINC should just suspend GPU work. If you have a monitor, you can verify this. My cruncher is a mostly stand-alone box. I use LogMeIn to remote into the machine. Others use TeamViewer and/or a flavor of VNC. I find that LogMeIn works the best for me. https://secure.logmein.com/US/home.aspx ____________
	ID: 996823 ·

JLConawayII Send message Joined: 2 Apr 02 Posts: 181 Credit: 2,630,328 RAC: 380	Message 996844 - Posted: 18 May 2010, 1:24:29 UTC - in response to Message 996823.
	BOINC should just suspend GPU work. If you have a monitor, you can verify this. It is definitely killing all of the workunits as compute errors as soon as I use remote desktop to connect to the remote box. Not only that, but once disconnected from remote desktop it doesn't seem to reactivate the Nvidia driver on that system. I watched my tasks for that computer for awhile after disconnecting, and dozens upon dozens of WU's were all being returned with compute errors. It would download new WU's and then kick them back with errors. Logging back in on that system fixes the problem, but the system will be running headless. The most obvious solution seems to be to use VNC instead of remote desktop. This leaves me with a bad feeling though, since I hate when things don't work the way they should and remote desktop should be competently enough designed to avoid these sorts of issues. Damn you Microsoft.
	ID: 996844 ·

BilBg Send message Joined: 27 May 07 Posts: 2014 Credit: 3,002,422 RAC: 5,846	Message 996862 - Posted: 18 May 2010, 3:26:20 UTC - in response to Message 996844.
	You can read: Remote Desktop http://setiathome.berkeley.edu/forum_thread.php?id=54045 Crashing GPUs when coming in with Remote Desktop http://setiathome.berkeley.edu/forum_thread.php?id=59604 ____________ - ALF - "Find out what you don't do well ..... then don't do it!" :)
	ID: 996862 ·

Ageless Send message Joined: 9 Jun 99 Posts: 11633 Credit: 1,986,276 RAC: 4,155	Message 996895 - Posted: 18 May 2010, 5:45:05 UTC - in response to Message 996844. Last modified: 18 May 2010, 5:58:59 UTC
	James, is this on your Windows Vista or Windows 7 system? Is this system fully updated with Windows Updates? 6.10.18 does have the "pause CUDA if remote desktop is detected" code, but this may have changed in your OS due to a Windows Update. It may also possible that the machine you're "remote desktopping to" (phew, what bad English ;-)) has a task stuck in the GPU. You could try for a full reboot of that machine. ____________ Jord - BOINC FAQ Service - BOINC User Wiki Real is just a matter of perception.
	ID: 996895 ·

Ageless Send message Joined: 9 Jun 99 Posts: 11633 Credit: 1,986,276 RAC: 4,155	Message 996972 - Posted: 18 May 2010, 15:37:34 UTC
	Ah, it would appear that 6.10.18 only has the remote desktop kills tasks prevention code for ATI cards, not for Nvidia cards. Please update to the latest development version (.56) from http://boinc.berkeley.edu/download_all.php. That'll fix it. ____________ Jord - BOINC FAQ Service - BOINC User Wiki Real is just a matter of perception.
	ID: 996972 ·

JLConawayII Send message Joined: 2 Apr 02 Posts: 181 Credit: 2,630,328 RAC: 380	Message 996990 - Posted: 18 May 2010, 22:50:25 UTC
	I installed UltraVNC, it seems to work fine for the functionality that I need with a minimal footprint on the system. Disaster has been averted once again. Thanks for your advice guys. ____________
	ID: 996990 ·

skildude Send message Joined: 4 Oct 00 Posts: 8940 Credit: 36,381,476 RAC: 55,695	Message 997004 - Posted: 18 May 2010, 23:53:47 UTC - in response to Message 996990.
	I was turned on to Logmein. they have a free webservice that can access windows machines. Unfortunately, they dont have anything for Linux yet ____________ Proud member of TSWB. End terrorism by building a school
	ID: 997004 ·

Stormprobe Volunteer tester Send message Joined: 20 May 99 Posts: 11 Credit: 7,254,313 RAC: 10,030	Message 1000783 - Posted: 5 Jun 2010, 1:54:22 UTC - in response to Message 996753.
	Do you have the same problem with SETI@home version 6.10.56? Has anyone tested this Windows 7's RemoteFX in SP1?
	ID: 1000783 ·

Grand Admiral Thrawn Send message Joined: 19 Feb 01 Posts: 53 Credit: 21,332,091 RAC: 29,114	Message 1023019 - Posted: 6 Aug 2010, 12:48:13 UTC
	I have tested this using BOINC 6.10.56 on Windows XP x64 Edition, running BOINC tasks under an unprivileged account. RDP will still break CUDA SETI work. To fix it, you will need to log in to the machine locally, and restart BOINC (and the computation processes with it). I'm using VNC now, until this gets properly fixed. ____________ 3dfx Voodoo5 6000 AGP HiNT Rev.A 3700 prototype, dead HiNT bridge
	ID: 1023019 ·

Questions and Answers : GPU applications : Remote Desktop and CUDA