public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Byron Stanoszek <bstanoszek-vdaza9t/se1BDgjK7y7TUQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Carlo Marcelo Arenas Belon
	<carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
Subject: Re: [PATCH] Abort if gcc4 was used to compile qemu and kvm is not enabled
Date: Mon, 08 Oct 2007 14:29:32 -0500	[thread overview]
Message-ID: <470A851C.3050602@codemonkey.ws> (raw)
In-Reply-To: <Pine.LNX.4.64.0710081411160.27239-4mf1WHGLwUrYtjvyW6yDsg@public.gmane.org>

Byron Stanoszek wrote:
> On Mon, 8 Oct 2007, Anthony Liguori wrote:
>>
>> If you're going to do anything, a firm warning when compiling with a
>> GCC4 override would be the best thing.
>
> I disagree with the compile warning. There have been times in the past 
> when
> I've forgotten to "insmod kvm*.ko" long after the compile stage, and 
> wound up
> wondering why the virtual machine was slower. Even when I first 
> started using
> KVM, I had no positive feedback that KVM was even working properly 
> (was the
> device node created? am I using a cpu with the correct extensions? 
> etc). I
> eventually figured out that if 'lsmod' showed kvm-intel.ko usage > 0, 
> then I
> knew it was working.

You don't have to have kvm.ko insmod'd during compile.  Presumably the 
issue you were seeing is that you built a version of QEMU without KVM 
support.  Were you using the top-level configure script?

> I would think that anyone who is using KVM has the required hardware 
> and wants
> to be sure that KVM is really being used. Specifying -no-kvm is an 
> excellent
> tool for debugging purposes, but I don't want KVM to fail silently on 
> me and
> pretend that I typed -no-kvm, especially if I'm using GCC 4.x and never
> intended to use the QEMU portion anyway.

Eventually, KVM will merge with upstream QEMU.  In that case, many 
people will be using QEMU without the desiring to use KVM.  We don't 
want to introduce behavior in QEMU that is unmergable with upstream QEMU 
b/c that will just cause users more headache when that behavior is 
eventually change.

Regards,

Anthony Liguori

> I would much rather see KVM fail gracefully, rather than revert to QEMU,
> regardless of the compiler version being used.
>
>  -Byron
>
> -- 
> Byron Stanoszek                         Ph: (330) 644-3059
> Systems Programmer                      Fax: (330) 644-8110
> Commercial Timesharing Inc.             Email: byron-vdaza9t/se1BDgjK7y7TUQ@public.gmane.org
>


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  parent reply	other threads:[~2007-10-08 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 15:44 [PATCH] Abort if gcc4 was used to compile qemu and kvm is not enabled Carlo Marcelo Arenas Belon
2007-10-08 15:53 ` Anthony Liguori
     [not found]   ` <470A5290.4040504-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-10-08 18:45     ` Byron Stanoszek
     [not found]       ` <Pine.LNX.4.64.0710081411160.27239-4mf1WHGLwUrYtjvyW6yDsg@public.gmane.org>
2007-10-08 19:29         ` Anthony Liguori [this message]
     [not found]           ` <470A851C.3050602-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-10-09  6:46             ` Carlo Marcelo Arenas Belon
2007-10-09 14:53               ` Anthony Liguori
2007-10-09 13:28         ` Avi Kivity

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=470A851C.3050602@codemonkey.ws \
    --to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
    --cc=bstanoszek-vdaza9t/se1BDgjK7y7TUQ@public.gmane.org \
    --cc=carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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