[Bug 1746630] Re: virsh api is stuck when vm is down with NFS borken

Ubuntu Foundations Team Bug Bot 1746630 at bugs.launchpad.net
Thu Feb 1 04:20:35 UTC 2018

The attachment "lp1746630_xenial.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.

  virsh api is stuck when vm is down with NFS borken

Status in Ubuntu Cloud Archive:
Status in libvirt:
  Fix Released
Status in libvirt package in Ubuntu:

Bug description:

  virsh command is hang if there is broken VM on broken NFS

  This is affected to Xenial, UCA-Mitaka

  [Test Case]

  1. deploy VM with NFS storage ( running )
  2. block NFS via iptables
  - iptables -A OUTPUT -d NFS_SERVER_IP -p tcp --dport 2049 -j DROP ( on host machine )
  3. virsh blkdeviotune generic hda => hang
  4. virsh domstats => hang
  5. virsh list => lang

  After patch, we can command domstats and list with short timeout. and libvirt-bin needs to be restarted. so if there are many VMs it will be affected short time while it is restarting.


  This bug is fixed in redhat bug report[1] and mailing list[2] and git

  and it is merged 1.3.5 upstream


  [1] https://bugzilla.redhat.com/show_bug.cgi?id=1337073
  [2] https://www.redhat.com/archives/libvir-list/2016-May/msg01353.html
  [3] https://libvirt.org/git/?p=libvirt.git;a=commit;h=5d2b0e6f12b4e57d75ed1047ab1c36443b7a54b3
  [4] https://libvirt.org/git/?p=libvirt.git;a=commit;h=3aa5d51a9530a8737ca584b393c29297dd9bbc37
  [5] https://libvirt.org/git/?p=libvirt.git;a=commit;h=71d2c172edb997bae1e883b2e1bafa97d9f953a1

To manage notifications about this bug go to:

More information about the Ubuntu-openstack-bugs mailing list