{"id":956,"date":"2020-04-28T02:15:18","date_gmt":"2020-04-28T02:15:18","guid":{"rendered":"http:\/\/www.tech-g.com\/?p=956"},"modified":"2023-11-21T20:16:39","modified_gmt":"2023-11-21T20:16:39","slug":"connecting-to-windows-kvm-with-vnc-and-putty-tunnel","status":"publish","type":"post","link":"https:\/\/www.voodoo.business\/blog\/2020\/04\/28\/connecting-to-windows-kvm-with-vnc-and-putty-tunnel\/","title":{"rendered":"Connecting to Windows KVM with VNC and putty tunnel"},"content":{"rendered":"\n

The setup assumed in this post is as follows, you are working on a remote windows computer, there is a Linux KVM host computer running guest virtual machines somewhere (OS of guest irrelevant), and you would like to connect to a guest machine’s console (which may be running windows, linux, macOS, or any operating system)<\/p>\n\n\n\n

KVM, by default only allows people to connect through VNC to the console of a virtual machine if they are using the local host computer, so here are the tips on creating a tunnel to the host computer and connecting to your KVM virtual machine.<\/p>\n\n\n\n

Windows does not support VNC very well, (Most VNC servers don’t run well on windows), but the VNC server here is not windows, it is KVM that is providing the VNC server to the guest’s console.<\/p>\n\n\n\n

1- Create a tunnel (Putty on windows), simply put, save the connection<\/strong> in putty to that host machine, then under tunnels you will need to have something like this (And go back and hot save again)<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Just create a tunnel for port 5900 and the destination localhost:5900 (5901 for the second virtual machine and so on), leave all other tunnel options unchecked\/default<\/p>\n\n\n\n

2- to know which ones are enabled on your machine run this command<\/p>\n\n\n\n

netstat -tlpn | grep 590<\/pre>\n\n\n\n
3- VNC should now connect to localhost:9500 for example (I am using tightVNC on windows), and that connection should be automatically router to the KVM host, which will display the guest’s console depending on the port (every guest has it’s own port)<\/p>\n","protected":false},"excerpt":{"rendered":"
The setup assumed in this post is as follows, you are working on a remote windows computer, there is a Linux KVM host computer running guest virtual machines somewhere (OS of guest irrelevant), and you would like to connect to a guest machine’s console (which may be running windows, linux, macOS, or any operating system) […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[140,4,139,193],"tags":[],"class_list":["post-956","post","type-post","status-publish","format-standard","hentry","category-kvm","category-linux","category-virtualization-linux","category-vnc"],"_links":{"self":[{"href":"https:\/\/www.voodoo.business\/blog\/wp-json\/wp\/v2\/posts\/956","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.voodoo.business\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.voodoo.business\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.voodoo.business\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.voodoo.business\/blog\/wp-json\/wp\/v2\/comments?post=956"}],"version-history":[{"count":6,"href":"https:\/\/www.voodoo.business\/blog\/wp-json\/wp\/v2\/posts\/956\/revisions"}],"predecessor-version":[{"id":3001,"href":"https:\/\/www.voodoo.business\/blog\/wp-json\/wp\/v2\/posts\/956\/revisions\/3001"}],"wp:attachment":[{"href":"https:\/\/www.voodoo.business\/blog\/wp-json\/wp\/v2\/media?parent=956"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.voodoo.business\/blog\/wp-json\/wp\/v2\/categories?post=956"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.voodoo.business\/blog\/wp-json\/wp\/v2\/tags?post=956"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}