All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, akrowiak@linux.vnet.ibm.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH V2 for-2.3] util/qemu-config: fix regression of qmp_query_command_line_options
Date: Wed, 01 Apr 2015 12:20:30 -0600	[thread overview]
Message-ID: <551C36EE.6060103@redhat.com> (raw)
In-Reply-To: <551C2CAE.9000108@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]

On 04/01/2015 11:36 AM, Marcel Apfelbaum wrote:
> On 04/01/2015 08:29 PM, Eric Blake wrote:
>> On 04/01/2015 10:47 AM, Marcel Apfelbaum wrote:
>>> Commit 49d2e64 (machine: remove qemu_machine_opts global list)
>>> made machine options specific to machine sub-type, leaving
>>> the qemu_machine_opts desc array empty. Sadly this is the place
>>> qmp_query_command_line_options is looking for supported options.
>>>
>>> As a fix for for 2.3 the machine_qemu_opts (the generic ones)
>>> are restored only for qemu-config scope.
>>> We need to find a better fix for 2.4.
>>>
>>> Reported-by: Tony Krowiak <akrowiak@linux.vnet.ibm.com>
>>> Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
>>> ---

>>
>> No longer a strict superset of the Fedora 21 qemu-kvm, which had:
>>
>>              "parameters": [
>>                  {
>>                      "name": "max-ram-below-4g",

>>                      "name": "kvm-type",

>> (remembering that query-command-line-options does things in reverse
>> order).  I don't think iommu and suppress-vmdesc hurt to add, but we
>> shouldn't lose kvm-type or max-ram-below-4g, if those were advertised at
>> the point prior to the QemuOpts conversion.  (I didn't actually
>> research, though, whether I'm comparing against downstream Fedora
>> qemu-kvm patches instead of upstream...)
> Hmm, in 2.3 kvm-type and max-ram-below-4g are machine specific.
> I only took the ones from hw/core/machine.c that are common to all
> machines.
> As you said, this approach does the best to not lie to libvirt...

And luckily, libvirt is not (currently) looking for either 'kvm-type' or
'max-ram-below-4g'.  So, I can live with this, and from the point of
view of libvirt's interaction with qemu:

Reviewed-by: Eric Blake <eblake@redhat.com>

Tested-by: Eric Blake <eblake@redhat.com>

-- 
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: 604 bytes --]

  reply	other threads:[~2015-04-01 18:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 16:47 [Qemu-devel] [PATCH V2 for-2.3] util/qemu-config: fix regression of qmp_query_command_line_options Marcel Apfelbaum
2015-04-01 17:27 ` Marcel Apfelbaum
2015-04-01 17:29 ` Eric Blake
2015-04-01 17:36   ` Marcel Apfelbaum
2015-04-01 18:20     ` Eric Blake [this message]
2015-04-02 12:38 ` Paolo Bonzini

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=551C36EE.6060103@redhat.com \
    --to=eblake@redhat.com \
    --cc=akrowiak@linux.vnet.ibm.com \
    --cc=armbru@redhat.com \
    --cc=marcel@redhat.com \
    --cc=pbonzini@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.