Hi,
I've done some regression testing on qemu from mitaka-proposed,
following the procedure from comment #6:
$ dpkg -l | grep qemu
ii ipxe-qemu
1.0.0+git-20131111.c3d1e78-2ubuntu1.1 all PXE boot
firmware - ROM images for qemu
ii qemu-block-extra:amd64 1:2.5+dfsg-5ubuntu10.36~cloud0
amd64 extra block backend modules for qemu-
system and qemu-utils
ii qemu-kvm 1:2.5+dfsg-5ubuntu10.36~cloud0
amd64 QEMU Full virtualization
ii qemu-system-common 1:2.5+dfsg-5ubuntu10.36~cloud0
amd64 QEMU full system emulation binaries (common
files)
ii qemu-system-x86 1:2.5+dfsg-5ubuntu10.36~cloud0
amd64 QEMU full system emulation binaries (x86)
ii qemu-utils 1:2.5+dfsg-5ubuntu10.36~cloud0
amd64 QEMU utilities
$ /hotplug.sh xenial 52:54:00:b3:ef:bc
Detach #1
Interface detached successfully
Detach #2
Interface detached successfully
...
Detach #2617
Interface detached successfully
This was performed while iperf and stress-ng were running. The guest
works correctly through and after the tests.
Thanks,
Heitor
** Tags removed: verification-mitaka-needed
** Tags added: verification-mitaka-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818880
Title:
Deadlock when detaching network interface
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1818880/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
