<html><body><div style="font-family: Arial; font-size: 10pt; color: #000000"><div>Hey Bernhard,</div><div><br></div><div>I've always needed the <p style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p style="margin: 0px;" data-mce-style="margin: 0px;">server.allow-insecure: on</p><br></div><div>for successful migrations. </div><div><br></div><div>Also, I've not had any issues with cache=none with my machines. A copy of a disk segment from one of my working machines</div><div><p style="margin: 0px;" data-mce-style="margin: 0px;"><disk type='network' device='disk'><br> <driver name='qemu' type='raw' cache='none'/><br> <source protocol='gluster' name='VMARRAY/HFMMNG1.img'><br> <host name='10.9.1.2' port=''/><br> </source><br> <target dev='vda' bus='virtio'/><br> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/><br> </disk></p><p style="margin: 0px;" data-mce-style="margin: 0px;"><br></p><p style="margin: 0px;" data-mce-style="margin: 0px;">Best,</p><p style="margin: 0px;" data-mce-style="margin: 0px;">Josh</p></div><div><br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Bernhard Glomm" <bernhard.glomm@ecologic.eu><br><b>To: </b>pkarampu@redhat.com<br><b>Cc: </b>gluster-users@gluster.org<br><b>Sent: </b>Thursday, January 16, 2014 9:02:54 AM<br><b>Subject: </b>Re: [Gluster-users] gluster and kvm livemigration<br><div><br></div><title></title><style>.felamimail-body-blockquote {margin: 5px 10px 0 3px;padding-left: 10px;border-left: 2px solid #000088;} </style><div>btw:</div><div><br></div><div>The VM are configured to use cache=writethrough</div><div>since cache=none doesn't work (can't install the machine</div><div>because of i/o errors when I try to use the disk)</div><div>can't start an installed machine with cache=none</div><div>with cache=writethrough and cache=writeback</div><div>the machines starts and runs, but lifemigration</div><div>shows both time the same issue that</div><div>the disk will become readonline on successful migration</div><div>remount, reboot failed</div><div>only a shutdown and a restart works.</div><div><br></div><div>TIA</div><div><br></div><div>Bernhard </div><div><br></div><div><br></div><div><br></div><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote">I experienced a strange behavior of glusterfs during livemigration<br>of a qemu-kvm guest<br>using a 10GB file on a mirrored gluster 3.4.2 volume<br>(both on ubuntu 13.04)<br>I run<br>virsh migrate --verbose --live --unsafe --p2p --domain atom01 --desturi<br>qemu+ssh://<target_ip>/system<br>and the migration works,<br>the running machine is pingable and keeps sending pings.<br>nevertheless, when I let the machine touch a file during migration<br>it stops, complaining that it's filesystem is read only (from that moment<br>that<br>migration finished)<br>A reboot from inside the machine failes,<br>machine goes down and comes up with an error<br>unable to write to sector xxxxxx on hd0<br>(than falling into the initrd).<br>a<br>virsh destroy VM && virsh start VM<br>leads to a perfect running VM again,<br>no matter on which of the two hosts I start the machine<br>anybody better experience with livemigration?<br>any hint on a procedure how to debug that?<br></blockquote></blockquote><style>.felamimail-body-blockquote {margin: 5px 10px 0 3px;padding-left: 10px;border-left: 2px solid #000088;} </style>
<br>_______________________________________________<br>Gluster-users mailing list<br>Gluster-users@gluster.org<br>http://supercolony.gluster.org/mailman/listinfo/gluster-users</div><div><br></div></div></body></html>