concurrent boot lxc instance will cause cpu 100% usage

[Lawrance]

i installed openstack folsom via ubuntu cloud source,below is the source address

cat /etc/apt/source.list
......
deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-proposed/folsom main
deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/folsom main
......

when i concurrent boot lxc instance, the process "libvirt_lxc" will cause cpu 100% usage,and the other instance will be BUILD state.so i have to reboot the host......

top
......
 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
17859 root 20 0 45688 1176 708 R 100 0.0 1:25.74 libvirt_lxc
......

nova list
+--------------------------------------+-------------+--------+----------------------------------+
| ID | Name | Status | Networks |
+--------------------------------------+-------------+--------+----------------------------------+
| 08a0b120-a6e1-4da1-bc8e-04a13349dc0f | instance001 | BUILD | private=172.20.1.46, 172.20.2.44 |
| 0fb75902-d2f7-4401-a01b-47bfedff0a21 | instance001 | BUILD | private=172.20.1.9, 172.20.2.34 |
| 11daba4f-53cf-4286-a29a-088650f0a534 | instance001 | ACTIVE | private=172.20.1.7, 172.20.2.28 |
| 211ae397-7b7d-4cd7-9d60-27eaf7ef31b6 | instance001 | BUILD | private=172.20.1.42, 172.20.2.38 |
| 383629e7-20c7-4109-8532-5670545b29f9 | instance001 | BUILD | private=172.20.1.45, 172.20.2.45 |
| 39543a2c-21d7-4234-babe-54ec491be1ee | instance001 | BUILD | private=172.20.1.40, 172.20.2.40 |
| 3b676875-ae38-483a-bd14-99c163eda0c3 | instance001 | BUILD | private=172.20.1.8, 172.20.2.29 |
| 6ac289fc-8326-4495-ac65-d7efc25d9c75 | instance001 | ACTIVE | private=172.20.1.5, 172.20.2.27 |
| 83eb9cf0-ea28-4da7-b6af-b2e4e7175154 | instance001 | BUILD | private=172.20.1.41, 172.20.2.46 |
| 9c7869c1-6987-4821-9113-55cb66a2381e | instance001 | BUILD | private=172.20.1.11, 172.20.2.43 |
| 9fd246ad-4031-4095-9bf0-76f1f30301ba | instance001 | BUILD | private=172.20.1.10, 172.20.2.39 |
| b241812c-df36-4391-bb24-069f162e36e8 | instance001 | BUILD | private=172.20.1.13, 172.20.2.36 |
| b5cbf092-4042-4f4a-9b02-4ad03c0863c8 | instance001 | BUILD | private=172.20.1.39, 172.20.2.37 |
| bd153f6e-5fbe-4c71-ab76-dd61a502825c | instance001 | BUILD | private=172.20.1.44, 172.20.2.41 |
| d131ab29-df4b-49b5-b5c5-5f2a519fd6ff | instance001 | BUILD | private=172.20.1.12, 172.20.2.35 |
| f30c25a5-fd79-4f25-ba5d-92a4a182a625 | instance001 | BUILD | private=172.20.1.43, 172.20.2.42 |
+--------------------------------------+-------------+--------+----------------------------------+

i think you can test this bug with below oneline script
for i in `seq 16`;do nova boot --flavor 6 --image 160cdfe9-d48c-441c-90bf-48092cb38482 --key_name key01 instance00$i;done

[Justin Shepherd (jshepher)]

Marking this issue as invalid, as it is filed against Folsom, and has not been updated in over a year and a half. If you believe this to be in error, please update this issue.