Ask Your Question

nova boot gives error after spawning

asked 2015-12-06 17:23:09 -0500

abdelhamid gravatar image

nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --security-group default --key-name mykey demo-instance

/var/log/noav/nova-scheduler.log shows that sync secessufully i don't reallly know the problem, is it necessary to use net id?

edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted

answered 2015-12-06 21:44:07 -0500

Bipin gravatar image


try with net-id.

nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --security-group default --nic net-id=<your-private-net-id> --key-name mykey demo-instance


edit flag offensive delete link more

answered 2015-12-07 02:28:23 -0500

RHK gravatar image

updated 2015-12-07 05:09:46 -0500

If you have multiple networks with out net-id you may get this error,

ERROR: Multiple possible networks found, use a Network ID to be more specific. (HTTP 400) (Request-ID: req-...)

then you have to select the which network you want to use. Check with neutron net-list it will show all networks.


edit flag offensive delete link more

answered 2015-12-07 07:26:45 -0500

abdelhamid gravatar image

Thank you very much for your quick replies. As for neutron net-list it shows nothing, that's bcs i didn't deploy neutron, i have only one interface which is <eth0 :="""">. i followed the installation guide for openstack liberty in the officiel site and in the section of adding network service (neutron) i found that they use a public ip address, which i don't have, so i skiped that part bcs i read that i can lauch instance isolated meaning without a network service. but i would like to use neutron, can i do that with only 1 interface(eth0 : management niterface) ?

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2015-12-06 17:23:09 -0500

Seen: 232 times

Last updated: Dec 07 '15