Re: [Openstack-operators] mitaka/xenial libvirt issues

We think we've pinned the qemu errors down to a mismatched group ID on a handful of compute nodes. The slow systemd/libvirt is still unsolved, but at the moment that does not actually be the cause of the qemu errors. On Mon, Nov 27, 2017 at 8:04 AM, Joe Topjian wrote: > Hi

Re: [Openstack-operators] mitaka/xenial libvirt issues

Hi all, To my knowledge, we don't use tunneled migrations. This issue is also happening with snapshots, so it's not restricted to just migrations. I haven't yet tried the apparmor patches that George mentioned. I plan on applying them once I get another report of a problematic instance. Thank

[Openstack-operators] ANNOUNCE: Self-healing SIG officially formed (fwd)

As per below, I'm happy to announce that the Self-healing SIG is now officially formed. For now, all discussions will happen on , so please subscribe to that list if you are interested in this topic! Cheers, Adam - Forwarded message from Adam Spiers

Re: [Openstack-operators] mitaka/xenial libvirt issues

Hello, The seems to assume tunnelled migrations, the live_migration_flag is removed in later version but is there in Mitaka. Do you have the VIR_MIGRATE_TUNNELLED flag set for [libvirt]live_migration_flag in nova.conf? Might be a long shot, but I've removed VIR_MIGRATE_TUNNELLED in our