On Thu, Jul 26, 2007 at 02:50:56PM +0900, Masayuki Sunou wrote: > Hi > > I notice that the following two changesets were committed to the > repository of virt-manager today. > > - changeset: Try and force GC of domain objects > - changeset: Second attempt at forcing release of virDomainPtr objects > > Will you tell me whether these are the fixing for the following bug > that I issued? > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=246198 > --> This problem is not found when I test it today. Yes, that could cause that kind of problem. Basically the deallocation within libvirt was dependant on Python garbage collector deallocation of the unreferenced Python object for the domain, and sometimes this wasn't done before a new domain with the same name was created again, leading to clash between libvirt internal cache for the old but still present domain object and the new one being created. I think this bug has been around nearly forever, taking different shape from an user perspective depending on the situation, and 246198 looks very much like one of those. Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard@xxxxxxxxxx | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
