[one-users] VM in boot state for a very long time

[Javier Fontan]

This can be caused by several things.

* There are already 15 actions being done by the VMM. By default the
drivers are only allowed to execute 15 actions at the same time and
the next actions are enqueued. Have you launched a batch of actions to
lots of VMs?

* There is already an action being executed in that host that is
hanging. The drivers only execute one action per Host at the same time
as sometimes libvirt does not play well with several actions. Can you
check that there is no hanging action script executing in that host? A
"ps" and check for script executions from /var/tmp/one is a good way
to check for them.

* The virtual network drivers are taking too much time. What are the
network drivers you are using?

Cheers

On Tue, Dec 10, 2013 at 5:54 PM, Liu, Guang Jun (Gene)
<Gene.Liu at alcatel-lucent.com> wrote:
> Hi there,
>
> I am running 4.2 (RHEL6.4, KVM). I experienced that VM stays in "BOOT"
> state for a very long time (~15 minutes). The image copy is fast (VM
> state goes to BOOT from prolog). There is not any log and the servers
> (both the computing node/host, and one front-server) are idle. Can
> anyone suggest me where I should look at to figure out the cause of VM
> in "BOOT" so long?
>
> Thanks very much!
>
> --
> Gene Liu
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org



-- 
Javier Fontán Muiños
Developer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | @OpenNebula | github.com/jfontan