Red Hat Bugzilla – Bug 467660
virDomainLookupByUUIDString fail after virDomainDestroy
Last modified: 2009-12-16 07:31:05 EST
Description of problem:
if i want to use virDomainLookupByUUIDString to get a domain object immediately after virDomainDestroy, it failed with message "internal error domain information incomplete, missing domid".
But if i wait for a while such as sleep(6) after virDomainDestroy, then virDomainLookupByUUIDString success.
Version-Release number of selected component (if applicable):
just call virDomainLookupByUUIDString immediately after virDomainDestroy.
Steps to Reproduce:
virDomainLookupByUUIDString return NULL.
return a valid domain object.
This is probably a race condition in XenD in the way it cleans up domains. After destroying it, there is a short window in which information may still be visible. This is what's causing the error message from libvirt. I'm not sure we can fix this problem
This is more than one year old now, and it's not a good idea to keep this
in the current state.
Closing as WONT FIX, as the complexity of the Xen stack here means
it's unlikely we could ever get something close to an atomic operation