Bug 211697

Summary: xm create <guest> gives an inscrutable error message when it picks up the wrong config file
Product: Red Hat Enterprise Linux 5 Reporter: Hugh Brock <hbrock>
Component: xenAssignee: Rik van Riel <riel>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: gcosta, xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: beta2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-23 01:33:31 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:
Attachments:
Description Flags
Fix proposal none

Description Hugh Brock 2006-10-20 21:08:53 UTC 
Description of problem:
xm create <guest> searches for a file named <guest> on the path. If it finds one
before the correct one in /etc/xen, it will try to use it; if the file is a
binary file, the error message complains about unparseable characters in the
file, rather than indicating that it may have found the wrong file.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Place a binary file named <guest> on the search path
2. type "xm create <guest>"
3.
  
Actual results:
Error message about unexpected binary characters in config file

Expected results:
Error message about finding a file with the same name as the config file that is
not the config file

Additional info:
Comment 1 Glauber Costa 2006-10-20 21:30:08 UTC 
Created attachment 139033 [details]
Fix proposal

I've just sent this patch to mainstream, which gives a more descriptive error
message.
Comment 2 Glauber Costa 2006-10-27 13:23:03 UTC 
just got upstream
Comment 3 RHEL Program Management 2006-10-27 13:25:31 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux release.  Product Management has requested further review
of this request by Red Hat Engineering.  This request is not yet committed for
inclusion in release.
Comment 4 Rod Nayfield 2006-10-27 13:38:33 UTC 
I have seen this problem manifest itself in milestone 6.   This patch is very
necessary, especially since our tools don't offer naming conventions (no .img by
default) ... so if you are in /xen you can't start machines when diskname ==
config name
Comment 5 Rik van Riel 2006-11-09 02:47:03 UTC 
Damnit, no QA ack yet :(
Comment 7 Jay Turner 2006-11-20 20:14:12 UTC 
QE ack for RHEL5.
Comment 8 Rik van Riel 2006-12-05 22:09:50 UTC 
in 3.0.3-9.el5
Comment 9 RHEL Program Management 2006-12-23 01:33:31 UTC 
A package has been built which should help the problem described in 
this bug report. This report is therefore being closed with a resolution 
of CURRENTRELEASE. You may reopen this bug report if the solution does 
not work for you.