Re: [Users] unable to start vm in 3.3 and f19 with gluster
On Thu, Sep 26, 2013 at 11:07 AM, David Riedl wrote:
g report on your issue.
https://bugzilla.redhat.com/show_bug.cgi?id=988299
Scroll to the end. ( https://bugzilla.redhat.com/show_bug.cgi?id=988299#c46
)
There is a modified glusterVolume.py. I have the same issue as well, I'm
trying to fix this it right now.
Regards David
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Unfortunately I have the esx infra down for a scheduled maintenance right now.
Later today I'm going to verify and test when up again as suggested to
me in the previous message..
But it doesn't appear as the same thing to me...
My volume is gv01 and without any _ or / in it.
Also the message is a bit different
On vdsm.log of host:
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2805, in createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
libvirtError: Unable to read from monitor: Connection reset by peer
In qemu.log of the VM
Gluster connection failed for server=ovnode01 port=0 volume=gv01
image=20042e7b-0929-48ca-ad40-2a2aa22f0689/images/d004045e-620b-4d90-8a7f-6c6d26393a08/dff09892-bc60-4de5-85c0-2a1fa215a161
transport=tcp
Gianluca