Hi Prasanna, Good day to you, and thank you for your e-mail.
On Mon, Jul 15, 2013 at 5:57 PM, Prasanna Santhanam <t...@apache.org> wrote: > On Mon, Jul 15, 2013 at 04:45:34PM +0800, Indra Pramana wrote: > > Hi Prasanna and all, > > > > I managed to work out on how to assign public IP to the VM instance using > > static NAT. > > > > However, I am still stuck with the console proxy time-out issue. It seems > > that my problem is exactly the one mentioned on this bug reported to > JIRA: > > > > > https://issues.apache.org/jira/browse/CLOUDSTACK-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel > > > > May I know whether there's any resolution to the bug above? The issue > seems > > to be identical to the one I am facing right now. > > > > Any other way on how to console in to the newly created VM other than > using > > the console proxy method? Unlike system VM, the instance VM doesn't give > > any link local address which I can SSH directly from the KVM host. Am I > > able to using virsh command to log in to the instance? > > Yup - virsh console to your domain would work. But is unsuitable for > users/tenants of the cloudstack deployment. I'll defer to someone with > more knowledge about the console-proxy issue. > I managed to find out the reason why the console-proxy didn't work. I set up Google's DNS servers (8.8.8.8 and 8.8.4.4) as Internal DNS 1 and 2 during zone creation since we don't have our own internal DNS server. This caused a routing entry on the CPVM for 8.8.8.8 and 8.8.4.4 to the internal network interface of the VM, causing the CPVM not able to resolve domains within the VM, resulting to the issue. I did a "route del" of the two entries from the VM's routing table and it resolves the problem. /sbin/route del -host 8.8.4.4 gw 10.19.16.1 /sbin/route del -host 8.8.8.8 gw 10.19.16.1 Thank you.
