Re: [PATCH] postocpy: Check that postocpy fd's are not NULL

* Juan Quintela (quint...@redhat.com) wrote: > "Dr. David Alan Gilbert" wrote: > > * Juan Quintela (quint...@redhat.com) wrote: > >> If postcopy has finished, it frees the array. > >> But vhost-user unregister it at cleanup time. > > > > I must admit to being confused as the double migrate case vs

Re: [PATCH] postocpy: Check that postocpy fd's are not NULL

"Dr. David Alan Gilbert" wrote: > * Juan Quintela (quint...@redhat.com) wrote: >> If postcopy has finished, it frees the array. >> But vhost-user unregister it at cleanup time. > > I must admit to being confused as the double migrate case vs migrate > once and shutdown. It might just be an orderin

Re: [PATCH] postocpy: Check that postocpy fd's are not NULL

* Juan Quintela (quint...@redhat.com) wrote: > If postcopy has finished, it frees the array. > But vhost-user unregister it at cleanup time. I must admit to being confused as the double migrate case vs migrate once and shutdown. It might just be an ordering thing? I notice that 'vhost_user_backe

[PATCH] postocpy: Check that postocpy fd's are not NULL

If postcopy has finished, it frees the array. But vhost-user unregister it at cleanup time. Signed-off-by: Juan Quintela --- migration/postcopy-ram.c | 4 1 file changed, 4 insertions(+) diff --git a/migration/postcopy-ram.c b/migration/postcopy-ram.c index e721f69d0f..d18b5d05b2 100644 --