qemu: migration: Don't access disk members without lock
qemu: migration: Don't access disk members without lock

The initiation of a synchronous block job in the NBD storage migration
code was placed after entering the monitor thus after the lock on the VM
object was unlocked. Thankfully nothing bad could happen in this
situation since the migration job prevents any disk detaches or other
modifications of the domain object.

Signed-off-by: Peter Krempa <2cf5c04c61aa466e4a47bfedc747d17279c72ffc@redhat.com>
Reviewed-by: John Ferlan <87558058f6f829e5ec976c8ef960720af4ff9c7d@redhat.com>

libvirt/libvirt,jfehlig/libvirt,olafhering/libvirt,crobinso/libvirt,andreabolognani/libvirt,andreabolognani/libvirt,fabianfreyer/libvirt,nertpinx/libvirt,fabianfreyer/libvirt,eskultety/libvirt,jfehlig/libvirt,zippy2/libvirt,zippy2/libvirt,crobinso/libvirt,andreabolognani/libvirt,eskultety/libvirt,nertpinx/libvirt,libvirt/libvirt,olafhering/libvirt,nertpinx/libvirt,zippy2/libvirt,andreabolognani/libvirt,fabianfreyer/libvirt,jardasgit/libvirt,nertpinx/libvirt,fabianfreyer/libvirt,eskultety/libvirt,crobinso/libvirt,jfehlig/libvirt,olafhering/libvirt,zippy2/libvirt,jardasgit/libvirt,jardasgit/libvirt,olafhering/libvirt,jardasgit/libvirt,jardasgit/libvirt,libvirt/libvirt,nertpinx/libvirt,crobinso/libvirt,eskultety/libvirt,eskultety/libvirt,fabianfreyer/libvirt,andreabolognani/libvirt,jfehlig/libvirt,libvirt/libvirt