Message boards :
Number crunching :
Problem VirtualBox 7.1.0 with RDP (Remote Desktop)
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 14 Jan 10 Posts: 1446 Credit: 9,714,030 RAC: 251   |
This is tested on Windows 10. With VirtualBox version 7.1.0 and Extention Pack (7.1.0) installed, Remote Desktop - in BOINC Manager: Show VM Console - is not working anymore. A vbox_remote_desktop.xml is created, but with port 0 (zero) In the result: Enabling remote desktop for VM. Required extension pack not installed, remote desktop not enabled. I downgraded to VBox version 7.0.20. |
|
Send message Joined: 14 Jan 10 Posts: 1446 Credit: 9,714,030 RAC: 251 |
I have to add that also the real processing starts after 40 minutes. 'Maybe' another problem with this VBox version. Could be Virtual HD-controller or Network interface. No idea.  |
 Send message Joined: 9 Feb 09 Posts: 37 Credit: 3,850,867 RAC: 13,111 
|
"My advice is to wait for others to act as beta testers with a newer, more modern application. Give it at least 1 month so they can identify and correct any possible defects. Before installing, read the forums to see if there are any issues. You will have more free and productive time with fewer problems." |
|
Send message Joined: 14 Jan 10 Posts: 1446 Credit: 9,714,030 RAC: 251 |
Besides mine noticed RDP-problem, there seems to be a real problem (maybe others) with the network interface between Host and Guest: https://www.virtualbox.org/ticket/22164 For 1 Theory task cvmfs needs about 360MB to download into BOINC's Guest VM and the speed is about 130KB, so before the processing can really start within the VM, it takes over half an hour or more. Example task: https://lhcathome.cern.ch/lhcathome/result.php?resultid=414225612 |
|
Send message Joined: 24 Jan 06 Posts: 4 Credit: 8,579,212 RAC: 4,361 
|
The download bottleneck, with VB 7.1.x, still seems to be present. I created a local squid proxy, a few weeks back, to hopefully resolve this issue - it did make some difference but not the major improvement I was hoping for. Four days ago I started getting the Could not get an x509 credentialmessage for CMS tasks error. So, yesterday, I updated to VB 7.1.6 hoping that the recent maintenance fixes for VB would resolve the issue no joy. Since then I've restricted the PC to running only one CMS task at a time, the same error is still produced. I did try to go through other users tasks and all the CMS ones I can find are run natively and work, so I don't know if Windows VB users, those on previous versions, are producing CMS results successfully or not - nothing in the forums so I presume they are. |
|
Send message Joined: 14 Jan 10 Posts: 1446 Credit: 9,714,030 RAC: 251 |
I suppose it's not VBox version related, but something wrong with your proxy. The Theory's you ran were working fine, but not CMS. First you could try a CMS without a local proxy. |
 Send message Joined: 15 Jun 08 Posts: 2631 Credit: 270,474,540 RAC: 85,418  |
This is reported in your logfiles: 2025-01-28 07:04:53 (2568): Guest Log: [INFO] 2.7.2.0 http://s1ral-cvmfs.openhtc.io http://192.168.1.56:3128 2025-01-28 07:04:53 (2568): Guest Log: [INFO] Environment HTTP proxy: http://window:3128 In the proxy configuration form try the IP "192.168.1.56" instead of the proxy name "window" before you reconfigure anything else. |
|
Send message Joined: 24 Jan 06 Posts: 4 Credit: 8,579,212 RAC: 4,361
|
Seems to have resolved the issue, thank you! I've completed two CMS and two Atlas tasks and well into another two CMS ones, these having passed the previous failure point. Possibly down to my DNS server giving out an IPv6 address and causing breakage with the proxy? Not sure but it's all back to working now. |
©2025 CERN