From 53830e5aa8042a311ea60c901322f0d90a4ef378 Mon Sep 17 00:00:00 2001
From: "Albert.Schulz" <albert.schulz@tu-dresden.de>
Date: Thu, 13 Apr 2017 18:43:56 +0200
Subject: [PATCH] Add new post to fix vivado bug

---
 ...ado-remote-connection-test-failed.markdown | 24 +++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 source/_posts/2017-04-13-solve-vivado-remote-connection-test-failed.markdown

diff --git a/source/_posts/2017-04-13-solve-vivado-remote-connection-test-failed.markdown b/source/_posts/2017-04-13-solve-vivado-remote-connection-test-failed.markdown
new file mode 100644
index 0000000..ca7c643
--- /dev/null
+++ b/source/_posts/2017-04-13-solve-vivado-remote-connection-test-failed.markdown
@@ -0,0 +1,24 @@
+---
+layout: post
+title: "Solve 'Connection test failed for host' issue for Vivado on Ubuntu"
+date: 2017-04-13 20:49:52 +0100
+comments: true
+categories:
+  - vivado
+  - ubuntu
+  - xilinx
+---
+
+When you are trying to get Vivado Remote Connections working on Ubuntu, you might have an issue to establish the connection.
+This can be easily solved by adding a symlink to your bash, called sh. You can do this for example using the following commands:
+
+```bash
+$ mkdir -p ~/.local/bin
+$ ln -s /bin/bash ~/.local/bin/sh
+```
+
+Thanks to ole2 for providing this solution in the xilinx forum, which you can find here:
+[forum post](https://forums.xilinx.com/t5/Installation-and-Licensing/Vivado-2013-2-Launching-jobs-on-a-remote-host)
+
+As he points out, this seem to be a bug in Vivado.
+I had this issue in Vivado 2016.4 and Ubuntu 16.04 LTS.