Red Hat Bugzilla – Bug 1160212
libvirt doesn't stop the NBD server after migration
Last modified: 2015-03-05 02:46:50 EST
Description of problem: After migration with NBD, the NBD server stays running on the destination, occupying a TCP port. Version-Release number of selected component (if applicable): libvirt-1.2.8-5.el7.x86_64 How reproducible: 100 % Steps to Reproduce: 1. Migrate a domain with --copy-storage-all Actual results: netstat -tnap shows qemu still listens on a port: tcp6 0 0 :::49153 :::* LISTEN 8073/qemu-kvm Expected results: The ports are no longer used after the migration finishes. Additional info: Upstream patch sent by Weiwei Li: https://www.redhat.com/archives/libvir-list/2014-November/msg00046.html
Fixed upstream by: commit c3012a023f2ae5763027cafc1cf2881a3c7c4b45 Author: Weiwei Li <nuonuoli@tencent.com> AuthorDate: 2014-11-04 10:52:10 +0100 Commit: Ján Tomko <jtomko@redhat.com> CommitDate: 2014-11-04 10:54:53 +0100 qemu: stop NBD server after successful migration In qemuMigrationFinish mig->nbd can not be initialized by qemuMigrationEatCookie without the QEMU_MIGRATION_COOKIE_NBD flag. That causes qemuMigrationStopNBDServer to return early without stopping the NBD server properly. Signed-off-by: Weiwei Li <nuonuoli@tencent.com> Signed-off-by: Ján Tomko <jtomko@redhat.com> git describe: v1.2.10-14-gc3012a0
I can reproduce this bug with libvirt-1.2.8-5.el7.x86_64 steps 1.migrate guest from the source to the target with --copy-storage-all option # virsh migrate --live --copy-storage-all rhel6 qemu+ssh://10.66.100.131/system --verbose root@10.66.100.131's password: Migration: [100 %] 2.After finish migration, still could see the nbd service occupying a TCP port. # netstat -tunlp|grep qemu-kvm tcp6 0 0 :::49154 :::* LISTEN 2934/qemu-kvm Verify this bug with libvirt-1.2.8-7.el7, after finish storage migration with --copy-storage-all, the nbd service will release all ports which its occupy previous # netstat -tunlp|grep qemu-kvm tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 3455/qemu-kvm
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0323.html