Comment 3 for bug 755666

Hi Andrey - sorry about the problem. You're correct, the patch does not address the case where the definition exists _and_ you reset the database so an instance ID is reused when creating a new machine. That shouldn't happen to production users (because we don't reuse instance IDs unless the DB is reset), I believe, and it only happens to people that ran the version between the break and the fix anyway. As a workaround, you can run "virsh undefine i-00000001" to remove the old definition (and do a virsh list --all to see if you have i-000002 etc). It wouldn't be safe to do that from code for new / unknown domains. However, the problem then shouldn't occur going forwards, and shouldn't occur anyway if you don't reset your DB.