4:38 p.m.
This is a multi-part message in MIME format.
--------------1BC2811328971F9BAD7C7EDB
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Le 08/02/2018 à 13:59, Yaniv Kaul a écrit :
On Feb 7, 2018 7:08 PM, "Nicolas Ecarnot" <nicolas(a)ecarnot.net
<mailto:nicolas@ecarnot.net>> wrote:
Hello,
TL; DR : qcow2 images keep getting corrupted. Any workaround?
Long version:
This discussion has already been launched by me on the oVirt and
on qemu-block mailing list, under similar circumstances but I
learned further things since months and here are some informations :
- We are using 2 oVirt 3.6.7.5-1.el7.centos datacenters, using
CentOS 7.{2,3} hosts
- Hosts :
- CentOS 7.2 1511 :
- Kernel = 3.10.0 327
- KVM : 2.3.0-31
- libvirt : 1.2.17
- vdsm : 4.17.32-1
- CentOS 7.3 1611 :
- Kernel 3.10.0 514
- KVM : 2.3.0-31
- libvirt 2.0.0-10
- vdsm : 4.17.32-1
All are somewhat old releases. I suggest upgrading to the latest RHEL
and qemu-kvm bits.
Later on, upgrade oVirt.
Y.
Hello Yaniv,
We could discuss for hours about the fact that CentOS 7.3 was released
in January 2017, thus not that old.
And also discuss for hours explaining the gap between developers' will
to push their freshest releases and the curb we - industry users - put
on adopting such new versions. In my case, the virtualization
infrastructure is just one of the +30 domains I have to master everyday,
and the more stable the better.
In the setup described previously, the qemu qcow2 images were correct,
then not. We did not change anything. We have to find a workaround and
we need your expertise.
Not understanding the cause of the corruption threatens us to the same
situation in oVirt 4.2.
--
Nicolas Ecarnot
--------------1BC2811328971F9BAD7C7EDB
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Le 08/02/2018 à 13:59, Yaniv Kaul a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAJgorsb_we+ZEu=m1aeh=e_jaiXqf4P09SyEHVdC8V-S+ZoTFg@mail.gmail.com">
<div dir="auto">
<div><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Feb 7, 2018 7:08 PM,
"Nicolas
Ecarnot" <<a href="mailto:nicolas@ecarnot.net"
moz-do-not-send="true">nicolas(a)ecarnot.net</a>&gt;
wrote:<br type="attribution">
<blockquote class="quote" style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">Hello,<br>
<br>
TL; DR : qcow2 images keep getting corrupted. Any
workaround?<br>
<br>
Long version:<br>
This discussion has already been launched by me on the
oVirt and on qemu-block mailing list, under similar
circumstances but I learned further things since months
and here are some informations :<br>
<br>
- We are using 2 oVirt 3.6.7.5-1.el7.centos datacenters,
using CentOS 7.{2,3} hosts<br>
- Hosts :<br>
- CentOS 7.2 1511 :<br>
- Kernel = 3.10.0 327<br>
- KVM : 2.3.0-31<br>
- libvirt : 1.2.17<br>
- vdsm : 4.17.32-1<br>
- CentOS 7.3 1611 :<br>
- Kernel 3.10.0 514<br>
- KVM : 2.3.0-31<br>
- libvirt 2.0.0-10<br>
- vdsm : 4.17.32-1<br>
</blockquote>
</div>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">All are somewhat old releases. I suggest
upgrading to the latest RHEL and qemu-kvm bits. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Later on, upgrade oVirt. </div>
<div dir="auto">Y. </div>
</div>
</blockquote>
Hello Yaniv,<br>
<br>
We could discuss for hours about the fact that CentOS 7.3 was
released in January 2017, thus not that old.<br>
And also discuss for hours explaining the gap between developers'
will to push their freshest releases and the curb we - industry
users - put on adopting such new versions. In my case, the
virtualization infrastructure is just one of the +30 domains I have
to master everyday, and the more stable the better.<br>
In the setup described previously, the qemu qcow2 images were
correct, then not. We did not change anything. We have to find a
workaround and we need your expertise.<br>
<br>
Not understanding the cause of the corruption threatens us to the
same situation in oVirt 4.2.<br>
<br>
-- <br>
Nicolas Ecarnot<br>
</body>
</html>
--------------1BC2811328971F9BAD7C7EDB--