Hi Jerry,
Thanks for this information. Is it related to CS 4.2 or early releases?
We will look into it.
-Cindy
On 8/1/13 6:51 PM, Jerry Jiang jerry.ji...@sjcloud.cn wrote:
Hi Cindy,
I faced the same issue days ago, and asked in this mail thread.
It seems there is CS bug in basic network.
Hi Swamy,
Thanks. I checked the below configuration on router VM.
1. The VM's MAC and IP indeed being recorded in /etc/dhcphosts.txt file
correctly;
2. The DHCP range configuration in /etc/dnsmasq.conf is below (seems to me
it is not correctly configured):
Dhcp-range=10.60.176.1, static
In my
Hi Cindy,
I faced the same issue days ago, and asked in this mail thread.
It seems there is CS bug in basic network. You could try with advanced
network to see the bug is there or not.
Thanks
-Jerry
-邮件原件-
发件人: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
发送时间: 2013年8月2日 星期五
Have you tried to bring-up eht0 and restart the network service?
Just try:
ifconfig eth0 up;
service network restart;
On 2013年08月02日 09:51, Jerry Jiang wrote:
Hi Cindy,
I faced the same issue days ago, and asked in this mail thread.
It seems there is CS bug in basic network. You could try
Hi,
Even I have the same issue. Doing as suggested below only helps
sometimes. But this method doesn't help while automating VM creation
and running scripts after the VM is launched.
Thanks
Sriharsha
Sent from my iPhone
On Aug 1, 2013, at 20:08, Yan Ke yan...@yonyou.com wrote:
Have you
Hi Sriharsha,
Can you check the following on your router?
1. When you start the VM. Do you see the VM's MAC, IP info being recorded
in /etc/dhcphosts.txt file on your router VM?
2. Also please make sure that /etc/dnsmasq.conf on your router contains
the following lines
Dhcp-range=IP From your
Hi Swamy,
Thanks for the reply. I will check on this tomorrow.
Can you please tell me the guidelines for making a template out of a
vm. What configuration changes do we need to make on the vm used for
creating a template.
I also had an extension to this issue. Cloudstack assigns
172.18.145.15
For me, this only occurs after a refresh CentOS 6.4 guest installation. And
I think it's due to CentOS not enabling eht0 by default.
If you're facing the same problem as I mentioned above, just edit the
'/etc/sysconfig/network-scripts/ifcfg-eth0', specify the 'onboot'
properties' value as yes.