From bug 526919.
If I migrate a guest using migrate --live, and poweroff that guest, I have no config files left anywhere. I cannot power on the guest any more.
If the guest was not defined, i.e. no virsh define, just a create
then that's normal, the guest was transcient on the source and stay
transcient on the target. On the other hand if the guest was being defined
on the source, than IMHO it's a bug. What was you use case ?
I can't see what the use for transient guests is (apart from to work around the weirdness of not deleting config files when a migrate is done).
(In reply to comment #2)
> I can't see what the use for transient guests is (apart from to work around the
> weirdness of not deleting config files when a migrate is done).
It's mostly as a quick testing type environment, but it's also useful in this migration scenario. That is, you can imagine:
1) Migrate guest from A -> B
2) Take down A for maintenance
3) Bring A back up
4) Migrate B -> A
In this case, maybe you never want to define the guest on B at all, since it's more or less just a container for it.
So there are scenarios you can construct for both defining and not defining the domain on the destination. I'm going to post a patch that allows you to fine-tune this behavior in the API, in which case you'll get to choose.
I'm going to close this bug, though, since it's doing the intended thing at the moment (even if it doesn't quite fit your use case). Feel free to re-open it if you disagree.