qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Michal Novotny <minovotn@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] vl.c: Output error on invalid machine type provided
Date: Tue, 30 Jul 2013 13:29:22 -0600	[thread overview]
Message-ID: <51F81412.10809@redhat.com> (raw)
In-Reply-To: <7f847cb5fd7c350e1460df5772c5a0481bc77b3c.1375211373.git.minovotn@redhat.com>

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

On 07/30/2013 01:10 PM, Michal Novotny wrote:
> Output error message when user provides the invalid machine type
> on the command line. This also saves time to find what issue is
> when you upgrade from one version of qemu to another version that
> doesn't support required machine type any longer.

I know that has historically happened downstream (for example, Fedora 13
made the mistake of creating a downstream-only fedora-13 machine type
that corresponded roughly to qemu 0.13, it took some further Fedora
patches to libvirt to modernize that name back to an upstream machine
type on an upgrade path before finally being able to drop the downstream
nonsense in Fedora 18 or so).  But isn't upstream qemu supposed to be
guaranteeing command-line stability, in that a newer qemu will never
take away a machine type supported by an older qemu?

But even if the upstream upgrade path never hits this code, your patch
will make it nicer if you _downgrade_ to a version of qemu (still with
this patch, of course) that lacks support for a newer machine.  And the
fact that downstream will take advantage of this even if upstream never
causes the problem on upgrades still justifies using it.

> 
> Signed-off-by: Michal Novotny <minovotn@redhat.com>
> 
> ---
> The patch is checked using ./scripts/checkpatch.pl script and
> also is_help_option() function is being used.
>  vl.c | 5 +++++
>  1 file changed, 5 insertions(+)

Reviewed-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: 621 bytes --]

  reply	other threads:[~2013-07-30 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 19:10 [Qemu-devel] [PATCH v3] vl.c: Output error on invalid machine type provided Michal Novotny
2013-07-30 19:29 ` Eric Blake [this message]
2013-07-31  6:37   ` Michal Novotny

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=51F81412.10809@redhat.com \
    --to=eblake@redhat.com \
    --cc=minovotn@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).