Open Stack

novncproxy_base_url=http://10.2.1.1:6080/vnc_auto.html # I think the ip here should be the public ip address that you can connect from your browser or telnet from your pc, not the private ip of your server.
vncserver_proxyclient_address=10.2.1.2 {IP of the local compute host here} # that is right here, 
vncserver_listen=0.0.0.0  # this ok too

here is my nova.conf:
vncserver_proxyclient_address=10.120.40.11  # private ip of the host/compute node
vncserver_listen=10.120.40.11 # private ip of the host/compute node, this will be used to create the libvirt.xml and you can see it by 'virsh dumpxml'
novncproxy_base_url=http://114.113.XXX.XXX:6080/vnc_auto.html  # the public ip address you can access


2013-01-25



Wangpan



发件人：John Barbee
发送时间：2013-01-25 10:21
主题：Re: [Openstack] Problem with VNC on compute node
收件人："Wangpan"<hzwangpan at corp.netease.com>
抄送："longeek"<mengql112233 at gmail.com>,"openstack"<openstack at lists.launchpad.net>

Here is my VNC config in nova.conf


My controller is 10.2.1.1. I modify vncserver_proxyclient_address to the static ip of each compute host rather than using 127.0.0.1. Not sure that matters, I have never tried 127.0.0.1. 
# Vnc configuration
novnc_enabled=true
novncproxy_base_url=http://10.2.1.1:6080/vnc_auto.html
novncproxy_port=6080
 vncserver_proxyclient_address=10.2.1.2 {IP of the local compute host here}
 vncserver_listen=0.0.0.0

--

Thanks,
John

On Jan 24, 2013, at 8:55 PM, Wangpan <hzwangpan at corp.netease.com> wrote:


Hi longeek & Russi,
I have some suggestions about the vnc issue of vm,
1. you can use 'sudo virsh dumpxml instance-uuid' to check the ip and port vnc bound, seems like this:
    <graphics type='vnc' port='5903' autoport='yes' listen='XXX.XXX.XXX.XXX' keymap='en-us'>
      <listen type='address' address='XXX.XXX.XXX.XXX'/>
    </graphics>
2. you should check the vnc connection to vm is ok or not by using vnc client, such as 'RealVNC viewer', and connect vm by using the ip and port in step 1, if it is OK here, the problem may occur in novnc service, the process on my host is like this '/usr/bin/python /usr/bin/nova-novncproxy --config-file=/etc/nova/nova.conf --web /usr/share/novnc/'

As your description, the error is "Failed to connect to server (code: 1006)", so I guess the problem may be the ip and port vnc bound can not be connect.
good luck!

2013-01-25



Wangpan



发件人：longeek
发送时间：2013-01-25 09:24
主题：Re: [Openstack] Problem with VNC on compute node
收件人："openstack"<openstack at lists.launchpad.net>
抄送：

Hi, 
   I also get the same issuse, I have check the vnc config in nova config.
   Can anybody tell us about why this and how the horizon access the vnc?

Tks,
Best Regards,

--------------------------------------------
Lawrency Meng
mail: mengql112233 at gmail.com

于 01/24/2013 12:27 AM, Guilherme Russi 写道:

Hello guys,

 I'm installing the folsom version and I have one computer like the controller and one being the compute node. I can start the VM with cirros OS but I can't use the VNC, I got the error: "Failed to connect to server (code: 1006)". I've been following this tutorial: http://docs.openstack.org/folsom/basic-install/content/basic-install_compute.html.

Can anybody help me?

Thank you and regards.

Guilherme.

 

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack at lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp




-- 

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack at lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack at lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130125/0f10139f/attachment.html>