From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
clalance@redhat.com, qemu-devel@nongnu.org,
Cole Robinson <crobinso@redhat.com>
Subject: [Qemu-devel] Re: [PATCH] Revive -version 'QEMU PC Emulator...'
Date: Fri, 14 May 2010 08:24:09 -0500 [thread overview]
Message-ID: <4BED4EF9.3090800@linux.vnet.ibm.com> (raw)
In-Reply-To: <4BEBF9A5.3070507@redhat.com>
On 05/13/2010 08:07 AM, Jes Sorensen wrote:
> On 05/13/10 15:04, Cole Robinson wrote:
>
>> On 05/13/2010 04:35 AM, Jes Sorensen wrote:
>>
>>> On 05/12/10 22:48, Cole Robinson wrote:
>>> I think rather than 1, it would be better to add a patch to libvirt to
>>> catch both formats. I know Chris Lalancette already cooked up a patch
>>> for this. Combined with the 2) patch I just posted, and 3) I think that
>>> should take care of the problems.
>>>
>> It doesn't solve the problem for existing libvirt installations. It's
>> not uncommon for users to track just the latest kvm releases without
>> upgrading libvirt: any future qemu or kvm release will break every
>> version of libvirt that exists today. Given that unfortunate case, I
>> still recommend reverting the 'PC' change at least for long enough for a
>> few fixed libvirt releases to make it into the wild.
>>
> But that is no different from what we have today. Users who update their
> qemu and see issues with libvirt can also be asked to update libvirt. I
> have already had several cases where I needed to do that anyway.
>
> I don't like reverting a change like this, just to schedule it to be
> reapplied again later.
>
The problem is, we've been down this road many times before. Every
time, the libvirt folks say they just need this one change for
compatibility and keep on using the help output. I understand that
that's the easiest thing to do so we need to make it easier for them to
do the right thing (which probably means making it harder to do the
wrong thing :-)).
So I'm willing to apply this patch but only as part of a larger series
that eliminates the need for libvirt to parse help output. The
important question is then, what information is libvirt getting from the
help output today.
Regards,
Anthony Liguori
> Cheers,
> Jes
>
>
next prev parent reply other threads:[~2010-05-14 13:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 20:29 [Qemu-devel] [PATCH] Revive -version 'QEMU PC Emulator...' Cole Robinson
2010-05-12 20:38 ` [Qemu-devel] " Jes Sorensen
2010-05-12 20:48 ` Cole Robinson
2010-05-13 8:35 ` Jes Sorensen
2010-05-13 13:04 ` Cole Robinson
2010-05-13 13:07 ` Jes Sorensen
2010-05-13 13:21 ` Daniel P. Berrange
2010-05-13 13:38 ` Luiz Capitulino
2010-05-13 14:00 ` Paul Brook
2010-05-13 19:20 ` Blue Swirl
2010-05-13 21:24 ` Stuart Brady
2010-05-14 13:24 ` Anthony Liguori [this message]
2010-05-14 13:54 ` Daniel P. Berrange
2010-05-14 14:22 ` Anthony Liguori
2010-05-14 14:42 ` Daniel P. Berrange
2010-05-14 14:52 ` Anthony Liguori
2010-05-14 15:02 ` Daniel P. Berrange
2010-05-14 15:08 ` Anthony Liguori
2010-05-14 13:17 ` Anthony Liguori
2010-05-14 13:25 ` Daniel P. Berrange
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=4BED4EF9.3090800@linux.vnet.ibm.com \
--to=aliguori@linux.vnet.ibm.com \
--cc=Jes.Sorensen@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=clalance@redhat.com \
--cc=crobinso@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).