From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Bruce Rogers <brogers@novell.com>
Subject: Re: [Qemu-devel] [PATCH] move 'unsafe' to end of caching modes in help
Date: Wed, 21 Jul 2010 16:45:46 -0500 [thread overview]
Message-ID: <4C476A8A.6000707@codemonkey.ws> (raw)
In-Reply-To: <20100721213238.GB28871@redhat.com>
On 07/21/2010 04:32 PM, Daniel P. Berrange wrote:
> On Wed, Jul 21, 2010 at 03:55:28PM -0500, Anthony Liguori wrote:
>
>> On 07/21/2010 03:32 PM, Bruce Rogers wrote:
>>
>>> Libvirt parses qemu help output to determine qemu features. In particular
>>> it probes for the following: "cache=writethrough|writeback|none". The
>>> addition of the unsafe cache mode was inserted within this string, as
>>> opposed to being added to the end, which impacted libvirt's probe.
>>> Unbreak libvirt by keeping the existing cache modes intact and add
>>> unsafe to the end.
>>>
>>> This problem only manifests itself if a caching mode is explicitly
>>> specified in the libvirt xml, in which case older syntax for caching is
>>> passed to qemu, which it no longer understands.
>>>
>>> Signed-off-by: Bruce Rogers<brogers@novell.com>
>>>
>>>
>> Errr, libvirt is still doing this?
>>
>> This comes up frequently and it's a real PITA. Help text is not a
>> feature probing interface. This is a libvirt bug and it needs to be
>> fixed in libvirt
>>
> Of course, there is no viable alternative yet.
Yes there is. Use the version number.
Regards,
Anthony Liguori
> The QMP patches I
> sent a few weeks back now to add ability to query capabilities were
> intended to provide the neccessary support in QEMU for us to use
> instead of -help. Given that QMP isn't going to be declared stable
> in 0.13 though, it looks like we'll be continuing to use -help
> until the 0.14 release of QEMU.
>
>
> Regards,
> Daniel
>
next prev parent reply other threads:[~2010-07-21 21:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 20:32 [Qemu-devel] [PATCH] move 'unsafe' to end of caching modes in help Bruce Rogers
2010-07-21 20:55 ` Anthony Liguori
2010-07-21 21:32 ` Daniel P. Berrange
2010-07-21 21:45 ` Anthony Liguori [this message]
2010-07-21 21:58 ` Daniel P. Berrange
2010-07-21 23:39 ` Anthony Liguori
2010-07-22 0:45 ` Jamie Lokier
2010-07-22 6:53 ` Markus Armbruster
2010-07-22 8:42 ` Daniel P. Berrange
2010-07-22 14:19 ` Anthony Liguori
2010-07-23 8:00 ` Markus Armbruster
2010-07-26 15:53 ` Anthony Liguori
2010-07-26 16:26 ` Avi Kivity
2010-07-26 16:29 ` Avi Kivity
2010-07-26 19:03 ` Anthony Liguori
2010-07-26 19:24 ` Avi Kivity
2010-07-26 19:43 ` [Qemu-devel] " Juan Quintela
2010-07-26 16:40 ` [Qemu-devel] " Anthony Liguori
2010-07-26 16:54 ` Avi Kivity
2010-07-26 18:59 ` Anthony Liguori
2010-07-26 19:19 ` Avi Kivity
2010-07-26 19:35 ` Anthony Liguori
2010-07-26 19:43 ` Avi Kivity
2010-07-26 20:03 ` Anthony Liguori
2010-07-27 8:11 ` Markus Armbruster
2010-07-27 9:47 ` Jes Sorensen
2010-07-27 12:30 ` Cole Robinson
2010-07-27 12:50 ` Anthony Liguori
2010-07-27 13:35 ` Cole Robinson
2010-07-27 8:26 ` Markus Armbruster
2010-08-03 9:43 ` Richard W.M. Jones
2010-07-27 8:56 ` Kevin Wolf
2010-07-22 13:45 ` Luiz Capitulino
2010-07-27 10:26 ` Daniel P. Berrange
2010-07-27 13:11 ` Bruce Rogers
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=4C476A8A.6000707@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=berrange@redhat.com \
--cc=brogers@novell.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).