From: Peter Maydell <peter.maydell@linaro.org>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Martin Kletzander <mkletzan@redhat.com>,
Libvirt <libvir-list@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [libvirt] [PATCH 3/5] qemu: add QEMU_CAPS_MACHINE_VMPORT_OPT
Date: Mon, 20 Apr 2015 15:54:20 +0100 [thread overview]
Message-ID: <CAFEAcA_NVCO904WSYwyKzSh6SG9+MvYEZ7jJJkdGN7AMddAgJQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ+F1CJaCCi9zq9ygyPjvpMFAbs=FmwFA=72fAMdpZkzq80-mw@mail.gmail.com>
On 20 April 2015 at 13:39, Marc-André Lureau <marcandre.lureau@gmail.com> wrote:
> Hi
>
> On Tue, Apr 14, 2015 at 6:07 PM, Eric Blake <eblake@redhat.com> wrote:
>>
>> > + { "machine", "vmport", QEMU_CAPS_MACHINE_VMPORT_OPT },
>>
>> Ouch. qemu commit 0a7cf21 fixes what would have been a regression in
>> 2.3 at exposing "mem-merge" through query-command-line-options, but it
>> does NOT expose "vmport", which is a per-architecture option rather than
>> a generic -machine option. Which means that even though qemu 2.2
>> (perhaps wrongly) advertised "vmport" for all machines (even when it was
>> not supported), 2.3 will not advertise it, and we are hoping for a
>> better solution in 2.4 for properly advertising vmport on an
>> as-appropriate basis.
>
>
> Thanks Eric for finding out this regression.
>
> Is anybody working on a better solution? I can imagine either a new qmp
> machine-list-properties, or perhaps more reasonably a new properties array
> in query-machines reply.
Unless this is an absolutely critical "we cannot ship 2.3 without
a fix" bug (in which case somebody should yell now and you really
need a patch on the list within a day or so), you've probably missed
the 2.3 boat at this point.
-- PMM
prev parent reply other threads:[~2015-04-20 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1427994155-25043-1-git-send-email-marcandre.lureau@gmail.com>
[not found] ` <1427994155-25043-4-git-send-email-marcandre.lureau@gmail.com>
[not found] ` <20150414142507.GI4131@wheatley>
[not found] ` <CAJ+F1CKrdygm-Dkhpsq06yHjM4ampZb1sBeJV-b2HJOgJCmRrA@mail.gmail.com>
2015-04-14 16:07 ` [Qemu-devel] [libvirt] [PATCH 3/5] qemu: add QEMU_CAPS_MACHINE_VMPORT_OPT Eric Blake
2015-04-14 16:27 ` Martin Kletzander
2015-04-20 12:39 ` Marc-André Lureau
2015-04-20 14:54 ` Peter Maydell [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=CAFEAcA_NVCO904WSYwyKzSh6SG9+MvYEZ7jJJkdGN7AMddAgJQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=libvir-list@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mkletzan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).