Unable to launch more than 1 instance in Openstack Mitaka

asked 2018-08-06 07:39:07 -0600

KKK gravatar image

updated 2018-08-06 08:46:20 -0600

Bernd Bausch gravatar image

Hi,

I am having one control node and one compute node. I have installed cinder with 1 TB capacity and launched an instance using that cinder. But I am unable to create more than one VM as it is throwing error "No valid host was found. There are not enough hosts available" but I am having enough CPU, RAM and Volumes. Please help to understand where I am doing mistake in launching instance. My setup supports hardware virutalization(please find screen shot below)

Please find below virt-host-validate output

root@kvmos-ctlnode:~# virt-host-validate
  QEMU: Checking for hardware virtualization                                 : PASS
  QEMU: Checking if device /dev/kvm exists                                   : PASS
  QEMU: Checking if device /dev/kvm is accessible                            : PASS
  QEMU: Checking if device /dev/vhost-net exists                             : PASS
  QEMU: Checking if device /dev/net/tun exists                               : PASS
  QEMU: Checking for cgroup 'memory' controller support                      : PASS
  QEMU: Checking for cgroup 'memory' controller mount-point                  : WARN (Mount 'memory' cgroup controller (suggested at /sys/fs/cgroup/memory))
  QEMU: Checking for cgroup 'cpu' controller support                         : PASS
  QEMU: Checking for cgroup 'cpu' controller mount-point                     : WARN (Mount 'cpu' cgroup controller (suggested at /sys/fs/cgroup/cpu))
  QEMU: Checking for cgroup 'cpuacct' controller support                     : PASS
  QEMU: Checking for cgroup 'cpuacct' controller mount-point                 : WARN (Mount 'cpuacct' cgroup controller (suggested at /sys/fs/cgroup/cpuacct))
  QEMU: Checking for cgroup 'devices' controller support                     : PASS
  QEMU: Checking for cgroup 'devices' controller mount-point                 : WARN (Mount 'devices' cgroup controller (suggested at /sys/fs/cgroup/devices))
  QEMU: Checking for cgroup 'net_cls' controller support                     : WARN (Enable CONFIG_NET_CLS_CGROUP in kernel Kconfig file)
  QEMU: Checking for cgroup 'blkio' controller support                       : PASS
  QEMU: Checking for cgroup 'blkio' controller mount-point                   : WARN (Mount 'blkio' cgroup controller (suggested at /sys/fs/cgroup/blkio))
  QEMU: Checking for device assignment IOMMU support                         : PASS
  QEMU: Checking if IOMMU is enabled by kernel                               : WARN (IOMMU appears to be disabled in kernel. Add intel_iommu=on to kernel cmdline arguments)
   LXC: Checking for Linux >= 2.6.26                                         : PASS
   LXC: Checking for namespace ipc                                           : PASS
   LXC: Checking for namespace mnt                                           : PASS
   LXC: Checking for namespace pid                                           : PASS
   LXC: Checking for namespace uts                                           : PASS
   LXC: Checking for namespace net                                           : PASS
   LXC: Checking for namespace user                                          : PASS
   LXC: Checking for cgroup 'memory' controller support                      : PASS
   LXC: Checking for cgroup 'memory' controller mount-point                  : FAIL (Mount 'memory' cgroup controller (suggested at /sys/fs/cgroup/memory))
   LXC: Checking for cgroup 'cpu' controller support                         : PASS
   LXC: Checking for cgroup 'cpu' controller mount-point                     : FAIL (Mount 'cpu' cgroup controller (suggested at /sys/fs/cgroup/cpu))
   LXC: Checking for cgroup 'cpuacct' controller support                     : PASS
   LXC: Checking for cgroup 'cpuacct' controller mount-point                 : FAIL (Mount 'cpuacct' cgroup controller (suggested at /sys/fs/cgroup/cpuacct))
   LXC: Checking for cgroup 'devices' controller support                     : PASS
   LXC: Checking for cgroup 'devices' controller mount-point                 : FAIL (Mount 'devices' cgroup controller (suggested at /sys/fs/cgroup/devices))
   LXC: Checking for cgrou
p 'net_cls' controller support                     : WARN (Enable CONFIG_NET_CLS_CGROUP in kernel Kconfig file)
   LXC: Checking for cgroup 'freezer' controller support                     : PASS
   LXC: Checking for cgroup 'freezer' controller mount-point                 : WARN (Mount 'freezer' cgroup controller (suggested at /sys/fs/cgroup/freezer))

****Error:****

File "/usr/lib/python2 ...
(more)
edit retag flag offensive close merge delete

Comments

Check the Nova logs on your controller(s). Most likely, the scheduler log will tell you which filter determines that there is no suitable compute node. If not, perhaps you need to switch on debug logging.

virt-host-validate seems to think something is wrong, but the output looks incomplete.

Bernd Bausch gravatar imageBernd Bausch ( 2018-08-06 08:45:58 -0600 )edit
add a comment