Comment 36 for bug 362288

Sometimes, using 'virsh destroy' or the 'Force off' button in virt-manager will cause multiple running VMs to be destroyed. Here's an example:

[wwoods@metroid ~]$ sudo virsh list --all
 Id Name State
----------------------------------
  1 Ubuntu_Jaunty running
  4 Fedora_10_clone running
  5 F10_2 running
  6 F10 running

[wwoods@metroid ~]$ sudo virsh destroy F10_2
Domain F10_2 destroyed

[wwoods@metroid ~]$ sudo virsh list --all
 Id Name State
----------------------------------
  1 Ubuntu_Jaunty running
  4 Fedora_10_clone running
  - F10 shut off
  - F10_2 shut off

Note that 'F10' is now also shut off, even though I didn't destroy it. This doesn't seem to happen every time, and it doesn't seem to be related to the names of the hosts being similar:

[wwoods@metroid ~]$ sudo virsh list --all
 Id Name State
----------------------------------
  1 Ubuntu_Jaunty running
  4 Fedora_10_clone running
  8 F10_2 running
  - F10 shut off

[wwoods@metroid ~]$ sudo virsh start F10
Domain F10 started

[wwoods@metroid ~]$ sudo virsh destroy Fedora_10_clone
Domain Fedora_10_clone destroyed

[wwoods@metroid ~]$ sudo virsh list --all
 Id Name State
----------------------------------
  1 Ubuntu_Jaunty running
 10 F10 running
  - F10_2 shut off
  - Fedora_10_clone shut off

There are no relevant messages in syslog, other than the expected ones (e.g. "kernel: virbr0: port 3(vnet2) entering disabled state" as the host comes down).