<html><head></head><body dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">No problem from s390x point of view. With Ubuntu we’re currently using<div class=""><br class=""><div class="">* qemu: 2.10.1</div><div class="">* libvirt: 3.6.0</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Thanks!</div><div class=""><div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;"><br class="Apple-interchange-newline">---</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">Andreas Scheuring (andreas_s)</div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<div><br class=""><div class="">On 30. Mar 2018, at 16:26, Kashyap Chamarthy <<a href="mailto:kchamart@redhat.com" class="">kchamart@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">The last version bump was in "Pike" release (commit: b980df0,<br class="">11-Feb-2017), and we didn't do any bump during "Queens".  So it's time<br class="">to increment the versions (which will also makes us get rid of some<br class="">backward compatibility cruft), and pick future versions of libvirt and<br class="">QEMU.                                          <br class=""><br class="">As it stands, during the "Pike" release the advertized NEXT_MIN versions                       <br class="">were set to: libvirt 1.3.1 and QEMU 2.5.0 -- but they weren't actually                         <br class="">bumped for the "Queens" release.  So they will now be applied for the                          <br class="">"Rocky" release.  (Hmm, but note that libvirt 1.3.1 was released more                          <br class="">than 2 years ago[1].)                          <br class=""><br class="">While at it, we should also discuss about what will be the NEXT_MIN                            <br class="">libvirt and QEMU versions for the "Solar" release.  To that end, I've                          <br class="">spent going through different distributions and updated the                                    <br class="">DistroSupportMatrix Wiki[2].                   <br class=""><br class="">Taking the DistroSupportMatrix into picture, for the sake of discussion,<br class="">how about the following NEXT_MIN versions for "Solar" release:                                 <br class=""><br class="">(a) libvirt: 3.2.0 (released on 23-Feb-2017)   <br class=""><br class="">    This satisfies most distributions, but will affect Debian "Stretch",                       <br class="">    as they only have 3.0.0 in the stable branch -- I've checked their<br class="">    repositories[3][4].  Although the latest update for the stable<br class="">    release "Stretch (9.4)" was released only on 10-March-2018, I don't<br class="">    think they increment libvirt and QEMU versions in stable.  Is<br class="">    there another way for "Stretch (9.4)" users to get the relevant<br class="">    versions from elsewhere?                   <br class=""><br class="">(b) QEMU: 2.9.0 (released on 20-Apr-2017)      <br class=""><br class="">    This too satisfies most distributions but will affect Oracle Linux<br class="">    -- which seem to ship QEMU 1.5.3 (released in August 2013) with<br class="">    their "7", from the Wiki.  And will also affect Debian "Stretch" --<br class="">    as it only has 2.8.0<br class=""><br class="">Can folks chime in here?<br class=""><br class="">[1] <a href="https://www.redhat.com/archives/libvirt-announce/2016-January/msg00002.html" class="">https://www.redhat.com/archives/libvirt-announce/2016-January/msg00002.html</a><br class="">[2] <a href="https://wiki.openstack.org/wiki/LibvirtDistroSupportMatrix" class="">https://wiki.openstack.org/wiki/LibvirtDistroSupportMatrix</a><br class="">[3] <a href="https://packages.qa.debian.org/libv/libvirt.html" class="">https://packages.qa.debian.org/libv/libvirt.html</a><br class="">[4] <a href="https://packages.qa.debian.org/libv/libvirt.html" class="">https://packages.qa.debian.org/libv/libvirt.html</a><br class=""><br class="">-- <br class="">/kashyap<br class=""><br class="">_______________________________________________<br class="">OpenStack-operators mailing list<br class=""><a href="mailto:OpenStack-operators@lists.openstack.org" class="">OpenStack-operators@lists.openstack.org</a><br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators<br class=""></div></div></div><br class=""></div></div></div></body></html>