Description of problem: Following bug 1215436 and a discussion with Alon, we should tell users to use vdsm tools to access the console. If vdsm does not yet provide such tools (didn't check), we should open a dependent bug there.
*** Bug 1269850 has been marked as a duplicate of this bug. ***
After a brief discussion with Didi, he is basically asking to: 1. add another option to vdsClient (or a dedicated new tool) to actually act as a wrapper of socat letting the user connect to the VM using that instead of directly using socat 2. from hosted-engine-setup just print: 'use vdsClient --connectVMConsole <vmname>' per something similar hiding all the connection details. Probably we could also use the same command with an additional option to let the user choose a textual or graphical connection. The benefit of this is that we move all the connection handling details in VDSM and we completely decouple hosted-engine-setup on this side: any new parameter or connection strategy will be handled on VDSM side only.
VDSM does not have a console feature we can use, therefore closing the bug.