From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@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: Tue, 09 Oct 2007 15:28:20 +0200 [thread overview]
Message-ID: <470B81F4.8000806@qumranet.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710081411160.27239-4mf1WHGLwUrYtjvyW6yDsg@public.gmane.org>
Byron Stanoszek wrote:
> 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.
>
The window title bar says 'QEMU/KVM' instead of 'QEMU' when kvm is active.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
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/
prev parent reply other threads:[~2007-10-09 13:28 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
[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 [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=470B81F4.8000806@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@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