Bug #2254

sunstone vnc proxy can't connect to my kvm vnc ports

Added by Adam Heath almost 8 years ago. Updated almost 8 years ago.

Status:ClosedStart date:07/31/2013
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Sunstone
Target version:-
Resolution:worksforme Pull request:
Affected Versions:OpenNebula 4.2

Description

After fixing the problems in the previous report(2253), the vnc proxy attempts to connect to the vnc port opened by kvm. However, the kvm is only listening on localhost, not globally.

opennebula
root@opennebula:/etc/one# tail -n2 /var/log/one/novnc.log
1: connecting to: virt-1.*************:6539
1: handler exception: [Errno 111] Connection refused
virt-1..*************
root@virt-1:/var/log/libvirt/qemu# netstat -anp|grep 6539
tcp 0 0 127.0.0.1:6539 0.0.0.0:* LISTEN 24839/kvm ==

I do not see a reason to reconfigure libvirt/qemu/kvm to listen on 0.0.0.0 for those vnc ports. virt-manager can proxy vnc over the ssh connection, why can't opennebula?

History

#1 Updated by Ruben S. Montero almost 8 years ago

  • Status changed from Pending to Closed
  • Resolution set to worksforme

virtmanager and KVM runs on the same host. That's not the case for OpenNebula that operates in a distributed setting.

Also available in: Atom PDF