[ https://issues.apache.org/jira/browse/CLOUDSTACK-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483431#comment-13483431 ]
Wido den Hollander commented on CLOUDSTACK-410: ----------------------------------------------- This should not be required anymore, but I think I bumped into this one as well. I did a commit some time ago which would use the Hypervisor IP for setting the VNC address in the domain XML: https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commitdiff;h=bc94948e0604e0e5931759be3c3d3155e84686f6 I'll look into this, since my commit should make changing vnc_listen in qemu.conf obsolete. > vnc_listen not configured in qemu.conf for Ubuntu KVM host > ---------------------------------------------------------- > > Key: CLOUDSTACK-410 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-410 > Project: CloudStack > Issue Type: Bug > Components: Install and Setup, KVM > Affects Versions: 4.0.0 > Reporter: Kirk Kosinski > Assignee: Wido den Hollander > Labels: ubuntu > Fix For: 4.0.0 > > > The vnc_listen configuration in /etc/libvirt/qemu.conf is left at the default > (commented out) for Ubuntu KVM hosts. The VNC console for VMs will listen on > the default of 127.0.0.1:59XX and will not be accessible to the Console Proxy > VM. I noticed this when using the CloudStack-non-OSS-4.0.0-24 build. > To reproduce: > 1. Install Ubuntu 12.04.1 Server, install updates. > 2. Install CloudStack agent on host (run install.sh with "A" option). > 3. Add the host to CloudStack. > 4. Launch a VM on the Ubuntu host and try to access the console. The error > will be: > Unable to start console session as connection is refused by the machine you > are accessing > 5. Check "netstat -plnt" on the KVM host to see the VNC session on > 127.0.0.1:59XX. -- 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