Description of problem: Received a message that a domain is in use when attempting to create it, even though the domain isn't in use. Version-Release number of selected component (if applicable): Latest 5.4 xen. How reproducible: 50% Steps to Reproduce: 1. Use halt command to shutdown a linux vm. 2. Attempt to create the vm with 'xm create -c $VM' 3. Actual results: # xm create -c raw-64pv Using config file "/etc/xen/raw-64pv". Error: VM name 'raw-64pv' already in use by domain 216 Expected results: vm creates, since it's actually not in use. Additional info: If 'xm list' or possibly other xm commands are run before the 'xm create' command, then 'xm create' will succeed.
Regression between 5.4 (xen-3.0.3-94.el5) and xen-3.0.3-95.el5. Raising priority and taking care of it (I think I know where the problem is)... BTW I can reproduce it almost in 100% cases on -95.el5.
Created attachment 370045 [details] Fix domain name conflicts after domain shutdown
Verified on -102.el5 Here are the details of the testing: x86-64-Server: Tried 20 times and no reproduction i386-Server: Tried 20 times and no reproduction ia64:Tried 20 times and no reproduction i386-Client: Tried 30 times and no reproduction x86-64-Client:Tried 25 times and no reproduction
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 therefore 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. http://rhn.redhat.com/errata/RHBA-2010-0294.html
This bug was closed during 5.5 development and it's being removed from the internal tracking bugs (which are now for 5.6).