Message ID | 20161118102141.8237.29567.malone@gac.canonical.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On Fri, Nov 18, 2016 at 11:21 AM, Rafael David Tinoco < rafael.tinoco@canonical.com> wrote: > With customers using vhost-user that might > still cause migration problems, but, likely, those are the vast > minority. > It is and has migration issues in general atm anyway - see: https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg03026.html https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg03223.html So that needs more work and is not in your current scope IMHO.
diff --git a/hw/virtio/vhost.c b/hw/virtio/vhost.c index 131f164..25bf67f 100644 --- a/hw/virtio/vhost.c +++ b/hw/virtio/vhost.c @@ -1122,7 +1122,7 @@ int vhost_dev_init(struct vhost_dev *hdev, void *opaque, if (!(hdev->features & (0x1ULL << VHOST_F_LOG_ALL))) { error_setg(&hdev->migration_blocker, "Migration disabled: vhost lacks VHOST_F_LOG_ALL feature."); - } else if (!qemu_memfd_check()) { + } else if (vhost_dev_log_is_shared(hdev) && !qemu_memfd_check()) { error_setg(&hdev->migration_blocker, "Migration disabled: failed to allocate shared memory"); }