How to track VM and task states in log files during VM deployment?

asked 2015-01-29 13:56:29 -0500

agardiman gravatar image

updated 2015-01-30 04:22:43 -0500

Hi everybody, I'm trying to figure out the steps that are executed by OpenStack from when an user asks to deploy a VM, to when the instance is running on the host. I would need to know all the actions (and the components involved) in the deployment workflow, and track down when each of these actions is executed (to know all the timings). My goal is to understand what components and what actions take most of the time in that process (analyzing different use cases), and afterwards trying to increase the performance changing the default configuration or the source code.

I know that, roughly, some of the steps needed to deploy a VM are:

  • insert the request in the system (in the database probably, and then send it through the queuing system)
  • find which of the physical server can host better the instance (through the scheduler in Nova)
  • clone the VM image to the designated host (from Glance to the host)
  • create the right environment in the host (reserve CPU, RAM, disk quota, etc)
  • the hypervisor in the host runs the VM

Moreover I found at the end of this link ( the main VM and task states during a VM deployment.

I've searched in all the log files specified in ( , also after changing the debug level in DEBUG in the file /etc/nova/logging.conf. I wasn't able to find anything related to what I'm searching.

Maybe I'm missing something and I set some wrong parameter, or I searched in the wrong places. I would like to know if I can find all these informations in the log files, and, if so, which options I have to change in the configuration files (nova.conf, loggin.conf etc).

If, userful, here there are some information on my running environment:

  • I have the juno release installed on 3 VM running on VirtualBox on my laptop. To install everything I followed the instructions listed this link ( (1 controller node, 1 network node, 1 compute node).
  • The hypervisor is KVM (libvirt).
  • The test image format is qcow2.

Thank you very much!!

edit retag flag offensive close merge delete