public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: hollisb@us.ibm.com, kvm@vger.kernel.org
Subject: Re: [PATCH] [PATCH] qemu: report issues causing the kvm probe to fail
Date: Mon, 15 Dec 2008 14:26:52 +0100	[thread overview]
Message-ID: <49465B1C.8010900@linux.vnet.ibm.com> (raw)
In-Reply-To: <494631D6.3080807@redhat.com>

Avi Kivity wrote:
> Christian Ehrhardt wrote:
>> I ran into the issue of a failign KVM Probe of the qemu configure 
>> script three
>> times this week always needing "set -x", inserting an exit, masking 
>> the cleanup
>> trap and compiling the c file by hand until I knew what the reason 
>> is. I think
>> we could make easier for developers and end users.
>> Therefore this patch keeps the qemu style configure output which is a 
>> list of
>> "$Feature $Status", but extend the "no" result like "KVM Support no" 
>> with some
>> more information.
>>
>> There might be a lot of things going wrong with that probe and I 
>> don't want
>> to handle all of them, but if it is one of the known checks e.g. for
>> KVM_API_VERSION then we could grep/awk that out and report it. The patch
>> reports in case of a known case in the style
>> "KVM support no - (Missing KVM capability 
>> KVM_CAP_DESTROY_MEMORY_REGION_WORKS)"
>>
>> In case more than one #error is triggered it creates a comma 
>> separated list in
>> those brackets and in case it is something else than an #error it 
>> just reports
>> plain old "no".
>>
>> diff --git a/qemu/configure b/qemu/configure
>> --- a/qemu/configure
>> +++ b/qemu/configure
>> @@ -1037,12 +1037,14 @@ if test "$kvm" = "yes" ; then
>>  if test "$kvm" = "yes" ; then
>>      cat > $TMPC <<EOF
>>  #include <linux/kvm.h>
>> -#if !defined(KVM_API_VERSION) || \
>> -    KVM_API_VERSION < 12 || \
>> -    KVM_API_VERSION > 12 || \
>> -    !defined(KVM_CAP_USER_MEMORY) || \
>> -    !defined(KVM_CAP_SET_TSS_ADDR)
>> +#if !defined(KVM_API_VERSION) || KVM_API_VERSION < 12 || 
>> KVM_API_VERSION > 12
>>  #error Invalid KVM version
>>   
>
> You might refine this a bit:  if KVM_API_VERSION is not defined, most 
> likely linux/kvm.h could not be found, so you might as well report that.
>
>> +#endif
>>   
>
>
Updated v2 should appear on the list soon reporting all gcc "error:" 
messages.

-- 

Grüsse / regards, 
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization


      reply	other threads:[~2008-12-15 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 16:40 [PATCH] [PATCH] qemu: report issues causing the kvm probe to fail Christian Ehrhardt
2008-12-15 10:30 ` Avi Kivity
2008-12-15 13:26   ` Christian Ehrhardt [this message]

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=49465B1C.8010900@linux.vnet.ibm.com \
    --to=ehrhardt@linux.vnet.ibm.com \
    --cc=avi@redhat.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    /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