[rhos-list] Cirros VM image DHCP issues

Rhys Oxenham roxenham at redhat.com
Tue Aug 27 04:48:14 UTC 2013



On 26 Aug 2013, at 20:45, Perry Myers <pmyers at redhat.com> wrote:

> On 08/26/2013 01:28 PM, Prashanth Prahalad wrote:
>> Thanks Rhys/Perry.
>> 
>> To answer your questions:
>> 
>> Rhys - I downloaded the cirros image you mentioned and that did the
>> trick ! The only issue I see is that with the new Cirros 3.1, the VM
>> takes a long time to come up (whereas 3.0 was pretty snappy). If you
>> happen to know, could you point me to the bug or the link which mentions
>> about this issue in Cirros.

Great!

Are you running the metadata service? I suspect that if you're not it is waiting on the metadata service and will eventually time out. Does it give any indication of this upon boot?

Thanks 
Rhys 

>> 
>> Perry - I'm running - 
>> 
>>    [root at controller ~(keystone_admin)]# uname -a
>>    Linux controller 2.6.32-358.114.1.openstack.el6.x86_64 #1 SMP Wed
>>    Jul 3 02:11:25 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux
>> 
>> 
>> Do you think this kernel could have the bug which you were mentioned  ?
>> Could you please reference the bug for this. I would really appreciate
>> this.
> 
> I don't know the bz# offhand, but that kernel is the latest released
> kernel for RHOS and it does have some bugs around using Quantum.  I was
> never able to get guests to get dhcp addresses when using that kernel.
> 
> Instead I have been using:
> http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/epel-6/kernel-2.6.32-358.114.1.openstack.el6.gre.2.x86_64.rpm
> 
> Which unfortunately is only available on RDO right now.  But we will be
> releasing a new RHOS kernel in 3.0 repos in the next few weeks which
> will have the same fixes as what is in RDO.
> 
>> Interestingly, I'm running the same bits on the compute node and that
>> seems fine (the VM picks up the DHCP reply just fine)




More information about the rhos-list mailing list