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):
Steps to Reproduce:
1. Place a binary file named <guest> on the search path
2. type "xm create <guest>"
Error message about unexpected binary characters in config file
Error message about finding a file with the same name as the config file that is
not the config file
Created attachment 139033 [details]
I've just sent this patch to mainstream, which gives a more descriptive error
just got upstream
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.
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 ==
Damnit, no QA ack yet :(
QE ack for RHEL5.
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.