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