I agree that it is important to be conservative, nevertheless, take a look
here:
--
"Although libvirt 1.2.15 works with Xen, libvirt 1.3.2 or newer is
recommended."
"We do however recommend using libvirt 1.3.2, which is fully supported and
tested as part of the Xen Project CI loop. It addresses live migration
monitoring related issues and adds support for peer-to-peer migration mode,
which nova relies on."
I agree that it is important to be conservative, nevertheless, take a look
here:
--
"Although libvirt 1.2.15 works with Xen, libvirt 1.3.2 or newer is
recommended."
"We do however recommend using libvirt 1.3.2, which is fully supported and
tested as part of the Xen Project CI loop. It addresses live migration
monitoring related issues and adds support for peer-to-peer migration mode,
which nova relies on."
https:/ /github. com/openstack/ openstack- manuals/ blob/master/ doc/config- reference/ source/ compute/ hypervisor- xen-libvirt. rst
--
-- /launchpad. net/~canonical- x/+archive/ ubuntu/ x-staging
Another example, Mesa is 11.1 but, Xorg team is planning to upgrade it to
11.2:
https:/
--
Cheers!
Thiago
On 18 March 2016 at 10:49, Launchpad Bug Tracker <<email address hidden>
> wrote:
> Status changed to 'Confirmed' because the bug affects multiple users. /bugs.launchpad .net/bugs/ 1558857 /bugs.launchpad .net/ubuntu/ +source/ libvirt/ +bug/1558857/ +subscriptions
>
> ** Changed in: libvirt (Ubuntu)
> Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Upgrade to latest stable version v1.3.2
>
> To manage notifications about this bug go to:
>
> https:/
>