From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: libvir-list@redhat.com, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [libvirt] [PATCH 6/7] qemu: Probe QEMU binary for host CPU
Date: Tue, 23 Jul 2013 10:27:05 -0600 [thread overview]
Message-ID: <51EEAED9.6050308@redhat.com> (raw)
In-Reply-To: <20130723161903.GL2477@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]
[adding qemu]
On 07/23/2013 10:19 AM, Daniel P. Berrange wrote:
> On Tue, Jul 23, 2013 at 06:11:35PM +0200, Jiri Denemark wrote:
>> Since QEMU and kvm may filter some host CPU features or add efficiently
>> emulated features, asking QEMU binary for host CPU data provides
>> better results when we later use the data for building guest CPUs.
>> ---
>> + virCommandAddArg(cmd, "-machine");
>> + virCommandAddArgFormat(cmd, "%s,accel=kvm",
>> + qemuCaps->machineTypes[0]);
>> +
>
>
> This code is causing us to invoke the QEMU binary multiple times,
> which is something we worked really hard to get away from. I really,
> really don't like this as an approach. QEMU needs to be able to
> give us the data we need here without multiple invocations.
>
> eg, by allowing the monitor command to specify 'kvm' vs 'qemu'
> when asking for data, so you can interrogate it without having
> to re-launch it with different accel=XXX args.
We don't know if -machine accel=kvm is a valid option until after
issuing some QMP commands, but now we are forced to reinvoke a new qemu
with -machine accel=kvm enabled in order to get the query to give us
accurate answers. I agree that this is less than desirable; hopefully
the qemu folks can help us figure out a solution, now that we are
bringing attention to the issue.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next parent reply other threads:[~2013-07-23 16:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1374595782.git.jdenemar@redhat.com>
[not found] ` <dd23e4f4185196f173b78196cf47e4fe2dfc0057.1374595782.git.jdenemar@redhat.com>
[not found] ` <20130723161903.GL2477@redhat.com>
2013-07-23 16:27 ` Eric Blake [this message]
2013-07-24 18:10 ` [Qemu-devel] [libvirt] [PATCH 6/7] qemu: Probe QEMU binary for host CPU Eduardo Habkost
[not found] ` <00920fe1cd728db02fa4c81602b359986a3cf2a1.1374595782.git.jdenemar@redhat.com>
[not found] ` <20130723163242.GQ2477@redhat.com>
[not found] ` <20130723172838.GJ4718@orkuz.home>
[not found] ` <20130723173246.GK4718@orkuz.home>
2013-07-24 18:25 ` [Qemu-devel] [libvirt] [PATCH 4/7] qemu: Add monitor APIs to fetch CPUID data from QEMU Eduardo Habkost
2013-07-25 9:14 ` Andreas Färber
2013-07-25 14:00 ` Eduardo Habkost
2013-07-25 14:09 ` Andreas Färber
2013-07-25 14:13 ` Daniel P. Berrange
2013-07-25 18:02 ` Eduardo Habkost
2013-07-26 12:31 ` Andreas Färber
2013-07-26 13:51 ` Eduardo Habkost
2013-07-25 9:45 ` Daniel P. Berrange
2013-07-25 13:15 ` Eduardo Habkost
2013-07-25 14:22 ` Daniel P. Berrange
[not found] ` <20130724100302.GK30336@redhat.com>
2013-07-24 18:31 ` Eduardo Habkost
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=51EEAED9.6050308@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=libvir-list@redhat.com \
--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.