Ask Your Question

Problem with create centos vm in virtual box

asked 2016-03-18 00:11:07 -0500

zero gravatar image


I use virtual box to setup an allinone env in local machine.

when I use heat template like below, all things go well. I can nova list, and ping the IP of this vm.

heat_template_version: 2013-05-23 resources: instance: type: OS::Nova::Server properties: image: cirros-0.3.4-x86_64-uec flavour: m1.tiny key_name: heat_key

However when I do these process: 1. download image from

  1. glance image-create –name centos6.5 –disk-format=qcow2 –container-format=bare –file=/mnt/image/CentOS-6-x86_64-GenericCloud-1508.qcow2

  2. change template like this way:

heat_template_version: 2013-05-23 resources: instance: type: OS::Nova::Server properties: image: centos flavour: m1.medium key_name: heat_key

  1. heat stack-create -f centos.yaml test

  2. nova list, I can find the IP, but it unreachable and I can not use ssh neither.

  3. I use nova console-log check the vm create log, it does not show anything. I try to logon the centos vm, but it fails.

which step am I wrong?

in fact, I want to play with cloud-init, but the first step is try to create a vm with cloud-init. the cirros-0.3.4-x86_64-uec seem without cloud-init inside.

is there any other way to solve the problem?

edit retag flag offensive close merge delete


Im seeing that you use the name centos at rhe yml file and the image is called centos6.5. Try using the id, and add set a network resource at the file. Regards

Eduardo Gonzalez gravatar imageEduardo Gonzalez ( 2016-03-18 00:56:37 -0500 )edit

1 answer

Sort by » oldest newest most voted

answered 2016-05-19 16:37:24 -0500

zaneb gravatar image

It's quite likely that the ssh username is different for different images (not to mention the behaviour here is different across different versions of Heat, check the config file for details).

However, if the IP is unreachable, it may be that the VM failed to boot. Or it may just be taking forever, because it's likely using qemu instead of kvm directly (i.e. an SW emulator, not full HW virtualisation).

Honestly, nested virtualisation is a dicey prospect at the best of times, and VirtualBox is basically a toy. Mixing them is almost certainly not going to work for any practical purposes.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2016-03-18 00:11:07 -0500

Seen: 249 times

Last updated: May 19 '16