From: Paolo Bonzini <pbonzini@redhat.com>
To: Bandan Das <bsd@redhat.com>
Cc: kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] x86-run: Print a meaningful message if the qemu binary isn't found
Date: Thu, 09 Apr 2015 19:17:19 +0200 [thread overview]
Message-ID: <5526B41F.8020205@redhat.com> (raw)
In-Reply-To: <jpgwq1lrzqb.fsf@redhat.com>
On 09/04/2015 19:14, Bandan Das wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
> ...
>> This breaks "QEMU=... ./x86-run ./x86/msr.flat"
>>
>> Fixed as follows:
>>
>> diff --git a/x86/run b/x86/run
>> index d5adf8d..219a93b 100755
>> --- a/x86/run
>> +++ b/x86/run
>> @@ -20,16 +20,15 @@ else
>> break
>> fi
>> done
>> -fi
>> -
>> -if [ -z "${QEMUFOUND}" ]
>> -then
>> - echo "A QEMU binary was not found, You can set a custom location by using the QEMU=<path> environment variable "
>> - exit ${NOTFOUND}
>> -elif [ -z "${qemu}" ]
>> -then
>> - echo "No Qemu test device support found"
>> - exit ${TESTDEVNOTSUPP}
>> + if [ -z "${QEMUFOUND}" ]
>> + then
>> + echo "A QEMU binary was not found, You can set a custom location by using the QEMU=<path> environment variable "
>> + exit ${NOTFOUND}
>> + elif [ -z "${qemu}" ]
>> + then
>> + echo "No Qemu test device support found"
>
> I think we still want to print this if the user supplied qemu has no test
> device support.
Yes, but we do not go through the "for" in that case...
Can you make a patch on top of master?
Paolo
next prev parent reply other threads:[~2015-04-09 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 21:12 [PATCH] x86-run: Print a meaningful message if the qemu binary isn't found Bandan Das
2015-04-02 12:47 ` Paolo Bonzini
2015-04-09 16:44 ` Paolo Bonzini
2015-04-09 17:14 ` Bandan Das
2015-04-09 17:17 ` Paolo Bonzini [this message]
2015-04-09 17:20 ` Bandan Das
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5526B41F.8020205@redhat.com \
--to=pbonzini@redhat.com \
--cc=bsd@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox