Hi all,
We're seeing some strange libvirt issues in an Ubuntu 16.04 environment.
It's running Mitaka, but I don't think this is a problem with OpenStack
itself.
We're in the process of upgrading this environment from Ubuntu 14.04 with
the Mitaka cloud archive to 16.04. Instances are being live mi
We hit the same issue a while back (I suspect), which we seemed to resolve
by pinning QEMU and related packages at the following version (you might
need to hunt down the debs manually):
1:2.5+dfsg-5ubuntu10.5
I'm certain there's a launchpad bug for Ubuntu qemu regarding this, but
don't have it to
Hi Chris,
Thanks - we will definitely look into this. To confirm: did you also
downgrade libvirt as well or was it all qemu?
Thanks,
Joe
On Thu, Nov 23, 2017 at 9:16 AM, Chris Sarginson wrote:
> We hit the same issue a while back (I suspect), which we seemed to resolve
> by pinning QEMU and re
I think we may have pinned libvirt-bin as well, (1.3.1), but I can't
guarantee that, sorry - I would suggest its worth trying pinning both
initially.
Chris
On Thu, 23 Nov 2017 at 17:42 Joe Topjian wrote:
> Hi Chris,
>
> Thanks - we will definitely look into this. To confirm: did you also
> down
OK, thanks. We'll definitely look at downgrading in a test environment.
To add some further info to this problem, here are some log entries. When
an instance fails to snapshot or fails to migrate, we see:
libvirtd[27939]: Cannot start job (modify, none) for domain
instance-4fe4; current job i
