On 1/3/2019 3:57 PM, Dan Smith wrote: > Or even that libvirt/kvm > migration changes in such a way that these no longer make sense even for > it. We already have an example this in-tree today, where the > recently-added libvirt post-copy mode makes the 'abort' option invalid. I'm not following you here. As far as I understand, post-copy in the libvirt driver is triggered on the force complete action and only if (1) it's available and (2) nova is configured to allow it, otherwise the force complete action for the libvirt driver pauses the VM. The abort operation aborts the job in libvirt [1] which I believe triggers a rollback [2]. [1] https://github.com/openstack/nova/blob/8ef3d253a086e4f8575f5221d4515cda421abea2/nova/virt/libvirt/driver.py#L7388 [2] https://github.com/openstack/nova/blob/8ef3d253a086e4f8575f5221d4515cda421abea2/nova/virt/libvirt/driver.py#L7454 -- Thanks, Matt