New Question

Nano Server won't boot

asked 2016-06-03 11:50:05 +0300

tictoc gravatar image

Using I created a nano.vhdx and imported it into my Mitaka Openstack.

Just continually reboots with Inaccessible Boot Device ...

All of my other images work fine so little lost on what to check.

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted

answered 2016-06-03 14:51:15 +0300

avladu gravatar image

updated 2016-06-03 14:57:01 +0300


please make sure you have the virtio drivers installed, in case you are using KVM. This can be achieved by setting the correct platform when you generate the image:

Moreover, if you are using KVM, the processor flags must be compatible. You may need to set a comptible cpu-model or the following conf value in the nova compute node, in nova.conf:


The reason behind this behavior is that the kvm cpu models(kvm64/qemu64) do not offer to the Windows 10 / Nano VM the required CPU capabilities: cx16, lahf_lm and PrefetchW(3dnow -- already emulated). More info here: .



edit flag offensive delete link more


PERFECT! Openstack Mitaka and Nano are running happily! Thank you!! I would add this into your Openstack Nano howto's as most of the RDO users are either QEMU or KVM. I run a nested Openstack under an ESXI server as well. Thanks Again!!!

tictoc gravatar imagetictoc ( 2016-06-04 03:29:46 +0300 )edit

Great! We will make sure to add the how'to s for kvm. Please mark the the answer as correct, if it answered your question, so that others may find it easier.

avladu gravatar imageavladu ( 2016-06-07 15:29:49 +0300 )edit

Your Answer

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

Add Answer

Question Tools

1 follower


Asked: 2016-06-03 11:50:05 +0300

Seen: 2,872 times

Last updated: Jun 03 '16