qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Live migrate, inconsistent machine types - new machine type to fix?
Date: Tue, 22 Jul 2014 18:14:50 +0530	[thread overview]
Message-ID: <20140722124450.GB32103@grmbl.mre> (raw)
In-Reply-To: <F2544586-F6BC-47E5-83DD-ABC463FBBCE1@alex.org.uk>

On (Tue) 22 Jul 2014 [13:15:41], Alex Bligh wrote:
> 
> On 22 Jul 2014, at 12:54, Amit Shah <amit.shah@redhat.com> wrote:
> 
> > Sigh; please read both my replies.
> > 
> > The only difference between qemu-kvm-1.0 and qemu-1.0 is the presence
> > of the pci-assign section in qemu-kvm-1.0.  All other output from
> > qemu-1.0 -> qemu-2.1 is equally applicable to qemu-kvm-1.0 ->
> > qemu-2.1.
> ...
> > I know that; but you brought up the comparison of your experiments
> > with the output of the checker.  I just pointed out the checker
> > flagged both those things you saw (and a few others too).
> 
> Apologies for my naivety here as it's the first time I've looked
> at this stuff. So sorry if I'm getting the wrong end of the stick.
> 
> However, am I correct in assuming your JSON checker is only
> checking for the field structure, and not for things like
> changed defaults?

It only looks at the vmstate structs.

> For instance the cirrus vga video ram size
> appears to be different between qemu-kvm-1.0 and qemu-1.0,

Right, this won't get flagged.

> but this isn't something brought up in your email highlighting
> the difference between a 2.1->qemu-1.0 comparison and a
> 2.1->qemu-kvm-1.0 comparison. I know you haven't directly
> compared qemu-1.0 and qemu-1.0-kvm, but if this difference
> does exist (which I think it does) I'd expect to see it
> in the list of differences (i.e. your second email), if your
> tool looks at that too.

I did compare qemu-1.0 and qemu-kvm-1.0, but this difference won't pop
up.

The other differences that the checker spotted may not be relevant to
you, as your VMs don't have those devices enabled.

		Amit

      reply	other threads:[~2014-07-22 12:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 23:33 [Qemu-devel] Live migrate, inconsistent machine types - new machine type to fix? Alex Bligh
2014-07-19  5:51 ` Paolo Bonzini
2014-07-19  7:10   ` Alex Bligh
2014-07-19  7:30     ` Paolo Bonzini
2014-07-19  8:43       ` Alex Bligh
2014-07-19  8:54         ` Peter Maydell
2014-07-19  8:59           ` Alex Bligh
2014-07-19 10:53         ` Paolo Bonzini
2014-07-19 11:37           ` Alex Bligh
2014-07-21 10:22             ` Paolo Bonzini
2014-07-21 13:59               ` Alex Bligh
2014-07-21 14:11                 ` Paolo Bonzini
2014-07-21 14:35                   ` Alex Bligh
2014-07-21 14:14                 ` Paolo Bonzini
2014-07-22  7:11             ` Amit Shah
2014-07-22  9:50               ` Amit Shah
2014-07-22  9:55                 ` Paolo Bonzini
2014-07-22 10:22                   ` Amit Shah
2014-07-22 10:32                     ` Alex Bligh
2014-07-22 10:54                       ` Amit Shah
2014-07-22 11:38                         ` Alex Bligh
2014-07-22 11:54                           ` Amit Shah
2014-07-22 12:12                             ` Paolo Bonzini
2014-07-22 12:19                               ` Alex Bligh
2014-07-22 12:47                                 ` Amit Shah
2014-07-22 12:40                               ` Amit Shah
2014-07-22 12:15                             ` Alex Bligh
2014-07-22 12:44                               ` Amit Shah [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=20140722124450.GB32103@grmbl.mre \
    --to=amit.shah@redhat.com \
    --cc=alex@alex.org.uk \
    --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 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).