[ https://issues.apache.org/jira/browse/CLOUDSTACK-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735580#comment-13735580 ]
ASF subversion and git services commented on CLOUDSTACK-3495: ------------------------------------------------------------- Commit 4333209af36ca001ca88935ddf2b4d981cc0150e in branch refs/heads/master from [~antbryan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4333209 ] CLOUDSTACK-3495 CS used to access vnc server in xenserver dom0 to get VM console, now CS moves to use XenServer console API. getvncport plugin is not needed any more. remove the code related to getvncport in XenServer > xenserver 6.1 and 6.2 can not open vnc console > ---------------------------------------------- > > Key: CLOUDSTACK-3495 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3495 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VNC Proxy, XenServer > Affects Versions: 4.2.0 > Environment: xenserver 6.1 or 6.2 > Reporter: Hongtu Zang > Assignee: Anthony Xu > Labels: console, vnc, xenserver > Fix For: 4.2.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > can not open vnc console in web UI, if hypervisor is xenserver 6.1 or 6.2 > this is because of the path of the vnc-port file is the same with 6.0 but the > vmops code is looking for the pid and port as xenserver 5.x -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira