Connect to VM without installing NoMachine onto VM

[kevin.poole]

Hello!

I have what I assume is a fairly advanced use case in mind, but I wonder if it is something that anyone has thoughts on.

What I would like to do, is to be able to use NoMachine to connect to a VM, but I do not want to install NoMachine software directly onto the VM – I would prefer to give NoMachine access to the VM at the hypervisor level. An example of this type of access would be the way that  QEMU KVM can facilitate VNC access to one of its VMs – no VNC software is installed onto the VM itself, and yet GUI access is facilitated.

There was one forum article which made mention of NoMachine being integrated at the hypervisor level in the future by way of what was called the “NoMachine Virtualization Server” – there was a link provided but it seemed to now be broken as apparently feature requests are no longer published in a publicly viewable manner.

I wonder if anyone has thoughts on how I may be able to go about this.

Thanks in advance for your help!

-Kevin

[Britgirl]

Hi, that scenario is not supported, I’m afraid. We had planned to develop our own Virtualization Server, but with so many options on the market at the time, we decided to invest efforts in developing our current product suite (for example, Cloud Server which besides functioning as the gateway to your infrastructure is also a powerful remote access management tool). We also invested efforts in improving NoMachine’s interoperability with the multitude of hypervisors already available (not just physical workstations) as well cloud-based platforms. Indeed all NoMachine products integrate seamlessly with VMware, Virtualbox, Proxmox and other hypervisor solutions, as well as cloud providers such as AWS EC2, Amazon WorkSpaces Core, Azure, and Google Cloud Platform for example.

[kevin.poole]

Thanks for the response Britgirl.

That makes sense.

When you mention NoMachine’s interoperability with other hypervisors, can you confirm whether you are just referring to the fact that products like NoMachine Desktop can be installed onto VM’s managed by those hypervisors? Or is there in fact some sort of direct hypervisor integration that you are alluding to?

As I’ve continued to explore, I am currently thinking I might be able to use NoMachine Terminal Server paired with a custom session to accomplish what I am trying to do. For anyone in the future who may read this and be interested, the setup becomes something like:

> Server runs VM using QEMU with exposed VNC server to the managed VM

> Install NoMachine Terminal Server and ensure necessary components are present to facilitate VNC (vncviewer, vncserver, etc.)

> Connect to NoMachine Terminal Server and use a custom session which executes a command similar to “vncviewer -fullscreen …”

[Britgirl]

When you mention NoMachine’s interoperability with other hypervisors, can you confirm whether you are just referring to the fact that products like NoMachine Desktop can be installed onto VM’s managed by those hypervisors?

That’s right.

I am currently thinking I might be able to use NoMachine Terminal Server paired with a custom session to accomplish what I am trying to do.

Take a look at the article here: https://kb.nomachine.com/AR10K00720. NoMachine supports VNC sessions. You need to enable VNC on the TS/ETS host first and then you will be able to run a VNC session to the VM. In the ‘VNC remote desktop’ panel, provide the IP or hostname of the VNC server and port to continue. In the next panel you will be requested to provide username and password to login to the VNC server.

[Author]

Posts