virsh destroy might also kill another running VM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Fedora) |
Fix Released
|
High
|
|||
libvirt (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Jaunty |
Fix Released
|
Critical
|
Dustin Kirkland |
Bug Description
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:
ttx@cassini:~$ virsh list
Connecting to uri: qemu:///system
Id Name State
-------
5 intrepid-test running
6 jaunty-devel running
ttx@cassini:~$ virsh destroy intrepid-test
Connecting to uri: qemu:///system
Domain intrepid-test destroyed
ttx@cassini:~$ virsh list
Connecting to uri: qemu:///system
Id Name State
-------
ttx@cassini:~$
Running strace on the-one-
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.
Related branches
Changed in libvirt (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in libvirt (Fedora): | |
status: | Unknown → Fix Committed |
Changed in libvirt (Fedora): | |
status: | Fix Committed → Fix Released |
Changed in libvirt (Ubuntu Jaunty): | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in libvirt (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in libvirt (Ubuntu Jaunty): | |
status: | Triaged → In Progress |
assignee: | nobody → Dustin Kirkland (kirkland) |
milestone: | none → jaunty-updates |
tags: |
added: verification-done removed: verification-needed |
Changed in libvirt (Fedora): | |
importance: | Unknown → High |
Possibly related: when attempting to reboot vm's from the Virtual Machine Manager windows causes this complaint:
Traceback (most recent call last): virt-manager/ virtManager/ engine. py", line 528, in reboot_domain virt-manager/ virtManager/ domain. py", line 504, in reboot vm.reboot( 0) python2. 6/dist- packages/ libvirt. py", line 392, in reboot
File "/usr/share/
vm.reboot()
File "/usr/share/
self.
File "/usr/lib/
if ret == -1: raise libvirtError ('virDomainReboot() failed', dom=self)
libvirtError: this function is not supported by the hypervisor: virDomainReboot