From: Avi Kivity <avi@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Alexander Graf <agraf@suse.de>,
Anthony Liguori <anthony@codemonkey.ws>,
Chris Wright <chrisw@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call agenda for Jan 26
Date: Tue, 26 Jan 2010 15:45:06 +0200 [thread overview]
Message-ID: <4B5EF1E2.5080900@redhat.com> (raw)
In-Reply-To: <20100126133325.GI5366@redhat.com>
On 01/26/2010 03:33 PM, Daniel P. Berrange wrote:
>
>> Me too, especially as the whole stack is involved, and qemu is the
>> topmost part from our perspective (no doubt libvirt will want to
>> integrate that functionality as well).
>>
> FYI, libvirt already exposes this kind of functionality. The API call
> virConnectGetCapabilities() / command line "virsh capabilities" command
> tells you about what the virtualization host is able to support. It can
> tell you what architectures are supported, by which binaries. What
> machine types are available. Whether KVM or KQEMU acceleration are
> present. What CPU model / flags are on the host. What NUMA topology is
> available. etc etc
>
>
Great. Note that for a cpu flag to be usable in a guest, it needs to be
supported by both kvm.ko and qemu, so reporting /proc/cpuinfo is
insufficient. There are also synthetic cpu flags (kvm paravirt
features, x2apic) that aren't present in /proc/cpuinfo.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call agenda for Jan 26
Date: Tue, 26 Jan 2010 15:45:06 +0200 [thread overview]
Message-ID: <4B5EF1E2.5080900@redhat.com> (raw)
In-Reply-To: <20100126133325.GI5366@redhat.com>
On 01/26/2010 03:33 PM, Daniel P. Berrange wrote:
>
>> Me too, especially as the whole stack is involved, and qemu is the
>> topmost part from our perspective (no doubt libvirt will want to
>> integrate that functionality as well).
>>
> FYI, libvirt already exposes this kind of functionality. The API call
> virConnectGetCapabilities() / command line "virsh capabilities" command
> tells you about what the virtualization host is able to support. It can
> tell you what architectures are supported, by which binaries. What
> machine types are available. Whether KVM or KQEMU acceleration are
> present. What CPU model / flags are on the host. What NUMA topology is
> available. etc etc
>
>
Great. Note that for a cpu flag to be usable in a guest, it needs to be
supported by both kvm.ko and qemu, so reporting /proc/cpuinfo is
insufficient. There are also synthetic cpu flags (kvm paravirt
features, x2apic) that aren't present in /proc/cpuinfo.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-01-26 13:45 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 6:49 KVM call agenda for Jan 26 Chris Wright
2010-01-26 6:49 ` [Qemu-devel] " Chris Wright
2010-01-26 9:09 ` Alexander Graf
2010-01-26 9:09 ` [Qemu-devel] " Alexander Graf
2010-01-26 13:11 ` Anthony Liguori
2010-01-26 13:11 ` [Qemu-devel] " Anthony Liguori
2010-01-26 13:17 ` Avi Kivity
2010-01-26 13:17 ` [Qemu-devel] " Avi Kivity
2010-01-26 13:18 ` Alexander Graf
2010-01-26 13:18 ` [Qemu-devel] " Alexander Graf
2010-01-26 13:24 ` Avi Kivity
2010-01-26 13:24 ` [Qemu-devel] " Avi Kivity
2010-01-26 13:33 ` Daniel P. Berrange
2010-01-26 13:33 ` [Qemu-devel] " Daniel P. Berrange
2010-01-26 13:37 ` Alexander Graf
2010-01-26 13:37 ` [Qemu-devel] " Alexander Graf
2010-01-26 13:45 ` Avi Kivity [this message]
2010-01-26 13:45 ` Avi Kivity
2010-01-26 14:13 ` Anthony Liguori
2010-01-26 14:13 ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:15 ` Avi Kivity
2010-01-26 14:15 ` [Qemu-devel] " Avi Kivity
2010-01-26 14:22 ` Anthony Liguori
2010-01-26 14:22 ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:26 ` Avi Kivity
2010-01-26 14:26 ` [Qemu-devel] " Avi Kivity
2010-01-26 14:32 ` Anthony Liguori
2010-01-26 14:32 ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:37 ` Avi Kivity
2010-01-26 14:37 ` [Qemu-devel] " Avi Kivity
2010-01-26 14:42 ` Alexander Graf
2010-01-26 14:42 ` [Qemu-devel] " Alexander Graf
2010-01-26 14:47 ` Avi Kivity
2010-01-26 14:47 ` [Qemu-devel] " Avi Kivity
2010-01-26 14:50 ` Alexander Graf
2010-01-26 14:50 ` [Qemu-devel] " Alexander Graf
2010-01-26 14:59 ` Anthony Liguori
2010-01-26 14:59 ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:42 ` Anthony Liguori
2010-01-26 14:42 ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:44 ` Avi Kivity
2010-01-26 14:44 ` [Qemu-devel] " 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=4B5EF1E2.5080900@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=berrange@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.