Description of problem: After a user has ( Live ) migrated vm image to another server flag that image ( perhaps new icon instead of the shutdown one ) and warn the user and/or prevent him to start the migrated image ( unless overwritten ) on the host that the image just got live migrated from. Version-Release number of selected component (if applicable): virt-manager-0.8.5-1.fc13 How reproducible: Always Steps to Reproduce: 1. Live migrate vm to another host 2. Run the vm that just got migrated and is mark as shutoff on the previous host 3. Actual results: The user can run the image again on the previous host. Expected results: User not being able to run the newly migrated image which is already running on the new host on the previous host. Additional info:
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Moving to upstream tracker. The whole preventing guests from being started twice if they use the same storage is the goal of libvirt's locking driver stuff (fairly new so not likely to arrive until f16)
I think the main problem here is that we leave the guest defined on the source host by default. We shouldn't do that. There's another bug tracking that issue *** This bug has been marked as a duplicate of bug 733388 ***