FWIW, in nova, I don't know if it's expected for an instance to go from power state 0 (None) to 3 (Paused) to 1 (Running) during provisioning. Power state information comes from the virt driver and there's a periodic sync task in compute manager that attempts to make vm_state and power_state match if there's a discrepancy. The periodic task runs by default every 10 minutes (and can be disabled). Note that there's no sync attempted when vm_state is "building" -- that case is ignored. When vm_state is "active", the "paused" power state is ignored because of [1].
So even if the sync periodic task fired while you were waiting, it wouldn't have done anything to the instance. So, I think the question is whether it's "normal" for the virt driver to report power state as "paused" during the domain bringup.
FWIW, in nova, I don't know if it's expected for an instance to go from power state 0 (None) to 3 (Paused) to 1 (Running) during provisioning. Power state information comes from the virt driver and there's a periodic sync task in compute manager that attempts to make vm_state and power_state match if there's a discrepancy. The periodic task runs by default every 10 minutes (and can be disabled). Note that there's no sync attempted when vm_state is "building" -- that case is ignored. When vm_state is "active", the "paused" power state is ignored because of [1].
So even if the sync periodic task fired while you were waiting, it wouldn't have done anything to the instance. So, I think the question is whether it's "normal" for the virt driver to report power state as "paused" during the domain bringup.
[1] https:/ /bugs.launchpad .net/nova/ +bug/1097806