For me, the CentOS 6.3 template works fine for some of the vm's I
create. For example, if I try creating 10 vm's, 7 of them will be just
fine but the rest 3 are corrupted.

My concern is if the template is wrong it should fail for all 10 vm's
but not just a few of them.


Sent from my iPhone

> On Aug 2, 2013, at 10:18, Chiradeep Vittal <chiradeep.vit...@citrix.com> 
> wrote:
>
> You shouldn't have any other DHCP servers in the network.
> Besides that it seems to be an issue specific to the CentOS template. Did
> the "builtin" Centos 5.3 template work?
>
>> On 8/2/13 9:32 AM, "Cindy Jiang" <cji...@infoblox.com> wrote:
>>
>> Hi Chiradeep,
>>
>> Thanks. "Dhclient eth0" would assign a IP address to my VM, but it is a
>> different IP instead of the IP Address assigned by CS.
>>
>> Moreover, what we are trying to do is to automate the VM provisioning
>> process, similar to what sriharsha said in his email, and the manual
>> enablement with DHCP is not desired…
>>
>> Thanks,
>> Cindy
>>
>>
>>
>>> On 8/1/13 2:50 PM, "Chiradeep Vittal" <chiradeep.vit...@citrix.com> wrote:
>>>
>>> You cannot attach anything or use HTML on Apache mailing lists.
>>> Can you try and bring up the interface up manually
>>> ifconfig eth0 up
>>> dhclient eth0
>>>
>>> Does the "built-in" template work?
>>>
>>>> On 8/1/13 2:45 PM, "Cindy Jiang" <cji...@infoblox.com> wrote:
>>>>
>>>> Somehow I can't attach screenshots. So I copy the outputs of this CentOS
>>>> instance here. As you can see, the ethernet0 interface configuration
>>>> doesn't contain any ip address or default gateway information, even
>>>> though Cloudstack assigns these information correctly.
>>>> [root@localhost network-scripts]# ifconfig
>>>> lo        Link encap:Local Loopback
>>>>         inet addr:127.0.0.1  Mask:255.0.0.0
>>>>         inet6 addr: ::1/128 Scope:Host
>>>>         UP LOOPBACK RUNNING  MTU:16436  Metric:1
>>>>         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>>         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>>         collisions:0 txqueuelen:0
>>>>         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>>>>
>>>> [root@localhost network-scripts]# hostname
>>>> Localhost.localdomain
>>>> [root@localhost network-scripts]# cat ifcfg-eth0
>>>> DEVICE="eth0"
>>>> HWADDR="06:57:6E:00:00:2A"
>>>> NM_CONTROLLED="yes"
>>>> ONBOOT="no"
>>>>
>>>> From: Cindy Jiang <cji...@infoblox.com<mailto:cji...@infoblox.com>>
>>>> Reply-To:
>>>> "users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>"
>>>> <users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>>
>>>> Date: Thursday, August 1, 2013 2:34 PM
>>>> To: "users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>"
>>>> <users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>>,
>>>> Soheil
>>>> Eizadi <seiz...@infoblox.com<mailto:seiz...@infoblox.com>>
>>>> Subject: Re: IP Address assigned by CS is not passed to new instance VM
>>>>
>>>> Attach the screenshots
>>>>
>>>> [cid:CFDFC580-184D-4F0E-AF41-5AF18794D413][cid:7E1641EF-DEBC-4A25-90B3-3
>>>> B
>>>> 1
>>>> 32C1A66B0]
>>>>
>>>> [cid:DA5AC137-FC18-4A63-9367-7583EB1A6940]
>>>>
>>>> From: Cindy Jiang <cji...@infoblox.com<mailto:cji...@infoblox.com>>
>>>> Reply-To:
>>>> "users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>"
>>>> <users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>>
>>>> Date: Thursday, August 1, 2013 2:24 PM
>>>> To: "users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>"
>>>> <users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>>,
>>>> Soheil
>>>> Eizadi <seiz...@infoblox.com<mailto:seiz...@infoblox.com>>
>>>> Subject: IP Address assigned by CS is not passed to new instance VM
>>>>
>>>> Hello,
>>>>
>>>> We are trying to create a new instance with basic networking setup using
>>>> CentOS 6.0 ISO. Cloudstack assigns the correct IP Address (in my case:
>>>> 10.60.176.110) to this new centOS instance, but once you log into this
>>>> VM, check "ifconfig" and "/etc/sysconfig/network-scripts/ifcfg-eth0",
>>>> the
>>>> IP Address and default gateway information are not passed through
>>>> correctly. The same issue with hostname ­ instead of "centos-107", it
>>>> shows as "localhost.localdomain". Please see attached screenshots. Has
>>>> anyone experienced the similar issue?
>>>>
>>>> Our environment:
>>>>
>>>> 1.  CS 4.2
>>>> 2.  XenServer 6.0.2
>>>> 3.  CentOS 6.0 ISO
>>>>
>>>> Thanks,
>>>> Cindy
>

Reply via email to