[Openstack] Unable to see console using VNC on ESX hypervisor

Gary Kotton gkotton at vmware.com
Thu Nov 21 15:37:48 UTC 2013


Hi,
Yes, Yaguang you are correct. The console output is not supported. In Havana we added a log message to indicate that it is not support. There are changes proposed in Icehosue to say that this is not supported.
Thanks
Gary

From: Yaguang Tang <heut2008 at gmail.com<mailto:heut2008 at gmail.com>>
Reply-To: "heut2008 at gmail.com<mailto:heut2008 at gmail.com>" <heut2008 at gmail.com<mailto:heut2008 at gmail.com>>
Date: Thursday, November 21, 2013 5:12 PM
To: Rajshree Thorat <rajshree.thorat at gslab.com<mailto:rajshree.thorat at gslab.com>>
Cc: "openstack at ask.openstack.org<mailto:openstack at ask.openstack.org>" <openstack at ask.openstack.org<mailto:openstack at ask.openstack.org>>, "openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>" <openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>>
Subject: Re: [Openstack] Unable to see console using VNC on ESX hypervisor


2013年11月21日 下午10:02于 "Yaguang Tang" <heut2008 at gmail.com<mailto:heut2008 at gmail.com>>写道:
>
> Grizzly openstack doesn't support vnc console with ESX driver.

sorry, i mean  vnc console log is not supported.
>
> 2013年11月21日 下午9:43于 "Rajshree Thorat" <rajshree.thorat at gslab.com<mailto:rajshree.thorat at gslab.com>>写道:
>
>> Hi All,
>>
>> I have configured OpenStack Grizzly to control ESX hypervisor. I can successfully launch instances but unable to see its console using VNC.
>>
>> Following is my configuration.
>>
>> ***Compute node :
>>
>> nova.conf for vnc:
>>
>> vnc_enabled = true
>> novncproxy_base_url=http://public_ip_of_controller:6080/vnc_auto.html<https://urldefense.proofpoint.com/v1/url?u=http://public_ip_of_controller:6080/vnc_auto.html&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0A&m=e%2BJeoge0j7b5ZWkd83QV3NqqCIjj7p%2BB4RP1JtYo7Lw%3D%0A&s=eb8057f245e92c7ab335fa466e326e95ccc8fdb0fb904f2c189453769bef9940>
>> novncproxy_port=6080
>> vncserver_proxyclient_address=management_ip_of_compute
>> vncserver_listen=0.0.0.0
>>
>> ***Controller node:
>>
>> nova.conf for vnc:
>>
>> novncproxy_base_url=http://public_ip_of_controller:6080/vnc_auto.html<https://urldefense.proofpoint.com/v1/url?u=http://public_ip_of_controller:6080/vnc_auto.html&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0A&m=e%2BJeoge0j7b5ZWkd83QV3NqqCIjj7p%2BB4RP1JtYo7Lw%3D%0A&s=eb8057f245e92c7ab335fa466e326e95ccc8fdb0fb904f2c189453769bef9940>
>> novncproxy_port=6080
>> vncserver_proxyclient_address=management_ip_of_controller
>> vncserver_listen=0.0.0.0
>>
>> root at openstk2:~# tail /var/log/nova/nova-consoleauth.log
>> 2013-11-21 18:40:35.228 7570 AUDIT nova.service [-] Starting consoleauth node (version 2013.1.3)
>> 2013-11-21 18:40:35.395 INFO nova.openstack.common.rpc.common [req-179d456d-f306-426f-b65e-242362758f73 None None] Connected to AMQP server on controller_ip:5672
>> 2013-11-21 18:42:34.012 AUDIT nova.consoleauth.manager [req-ebc33f34-f57b-492b-8429-39eb3240e5d7 a8f0e9af6e6b4d08b1729acae0510d54 db63e4a448fc426086562638726f9081] Received Token: 1bcb7408-5c59-466d-a84d-528481af3c37, {'instance_uuid': u'969e49b0-af3f-45bd-8618-1320ba337962', 'internal_access_path': None, 'last_activity_at': 1385039554.012067, 'console_type': u'novnc', 'host': u'ESX_host_IP', 'token': u'1bcb7408-5c59-466d-a84d-528481af3c37', 'port': 6031})
>> 2013-11-21 18:42:34.015 INFO nova.openstack.common.rpc.common [req-ebc33f34-f57b-492b-8429-39eb3240e5d7 a8f0e9af6e6b4d08b1729acae0510d54 db63e4a448fc426086562638726f9081] Connected to AMQP server on controller_ip:5672
>> 2013-11-21 18:42:34.283 AUDIT nova.consoleauth.manager [req-518ed47e-5d68-491d-8c57-16952744a2d8 None None] Checking Token: 1bcb7408-5c59-466d-a84d-528481af3c37, True)
>> 2013-11-21 18:42:35.710 AUDIT nova.consoleauth.manager [req-2d65d8ac-c003-4f4d-9014-9e8995794ad6 None None] Checking Token: 1bcb7408-5c59-466d-a84d-528481af3c37, True)
>>
>> With same configuration I can connect to vm's console on KVM setup. Is there any other setting to access console for ESX hypervisor?
>>
>> Any help would be highly appreciated.
>>
>> Thanks in advance,
>>
>> Regards,
>> Rajshree
>>
>>
>>
>>
>> _______________________________________________
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack<https://urldefense.proofpoint.com/v1/url?u=http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0A&m=e%2BJeoge0j7b5ZWkd83QV3NqqCIjj7p%2BB4RP1JtYo7Lw%3D%0A&s=25aa91a892c861cc6777f1948aa46a76ef0dcf16f0e3645e8d44441459b77dab>
>> Post to     : openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack<https://urldefense.proofpoint.com/v1/url?u=http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0A&m=e%2BJeoge0j7b5ZWkd83QV3NqqCIjj7p%2BB4RP1JtYo7Lw%3D%0A&s=25aa91a892c861cc6777f1948aa46a76ef0dcf16f0e3645e8d44441459b77dab>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20131121/fc94f244/attachment.html>


More information about the Openstack mailing list