{"id":3296,"date":"2012-02-02T12:10:06","date_gmt":"2012-02-02T10:10:06","guid":{"rendered":"https:\/\/ingmarverheij.com\/?p=3296"},"modified":"2013-11-30T14:30:22","modified_gmt":"2013-11-30T13:30:22","slug":"connect-to-vm-without-xencenter","status":"publish","type":"post","link":"https:\/\/ingmarverheij.com\/en\/connect-to-vm-without-xencenter\/","title":{"rendered":"Connect to VM without XenCenter"},"content":{"rendered":"

Author: Ingmar Verheij<\/a>\"\"<\/p>\n

If you want to connect to the console of a virtual machine running on Citrix XenServer you either need XenCenter or the Web Self Service portal.<\/p>\n

I created a PowerShell script that connects to the console of the virtual machine, without the use of both. This script can be used to offer a shortcut to a virtual machine without requiring the user to have XenCenter installed, or having a XenServer Enterprise or Platinum license (it works with the free license).<\/p>\n

<\/p>\n

VNC<\/h4>\n

XenServer uses virtual network computing <\/em>(VNC) to connect to the console of a virtual machine. In this script I\u2019m using the TightVNC<\/a> viewer to connect to the console, but you can use any other VNC viewer (although it requires you to change the script and might give issues when used via Citrix ICA).<\/p>\n

<\/h4>\n

SSH tunnel<\/h4>\n

The VNC connector on the XenServer only listens on the localhost, so you\u2019re unable to connect to it directly. Before you can connect your VNC viewer to the console you need to tunnel the data through an SSL tunnel. This will encapsulate all VNC data through a secured channel and deliver it on the XenServer. I\u2019m using plink (a component of the PuTTY<\/a> suite) to send SSH commands and setup a SSL tunnel between the host and the XenServer host (just like XenCenter does when you connect to the console of a VM).<\/p>\n

Note: The sa2 key fingerprint is accepted automatically by the script. <\/em><\/p>\n

Note: I\u2019m aware there is a Powershell cmdlet for SSH<\/a> (which could prevent the use of plink) but this cmdlet is unable to set up a SSL tunnel.<\/em><\/p>\n

<\/h4>\n

Connect to who and where?<\/h4>\n

Before you can setup the SSL tunnel you need to know two thing. The XenServer the VM is running on (1) and the port the VNC server is running on (2). So before setting up the SSL tunnel I\u2019m querying the XenServer (pool master)\u00a0 for IP address of the XenServer host where the VM is running.<\/p>\n

The name of my virtual machine is \u2018WS01\u2019 and I added custom field \u2018STUDENT\u2019 with the value \u20181\u2019.<\/em><\/p>\n

xe vm-list name-label=\"WS01\" other-config:XenCenter.CustomFields.STUDENT=1 os-version:distro=\"windows\" params=resident-on --minimal\r\nxe pif-list management=true params=IP host-uuid=(uuid of XenServer host) --minimal<\/pre>\n
Now I know the IP address of the XenServer where the VM is running I can search for the domain ID of the virtual machine. With the domain ID I can search for the VNC server process qemu-dm-<domid>.<\/p>\n
xe vm-list name-label=\"WS01\" other-config:XenCenter.CustomFields.STUDENT=1 os-version:distro=\"windows\" params=dom-id --minimal\r\nnetstat -lp|grep -w $varDomPrefix(domID of the VM)|awk '{print $4}'|cut -d: -f2<\/pre>\n
Okay, so now I know the IP address of the XenServer where the VM is running (1) and the port where the VNC host is running (2).<\/p>\n
plink -N \u2013L (VNC port):localhost:(VNC port) root@(IP<\/a> Address of XenServer)<\/pre>\n
 <\/p>\n
Connecting though ICA (Citrix XenApp \/ XenDesktop)<\/h4>\n
I published the console of a virtual machine as a published application so my users can access the console from anywhere (via the CloudGateway). During testing I found out that both RealVNC and UltraVNC had performance issues, only TightVNC in 8-bit mode worked at a proper speed.<\/p>\n
If you don\u2019t want the connect in 8-bit mode, change the line $vncUse8Bit=$true<\/em> to $vncUse8Bit=$false<\/em>.<\/p>\n
\u00a0\"Published<\/a>\"PowerShell\"<\/a>\"Remote<\/a><\/h4>\n
<\/h4>\n
 <\/p>\n
PowerShell script (this is where it\u2019s all about)<\/h4>\n
Download:\u00a0\n\tConsoleXSConnect.ps1<\/a>\n<\/p>\n
<\/h4>\n
 <\/p>\n
Usage<\/h4>\n
The script requires 4 arguments and has 2 optional arguments<\/p>\n
Usage<\/strong>\r\npowershell.exe .\\ConsoleConnect.ps1 (XenServerPoolMaster) (XenServerUsername) (XenServerPassword) (VMName) [CustomFieldName] [CustomFieldValue]\r\n\r\nExample<\/strong>\r\npowershell.exe .\\ConsoleConnect.ps1 172.16.1.1 root Passw0rd WS01 STUDENT 1<\/pre>\n
XenServerPoolMaster: The IP\/FQDN of the XenServer (pool master) host<\/p>\n
XenServerUsername: The username to connect to the XenServer<\/p>\n
XenServerPAssword: The password to connect to the XenServer<\/p>\n
VMName: The name of the virtual machine<\/p>\n
CustomFieldName (optional): The name of a custom field<\/p>\n
CustomFieldValue (optional): The value of the custom field<\/p>\n
 <\/p>\n
The custom field can be used to uniquely identify a virtual machine if the name of the machine is reused. In my environment I cloned the virtual machine \u2018WS01\u2019 multiple times and added a CustomField \u2018STUDENT\u2019. For each student a virtual machine is published.<\/p>\n
\"'WS01'<\/a>.<\/p>\n
 <\/p>\n
Additional downloads (required)<\/h4>\n