Description of problem:
In making and deleting a lot of domU instances, I've occasionally used a name
more than once. Even if it was previously deleted, virt-manager always gives an
error about the name being used before. It then proceeds to start the install
even though I go back and change the name. This is confusing to say the least.
Version-Release number of selected component (if applicable):
happens every time
Steps to Reproduce:
1. see above
Hmm, good catch, thanks. This turns out to be a nasty python reference-counting
bug (we think). Working on a fix now.
The patch below fixes the problem by forcing libvirt to release the underlying
pointer to the domain object, even though the python code doesn't always release
the reference reliably.
Created attachment 159881 [details]
Aggressively free domain pointer in libvirt
This patch aggressively frees the domain pointer in libvirt so that when you
create a domain with the same name as one you just deleted, the deleted domain
configuration doesn't get resurrected in virt-manager.
*** Bug 251489 has been marked as a duplicate of this bug. ***
For reference, this bug is addressed in virt-manager-0.4.0-3.el5
* Tue Jul 24 2007 Hugh O. Brock <email@example.com> - 0.4.0-3.el5
- Aggressively free libvirt domain object after it has been deleted. Workaround
for python's unreliable garbage collection. (rhbz #249094)
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.