<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Dan,<br>
<br>
Even with Glusterfs 4.3.2, we still need some extra steps to make
native integration with QEMU work, you can find more details from
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://www.gluster.org/community/documentation/index.php/Building_QEMU_with_gfapi_for_Debian_based_systems">http://www.gluster.org/community/documentation/index.php/Building_QEMU_with_gfapi_for_Debian_based_systems</a><br>
<br>
As for the qcow2 image importing, you can do it in two ways:<br>
(1) The FUSE approach:<br>
mount -t glusterfs //brickServerIp/volumeName /mnt<br>
qemu-img convert -f raw -O qcow2
path-to-the-source-raw-image-file /mnt/imageName.qcow2<br>
(2) The native approach, e.g., qemu-img convert -f raw -O qcow2
path-to-the-source-raw-image-file
gluster://brickServerIp/volumeName/imageName.qcow2<br>
<br>
Good luck!<br>
<br>
Best Regards,<br>
Bob<br>
<br>
On 04/02/2014 12:26 PM, Daniel wrote:<br>
</div>
<blockquote cite="mid:533B915C.9080706@collisiondetection.biz"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Hi,<br>
<br>
I am trying to achieve the same thing. Why did you have to
enable QEMU native integration when Glusterfs 4.3.2 already has
native QEMU support?<br>
<br>
How did you import the qcow2 image and how did you set it up. <br>
<br>
<br>
Thanks,<br>
<br>
Dan <br>
<br>
<div class="moz-cite-prefix">On 04/02/2014 10:59 AM, Chenggang
ZHANG wrote:<br>
</div>
<blockquote cite="mid:533B8B1E.9060200@gmail.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Dear All,<br>
<br>
I am using QEMU 1.7.0 and GlusterFs 4.3.2 and have carried out
necessary configurations to enable QEMU-Glusterfs native
integration (i.e., using libgfapi instead of FUSE).<br>
<br>
On the server side, I have configured a volume named "image"
using two bricks on two different machines "brk1" and "brk2".
And a qcow2 image <b>centos.qcow2</b> has been imported to
Glusterfs.<br>
<br>
On the client side (e.g., the KVM host), the configuration
"-drive file=gluster://<b>brk1</b>/image/centos.qcow2" is used
when starting a KVM VM. The VM boots successfully.<br>
When it's running, I shut down the machine brk1 on purpose and
want to see whether the KVM VM can automatically switch to use
"-drive file=gluster://<b>brk2</b>/image/centos.qcow2" (i.e., IP
failover). Unfortunately, the VM crashes.<br>
<br>
I am writing to ask whether the feature "IP failover" in
QEMU-Glusterfs native integration is supported. Thanks so much
for your kind help!<br>
<br>
<br>
Best Regards,<br>
Bob ZHANG<br>
<br>
<br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>