Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 529880

Summary: xm-create incorrectly states a vm is in use, when it isn't
Product: Red Hat Enterprise Linux 5 Reporter: Andrew Jones <drjones>
Component: xenAssignee: Jiri Denemark <jdenemar>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: urgent    
Version: 5.5CC: jdenemar, rwu, syeghiay, xen-maint
Target Milestone: rcKeywords: Regression, ZStream
Target Release: 5.5   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: xen-3.0.3-99.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-30 08:57:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 547289    
Attachments:
Description Flags
Fix domain name conflicts after domain shutdown
none
Fix domain name conflicts after domain shutdown none

Description Andrew Jones 2009-10-20 15:10:46 UTC
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.

Comment 1 Jiri Denemark 2009-10-21 09:21:46 UTC
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.

Comment 6 Jiri Denemark 2009-11-18 09:46:55 UTC
Created attachment 370045 [details]
Fix domain name conflicts after domain shutdown

Comment 13 Rita Wu 2009-12-28 10:44:03 UTC
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

Comment 15 errata-xmlrpc 2010-03-30 08:57:43 UTC
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

Comment 16 Paolo Bonzini 2010-04-08 15:44:36 UTC
This bug was closed during 5.5 development and it's being removed from the internal tracking bugs (which are now for 5.6).