<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <blockquote
      cite="mid:27A017A4-5304-488F-92DB-5179EDE001F5@redhat.com"
      type="cite">
      <blockquote type="cite">
        <blockquote type="cite">
          <blockquote type="cite">
            <blockquote type="cite">
              <pre wrap="">[...]
Il 26/03/2015 08:56, Christopher Pereira ha scritto:
</pre>
              <blockquote type="cite">
                <pre wrap="">[...]

During the "Waiting for the host to become operational in the engine"
stage, the hosted-engine-setup fails because of the following VDSM
requirement:

  "VIR_MIGRATE_AUTO_CONVERGE not found in libvirt, support for
  clusterLevel &gt;= 3.6 is disabled. For Fedora 20 users, please consider
  upgrading
  libvirt from the virt-preview repository"

According to [1], libvirt version &gt;= 1.2.3 is required.

Any suggestion where to get this packages + dependencies for CentOS 7?


</pre>
              </blockquote>
            </blockquote>
          </blockquote>
        </blockquote>
        <pre wrap="">[...]

OTOH, I wrote the above only because Centos 7.1 is not yet released, so one must use
the RC (Release Candidate) Centos repos, and because I can't recommend any extra repo.
</pre>
      </blockquote>
      [...]<br>
    </blockquote>
    <br>
    For the records,<br>
    <br>
    I installed libvirt 1.2.8 from CR repo:<br>
        yum --enablerepo=cr install libvirt-daemon<br>
    <br>
    This broke vdsm because of a "no connection driver available for
    qemu:///system" error.<br>
    <br>
    The problem was that libvirt 1.2.8 "failed to load module
    /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so" and
    "/usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so:
    undefined symbol: virStorageFileCreate".<br>
    <br>
    The solution is to upgrade device-mapper-libs:<br>
        yum --enablerepo=cr upgrade device-mapper-libs<br>
    <br>
    Conclusion: A device-mapper dependency should be added to libvirt<br>
    <br>
    This are my installed packages:<br>
    <br>
    device-mapper-1.02.93-3.el7.x86_64<br>
    device-mapper-event-1.02.93-3.el7.x86_64<br>
    device-mapper-event-libs-1.02.93-3.el7.x86_64<br>
    device-mapper-libs-1.02.93-3.el7.x86_64<br>
    device-mapper-multipath-0.4.9-66.el7.x86_64<br>
    device-mapper-multipath-libs-0.4.9-66.el7.x86_64<br>
    device-mapper-persistent-data-0.3.2-1.el7.x86_64<br>
    libvirt-client-1.2.8-16.el7_1.1.x86_64<br>
    libvirt-daemon-1.2.8-16.el7_1.1.x86_64<br>
    libvirt-daemon-config-nwfilter-1.2.8-16.el7_1.1.x86_64<br>
    libvirt-daemon-driver-interface-1.2.8-16.el7_1.1.x86_64<br>
    libvirt-daemon-driver-network-1.2.8-16.el7_1.1.x86_64<br>
    libvirt-daemon-driver-nodedev-1.2.8-16.el7_1.1.x86_64<br>
    libvirt-daemon-driver-nwfilter-1.2.8-16.el7_1.1.x86_64<br>
    libvirt-daemon-driver-qemu-1.2.8-16.el7_1.1.x86_64<br>
    libvirt-daemon-driver-secret-1.2.8-16.el7_1.1.x86_64<br>
    libvirt-daemon-driver-storage-1.2.8-16.el7_1.1.x86_64<br>
    libvirt-daemon-kvm-1.2.8-16.el7_1.1.x86_64<br>
    libvirt-lock-sanlock-1.2.8-16.el7_1.1.x86_64<br>
    libvirt-python-1.2.8-7.el7_1.1.x86_64<br>
    <br>
    Regards,<br>
    Christopher<br>
    <b style="font-weight:normal;"
      id="docs-internal-guid-130ebd9b-56cd-ce15-c195-f904f64cf96c"><span
style="font-size:15px;font-family:Arial;color:#000000;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap;"><b></b></span></b>
  </body>
</html>