From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "You, Yongkang" <yongkang.you-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Is there any accurate way to check if Qemu is using KVM modules?
Date: Tue, 19 Jun 2007 17:49:48 +0300 [thread overview]
Message-ID: <4677ED0C.9090309@qumranet.com> (raw)
In-Reply-To: <094BCE01AFBE9646AF220B0B3F367AABCDA148-wq7ZOvIWXbMgGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
You, Yongkang wrote:
>>> I am a newbie for KVM testing.
>>> Now I meet a problem in testing, that it seems there isn't a simple and
>>>
>> effective way to judge if a Qemu is using KVM modules or doing pure Qemu
>> operations.
>>
>>> Checking how many reference of kvm.ko by lsmod is a way, but would meet
>>>
>> trouble when creating multi KVM guest at the same time. And can not locate
>> which one is using KVM modules.
>>
>>> I also checked /sys file system, but didn't get any reference. Is it possible to
>>>
>> expose some useful information about KVM/Qemu alive status and cpu
>> assignment/usage information in the user space. This would be a good friend
>> to customer and tester. :)
>>
>> I believe there is an 'info kqemu' command in the qemu monitor. It would
>> be a good idea to implement an 'info kvm' to get such information in a
>> systematic way.
>>
>>
> Hi Avi,
>
> I tried 'info kqemu' in Qemu monitor. But I always got the same result: "kqemu supported : not compiled". Is it correct?
>
>
Yes. I gave kqemu as an example (kqemu is similar to kvm, but does not
use hardware acceleration). We'll need to implement 'info kvm' in a
similar way (it would report the value of the kvm_allowed variable).
--
error compiling committee.c: too many arguments to function
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- Attachment #3: Type: text/plain, Size: 186 bytes --]
_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel
prev parent reply other threads:[~2007-06-19 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 14:12 Is there any accurate way to check if Qemu is using KVM modules? You, Yongkang
[not found] ` <094BCE01AFBE9646AF220B0B3F367AABCDA146-wq7ZOvIWXbMgGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-06-19 14:17 ` Avi Kivity
[not found] ` <4677E578.6060800-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-19 14:42 ` You, Yongkang
[not found] ` <094BCE01AFBE9646AF220B0B3F367AABCDA148-wq7ZOvIWXbMgGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-06-19 14:49 ` 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=4677ED0C.9090309@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=yongkang.you-ral2JQCrhuEAvxtiuMwx3w@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