On Wed, Aug 15, 2012 at 12:14 PM, Yin Yin <maillistofyinyin@xxxxxxxxx> wrote: > Hi,Bharata B Rao: > I have try your patch, but has some problem. I found that both > glusterfs and qemu have a fun uuid_is_null. > glusterfs use contrib/uuid/isnull.c > qemu use block/vdi.c > > > I test the api/example, the glfsxmp.c call uuid_is_null in > contrib/uuid/isnull.c > but qemu/block/gluster.c finally call the uuid_is_null in vdi.c which cause > vm can't boot. So you are configuring QEMU with --disable-uuid ? Even then, there should be no issues. I just verified that and I don't understand why it should cause problems in VM booting. Can you please ensure the following: - Remove all the traces of gluster from your system (which means removing any installed gluster rpms) before you compile gluster from source. - Try with my v6 patcheset (http://lists.nongnu.org/archive/html/qemu-devel/2012-08/msg01536.html) When you say VM isn't booting, do you see a hang or a segfault ? Let me know how are you specifying the gluster drive (-drive file=gluster://server[:port]/volname/image[?transport=socket]) Please verify that you are able to FUSE mount your volume before tying with QEMU. Regards, Bharata.
