openstack team mailing list archive

[Marton Kiss <marton.kiss@xxxxxxxxx>]

Are you using devstack or a package based deployment?

M.

2012/4/15 Salman Malik <salmanmk@xxxxxxxx>:
> I haven't edited nova-compute.conf. Can you please tell me where to look for
> it ?
>
> Thanks,
> Salman
>
>> Date: Sun, 15 Apr 2012 07:00:12 +0200
>
>> Subject: Re: [Openstack] Unable to ping launched Instance
>> From: marton.kiss@xxxxxxxxx
>> To: salmanmk@xxxxxxxx
>> CC: openstack@xxxxxxxxxxxxxxxxxxx
>>
>> Hi,
>>
>> It's a tricky issue. I bet you have a different libvirt_type setting
>> in your nova.conf and separate nova-compute.conf. I experienced the
>> same, and spent 2 days to tracking what could be wrong with libvirt
>> that starting instances randomly going into no state.
>>
>> Regards,
>> Márton Kiss, CTO
>> Xemeti
>>
>> 2012/4/15 Salman Malik <salmanmk@xxxxxxxx>:
>> > Thanks Marton for the advice. I actually already had the
>> > libvirt_type=qemu,
>> > and since I did not have '--' before any of the lines in nova conf, I
>> > added
>> > that before the libvirt_type line. Then, I rebooted the VM and started
>> > rejoin-stack.sh to start the services again. But now when I launch an
>> > instance I get status: Error , Task: Spawning and Power State: no State.
>> >
>> > Any other thoughts as to what might be wrong ?
>> > (The log for the instance says : "Unable to get log for instance
>> > "90bf00e8-6ece-4978-aa16-1b68f34bf44e"."   Possibly because machine
>> > never
>> > went up ?)
>> >
>> > Thanks,
>> > Salman
>> >
>> >
>> >
>> >
>> >> Date: Sun, 15 Apr 2012 05:35:14 +0200
>> >> Subject: Re: [Openstack] Unable to ping launched Instance
>> >> From: marton.kiss@xxxxxxxxx
>> >> To: salmanmk@xxxxxxxx
>> >> CC: openstack@xxxxxxxxxxxxxxxxxxx
>> >
>> >>
>> >> Hi,
>> >>
>> >> Try qemu instead of kvm, and it'll work inside a virtualbox vm, Change
>> >> the following nova config option:
>> >> --libvirt_type=qemu
>> >>
>> >> Regards,
>> >> Márton Kiss, CTO
>> >> Xemeti
>> >>
>> >> 2012/4/15 Salman Malik <salmanmk@xxxxxxxx>:
>> >> > Hi Guys,
>> >> >
>> >> > I have launched an instance using dashboard. The 'intances and
>> >> > volume'
>> >> > tab
>> >> > shows that the instance is in active status and power state = running
>> >> > (
>> >> > IP
>> >> > address = 10.0.0.3).
>> >> > But when I click on the instance name and go to see the logs, there
>> >> > are
>> >> > no
>> >> > logs (nothing in 'view full log' as well) and the Instance's VNC
>> >> > console
>> >> > shows:
>> >> >
>> >> > "This kernel requires x86-64 CPU, but only detected an i686 CPU.
>> >> > Unable
>> >> > to
>> >> > boot - please use a kernel appropriate for your CPU"
>> >> >
>> >> > I have had the same problem and the proposed solution that I found
>> >> > was
>> >> > to
>> >> > enable virtualization in BIOS. But I am running the devstack on a
>> >> > VirtualBox
>> >> > VM and thus can not enable that in BIOS. Since stack.sh is supposed
>> >> > to
>> >> > run
>> >> > on VMs, can someone propose a solution ?
>> >> >
>> >> > Thanks in advance,
>> >> > Salman
>> >> >
>> >> > _______________________________________________
>> >> > Mailing list: https://launchpad.net/~openstack
>> >> > Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> >> > Unsubscribe : https://launchpad.net/~openstack
>> >> > More help   : https://help.launchpad.net/ListHelp
>> >> >