GrueMaster
New ContributorJoined 5 years ago
User Profile
New Contributor
User Widgets
Contributions
Re: At least one S10 system fails to launch X2Go
I didn't catch that minor detail near the bottom of the x2go documentation. Not exactly a very good location for it to be honest. Suggestion: Have a MOTD on that system that will let users know that it isn't supported when they log in. As to our need, we are developing an end-to-end streaming video analytics solution, and devcloud was suggested by Intel Marketing as a way for customers (Intel and ours) to try our product. For visualization, we create a webUI. Being able to launch a browser in the system under X2Go would be easier, especially since Intel wants to block web servers on these systems (which I fully understand). Once the customer 'sees' that the demo is working, they can discontinue use of the webui and focus on attaching to our back end apis and running their own experiments.2.1KViews0likes1CommentRe: Systems with fpga,darby need more hugepages
As a Linux developer and sysadmin for 25 years (I helped work on the Intel LinuxSET images back in 1999-2003), I am well aware of how to set this, however it requires root/sudo which is not allowed on devcloud. Just because your forum tags me as a beginner doesn't mean I am one.1.6KViews0likes0CommentsSystems with fpga,darby need more hugepages
Systems with S10 were configured with 256 hugepages (cat /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages) a few weeks ago. Now they are reverted back to 20. Can we get them set back to 256? Our tools require them to be high, to be able to maximize the DMA transfers between the S10 and system memory. The demo DMA provided by IntelDevStack is not sufficient for realtime streaming, and we have written our own optimized DMA engine, but we require these larger page tables. Other users will benefit from them as well. To enable, please add vm.nr_hugepages = 256 to /etc/sysctl.d/10-hugetlbfs.conf and either run 'sudo sysctl -p' or reboot to enable them. Thanks, Tobin Davis Senior DevOps Engineer Megh Computing1.7KViews0likes4CommentsRe: At least one S10 system fails to launch X2Go
Steps to reproduce: ssh devcloud pbsnodes -s v-qsvr-fpga|fgrep -A1 s005-n008 # verify system is free before next steps qsub -q batch@v-qsvr-fpga -I -l nodes=s005-n008:ppn=2 # to get an interactive shell (In a new terminal on your desktop) ssh -L 4002:s005-n008:22 devcloud # this establishes the X2Go tunnel Launch X2Go client per instructions. Observe that xfce4-session fails to launch. The above steps work on other systems I have tested so far.2.3KViews0likes6CommentsAt least one S10 system fails to launch X2Go
I have been testing our solution on the S10 platforms, part of which requires a web browser to view our demo UI. X2Go is the simplest solution for this currently (we'll look at tunneling later). s005-n008 was the system assigned by devcloud_login. I was able to get around this by logging out of that system, running 'pbsnodes -s v-qsvr-fpga' to find a free S10 and ' qsub -q batch@v-qsvr-fpga -I -l nodes=s005-n009:ppn=2' to get a different available system. I've also noticed differences in the system configurations (mostly minor, dealing with /opt installations). These systems should be cloned and up-to-date (wish they were Ubuntu as well - sigh).2.3KViews0likes7Comments