Description of problem:
when migrating a guest from a host to another ( with a shared storage pool )
the source guest stay defined on the previous host
Version-Release number of selected component (if applicable):
i am using 0.8.6 from RHEL6.1 or SL6.1
Steps to Reproduce:
with virt-manager, connect to 2 hosts with a common shared storage
select migrate menu to a new host
the guest is correctly migrated to the new host, but stay defined
( switched off ) on the previous host
the guest should be undefined on the previous host
similarly as if the migration was done with the virsh CLI tool
with the migrate --undefinesource option.
it is more an enhancement than a bug, but i think the default should be
to undefine source , or at least propose an option to behave like this.
because when you have a lot of guests, it is VERY EASY to miss that a guest
was already migrated and running to another host, and nothing prevent you
to switch on this guest again. ( i have just done it! )
this is VERY dangerous, because with shared storage, booting a guest twice
will certainly lead to data corruption.
Agreed. We should make this the default, and maybe provide an option to 'leave copy of guest on source host' or something like that.
*** Bug 629016 has been marked as a duplicate of this bug. ***
That 'offline' migrate UI was actually bogus, and wasn't truly migrating offline, it was just migrating non-live, which means it would pause the VM to make it migrate faster. In general nobody really wants non-live migration, but if they did, they can manually pause their VM first. So i've removed that option from the upstream UI.
libvirt has true OFFLINE migration support (really just redefining the VM on the new connection), but we are now tracking that in a bug detailing a larger cleanup in this area.
*** This bug has been marked as a duplicate of bug 1060462 ***
Urgh, wrong comment. But the end result is the same, we are tracking this undefine issue at the dup'd bug.