[one-users] Strange IP assigning

[fanttazio]

I did what you said and now it works.
Mehdi

On Sun, Jun 19, 2011 at 5:29 PM, Carlos A. <caralla at upv.es> wrote:

> **
> I think that I had that problem before: when the script is ran, the
> interfaces are already up (because of the ubuntu quick-boot; read-ahead?).
> The result is that you must stop and start again the interfaces once the
> interfaces file has been created.
>
> Try to put in the script a pair of lines such as (for each interface you
> need; I do not know which context script are you using):
>
> ifconfig eth0 down
> ifup eth0
>
> just after the interfaces script has been generated.
>
> Moreover you should delete the /etc/udev/rules.d/70-persistent-net.rules
> file just before releasing the image i.e. the last line before stating a
> poweroff in the image that you are going to use as ONE image should be
>
> $ rm /etc/udev/rules.d/70-persistent-net.rules
>
> I hope this helps you
>
> Regards,
> Carlos A.
>
> El 19/06/2011 18:14, fanttazio escribió:
>
> onevnet shows that the one MAC address has been leased. In VM even the in
> interface configuration I see that the IP has been written correctly but the
> ifconfig output shows something different. but after I restart the network
> service it assigns the correct IP. Could it be for run level of the script?
> I put it in rc2 as it says in the document.
>
> On Sun, Jun 19, 2011 at 4:47 PM, Steven Timm <timm at fnal.gov> wrote:
>
>> I've seen that happen when the virtual network is out of network
>> leases.. what does onevnet show tell you.  Also it can
>> happen if the template specifies some nonesense option for the network,
>> then ONE will just give you something really random.
>>
>> Steve
>>
>>
>> On Sun, 19 Jun 2011, fanttazio wrote:
>>
>>  Hi to all,
>>>
>>> I have created a small cloud finally. front-end and hosts are all Ubuntu
>>> 10.04 (KVM virtualisation). I can run VM but when it boots, it assigns an
>>> strange IP despite the MAC address that ONE has given to VM but when I
>>> reboot VM it sets the correct IP. so for every VM I have to reboot it
>>> once
>>> to get the correct IP. I used the script that is provided on the site
>>> (net-context). Any Idea why it acts like that?
>>>
>>> Regards,
>>> Mehdi
>>>
>>>
>>   --
>> ------------------------------------------------------------------
>> Steven C. Timm, Ph.D  (630) 840-8525
>> timm at fnal.gov  http://home.fnal.gov/~timm/
>> Fermilab Computing Division, Scientific Computing Facilities,
>> Grid Facilities Department, FermiGrid Services Group, Group Leader.
>> Lead of FermiCloud project.
>>
>
>
> _______________________________________________
> Users mailing listUsers at lists.opennebula.orghttp://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20110619/4520f11f/attachment-0003.htm>