Il 30/10/2013 13:58, Dan Kenigsberg ha scritto:

On Wed, Oct 30, 2013 at 11:34:21AM +0100, Alessandro Bianchi wrote:

   Hi everyone

   I've set up a gluster storage with two replicated bricks

   DC is up and I created a VM to test gluster storage

   If I start the VM WITHOUT any disk attached (only one virtual DVD) it
   starts fine.

   If I attach a gluster domain disk thin provisioning 30 Gb the Vm stucks in
   "waiting for launch" state

   I see no special activity on the gluster servers (they serve several other
   shares with no troubles at all and even the ISO domain  is a NFS on
   locally mounted gluster and works fine)

   I've double checked all the pre requisites and they look fine (F 19 -
   gluster setup insecure  in both glusterd.vol and volume options -
   uid/gid/insecure )

   Am I doing something wrong?

   I'm even unable to stop the VM from the engine GUI

   Any advise?

Which version of ovirt are you using? Hopefully ovirt-3.3.0.1.
For how long is the VM stuck in its "wait for launch" state?
What does `virsh -r list` has to say while startup stalls?
Would you provide more content of your vdsm.log and possibly
libvirtd.log so we can understand what blocks the VM start-up? Please
use attachement of pastebin, as your mail agents wreaks havoc to the log
lines.

Thank you for your answer.

Here are the "facts"

In the GUI I see

"waiting for launch 3 h"

 virsh -r list
 Id    Nome                           Stato
----------------------------------------------------
 3     CentOS_30                      terminato


vdsClient -s 0 list table
200dfb05-461e-49d9-95a2-c0a7c7ced669      0  CentOS_30            WaitForLaunch 

Packages:

ovirt-engine-userportal-3.3.0.1-1.fc19.noarch
ovirt-log-collector-3.3.1-1.fc19.noarch
ovirt-engine-restapi-3.3.0.1-1.fc19.noarch
ovirt-engine-setup-3.3.0.1-1.fc19.noarch
ovirt-engine-backend-3.3.0.1-1.fc19.noarch
ovirt-host-deploy-java-1.1.1-1.fc19.noarch
ovirt-release-fedora-8-1.noarch
ovirt-engine-setup-plugin-allinone-3.3.0.1-1.fc19.noarch
ovirt-engine-webadmin-portal-3.3.0.1-1.fc19.noarch
ovirt-engine-sdk-python-3.3.0.7-1.fc19.noarch
ovirt-iso-uploader-3.3.1-1.fc19.noarch
ovirt-engine-websocket-proxy-3.3.0.1-1.fc19.noarch
ovirt-engine-dbscripts-3.3.0.1-1.fc19.noarch
ovirt-host-deploy-offline-1.1.1-1.fc19.noarch
ovirt-engine-cli-3.3.0.5-1.fc19.noarch
ovirt-engine-tools-3.3.0.1-1.fc19.noarch
ovirt-engine-lib-3.3.0.1-1.fc19.noarch
ovirt-image-uploader-3.3.1-1.fc19.noarch
ovirt-engine-3.3.0.1-1.fc19.noarch
ovirt-host-deploy-1.1.1-1.fc19.noarch

I attach the full vdsm log

Look around 30-10 10:30 to see all what happens

Despite the "terminated" label in output from virsh I still see the VM "waiting for launch" in the GUI, so I suspect the answer to "how long" may be "forever"

Since this is a test VM I can do whatever test you may need to track the problem included destroy and rebuild

It would be great to have gluster support stable in ovirt!

Thank you for your efforts

Best regards

Alessandro