VM create fails with "Require both a host and instance NUMA topology to fit instance on host"

asked 2017-01-30 09:00:22 -0600

ravishekar-jethani gravatar image

updated 2017-02-02 09:20:43 -0600

rbowen gravatar image

I am trying to create a multi-node setup by following devstack guide.


I have a base Ubuntu14 laptop running 2 virtualbox based ubuntu16 VMs: "controller" and "compute1". I intentionally disabled nova-compute service on controller just to see a server instance getting created on the compute1 node. But instance creation fails and I see the following in nova scheduler service logs:

2017-01-30 17:19:15.688 DEBUG nova.virt.hardware [req-cc1cc793-3801-4ff1-af6b-3a6f8add7622 demo demo] Require both a host and instance NUMA topology to fit instance on host. from (pid=28618) numa_fit_instance_to_host /opt/stack/nova/nova/virt/hardware.py:1328

Full log: http://paste.openstack.org/show/596898/

I am using the cirros test image that comes with devstack and using "cirros256" flavor for creating instance. Here are the local.conf for controller and compute1 nodes.

When I enable compute service on controller the instance gets created successfully on the controller node. What am I doing wrong?

edit retag flag offensive close merge delete


This doesn't look like an error. Since neither host nor instance have or require a NUMA topology, this method returns immediately. The scheduler log shows that compute1 has been selected.

Any other errors related to req-cc1cc793-3801-4ff1-af6b-3a6f8add7622? Perhaps in the nova-compute.log?

Bernd Bausch gravatar imageBernd Bausch ( 2017-01-31 17:37:32 -0600 )edit

any luck here ?? I am facing similar issue. With Ocata, my instances are getting stuck in "scheduling" state.

vk gravatar imagevk ( 2017-03-14 04:35:13 -0600 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2017-04-06 14:06:41 -0600

ravishekar-jethani gravatar image

Hi, I also faced exactly same issue. The problem: Virtualbox does not support nested virtualization and may not ever support it. That is it does not exposes host's hardware virtualization features into the guest. That is even if you actual hardware and host OS are capable of hardware virtualization your guest OS cannot take advantage of it.

The solution: Use some other hypervisor which supports nested virtualization. Given that you are using Ubuntu14, QEMU/KVM would be your best choice. There is also a quite friendly no fuss GUI. There are many other GUIs but this is simplest to install/maintain and quite close to Virtualbox GUI. Just one problem: graphics hungry OSes like desktop versions Ubuntu or Windows may not run as smoothly as they do in virtualbox. Your .vdi files are also acceptable in kvm but its best to use qcow2 based disks with kvm as they come with many more features.

Caution: Do uninstall virtualbox before installing kvm. Many may suggest that they can be run together with some hacks but it's best to keep only one hypervisor on the system.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2017-01-30 09:00:22 -0600

Seen: 1,239 times

Last updated: Apr 06 '17