Open Stack

I think I had the same issue before.

Check you LVM partitions. I would guess if you are using Packstack that your volume size is too small. You may have to increase the size of the partition that openstack is using to store instances.

You can check the sizes with the below commands:
# pvdisplay    -physical volumes
# lvdisplay     -logical volumes
# vgdisplay    -volume groups


________________________________
 From: Wangpan <hzwangpan at corp.netease.com>
To: Brandon Adams <brandon.adams at newwave-technologies.com>; openstack <openstack at lists.launchpad.net> 
Sent: Thursday, July 25, 2013 10:39 AM
Subject: Re: [Openstack] Help with spawning VMs
 


   
Hi Brandon,
Does there have other error log in the compute log?
this is just a warning log, may not this causes the VM sticks in spawning 
status.
 
2013-07-25

________________________________
 
Wangpan

________________________________
 
发件人：Brandon Adams 
<brandon.adams at newwave-technologies.com>
发送时间：2013-07-25 02:55
主题：[Openstack] Help with 
spawning VMs
收件人："openstack"<openstack at lists.launchpad.net>
抄送：
 
Hi everyone,
First time doing this so bear with me here. I'm 
trying to launch instances with my Packstack install of Open Stack, single-node 
installation. Whenever I launch a VM, it always gets stuck spawning. When I 
check the compute.log file, it gives me this:

2013-07-24 14:23:01.520 
AUDIT nova.compute.claims [req-deed723b-e518-47da-a2c1-2d688c8c53f4 
19cdb5980cd14a60ac488df4eee0eb96 f445e3e9b64742d4929ae2469e9ba04a] [instance: 
1c5055d0-3262-409e-81d6-8293b343c806] CPU limit: 64 VCPUs, free: 62 
VCPUs
2013-07-24 14:23:01.520 AUDIT nova.compute.claims 
[req-deed723b-e518-47da-a2c1-2d688c8c53f4 19cdb5980cd14a60ac488df4eee0eb96 
f445e3e9b64742d4929ae2469e9ba04a] [instance: 
1c5055d0-3262-409e-81d6-8293b343c806] Claim successful
2013-07-24 
14:23:02.652 INFO nova.virt.libvirt.driver 
[req-deed723b-e518-47da-a2c1-2d688c8c53f4 19cdb5980cd14a60ac488df4eee0eb96 
f445e3e9b64742d4929ae2469e9ba04a] [instance: 
1c5055d0-3262-409e-81d6-8293b343c806] Creating image
2013-07-24 14:23:06.226 
INFO nova.virt.libvirt.driver [req-deed723b-e518-47da-a2c1-2d688c8c53f4 
19cdb5980cd14a60ac488df4eee0eb96 f445e3e9b64742d4929ae2469e9ba04a] [instance: 
1c5055d0-3262-409e-81d6-8293b343c806] Injecting key into image 
6663c7cd-10e9-44ee-8d73-6be11195c17f
2013-07-24 14:23:10.157 WARNING 
nova.virt.disk.api [req-deed723b-e518-47da-a2c1-2d688c8c53f4 
19cdb5980cd14a60ac488df4eee0eb96 f445e3e9b64742d4929ae2469e9ba04a] Ignoring 
error injecting key into image (aug_get: no matching node)
2013-07-24 
14:23:16.528 6147 AUDIT nova.compute.resource_tracker [-] Auditing locally 
available compute resources
2013-07-24 14:23:16.588 6147 AUDIT 
nova.compute.resource_tracker [-] Free ram (MB): 9263
2013-07-24 14:23:16.588 
6147 AUDIT nova.compute.resource_tracker [-] Free disk (GB): -71
2013-07-24 
14:23:16.588 6147 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 
1
2013-07-24 14:23:16.666 6147 INFO nova.compute.resource_tracker [-] 
Compute_service record updated for 
localhost.localdomain:localhost.localdomain

The important bit is 
obviously at the bottom. It seems like it is incorrectly thinking that I have 
run out of disk space, which is not the case. It continues to spin indefinitely. 
In addition, none of these instances are able to be deleted either. I can 
provide more information when necessary. Can anyone help me out? 
Thanks.

Brandon

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack at lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130724/148ffaae/attachment.html>