Public bug reported:
Jaunty KVM amd64 host running:
libvirt 0.6.1-0ubuntu4
kvm 1:84+dfsg-0ubuntu10
I'm starting multiple VMs (using virsh start or virt-manager)
Then calling "virsh destroy" on the first one in the list also destroys the
second one:
t...@cassini:~$ virsh list
Connecting to uri: qemu:///system
Id Name State
----------------------------------
5 intrepid-test running
6 jaunty-devel running
t...@cassini:~$ virsh destroy intrepid-test
Connecting to uri: qemu:///system
Domain intrepid-test destroyed
t...@cassini:~$ virsh list
Connecting to uri: qemu:///system
Id Name State
----------------------------------
t...@cassini:~$
Running strace on the-one-that-shouldn't-be-killed reveals it receives
SIGKILL.
Test scenarios:
Starting A, Starting B, virsh destroy A -> A and B get destroyed
Starting B, Starting A, virsh destroy B -> A and B get destroyed
Starting A, Starting B, virsh destroy B -> only B is destroyed
Starting A, Starting B, Starting C, virsh destroy A -> A and B get destroyed
Starting A, Starting B, Starting C, virsh destroy B -> B and C get destroyed
I can reproduce it on freshly created VMs stuck at "select boot device"
BIOS stage (I hit F12) so it probably doesn't depend on the guest
nature.
Using "Force off" from virt-manager also triggers the issue.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
