qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	Chao Peng <chao.p.peng@linux.intel.com>,
	"Tian, Kevin" <kevin.tian@intel.com>, Fam Zheng <famz@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] change x86 default machine type to Q35?
Date: Thu, 6 Jul 2017 12:13:06 +0100	[thread overview]
Message-ID: <20170706111305.GA3174@work-vm> (raw)
In-Reply-To: <20170706110627.GK3988@redhat.com>

* Daniel P. Berrange (berrange@redhat.com) wrote:
> On Thu, Jul 06, 2017 at 01:00:53PM +0200, Thomas Huth wrote:
> > On 06.07.2017 12:49, Daniel P. Berrange wrote:
> > [...]
> > > This avoids the user having problems with guest ABI silently changing
> > > behind their back, or migration suddenly failing to load vm state,
> > 
> > For proper migration, you've got to specify the right versioned machine
> > type anyway, so that should not be an issue here.
> 
> That's only true if you have mis-matched QEMU releases on each host.
> If you know you have the same QEMU release everywhere, there's no
> need for versioned machine types. Though obviously we'd still recommend
> people us versioned machine type, its not unreasonable that some people
> will not

We have got protection against machine type screwups; e.g going from -M
pc to -M q35 we get:

qemu-system-x86_64: Machine type received is 'pc-i440fx-2.9' and local is 'pc-q35-2.9'

Dave

> Regards,
> Daniel
> -- 
> |: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org         -o-            https://fstop138.berrange.com :|
> |: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  parent reply	other threads:[~2017-07-06 11:13 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05  6:57 [Qemu-devel] change x86 default machine type to Q35? Chao Peng
2017-07-05  8:14 ` Thomas Huth
2017-07-05  9:32   ` Marcel Apfelbaum
2017-07-07 13:39     ` Eduardo Habkost
2017-07-07 15:17       ` Michael S. Tsirkin
2017-07-07 18:03         ` Eduardo Habkost
2017-07-10  7:42           ` Marcel Apfelbaum
2017-07-10  9:45             ` Paolo Bonzini
2017-07-10 13:59             ` Eduardo Habkost
2017-07-10 16:45               ` Michael S. Tsirkin
2017-07-10 17:47                 ` Eduardo Habkost
2017-07-11  7:48                   ` Thomas Huth
2017-07-11  8:01                     ` Marcel Apfelbaum
2017-07-11  8:13                     ` Gerd Hoffmann
2017-07-11 14:42                       ` Kevin Wolf
2017-07-11 14:47                         ` Paolo Bonzini
2017-07-12  6:39                           ` Marcel Apfelbaum
2017-07-12 15:17                             ` Eduardo Habkost
2017-07-12  5:51                         ` Gerd Hoffmann
2017-07-12  6:18                           ` Marcel Apfelbaum
2017-07-12  8:28                           ` Kevin Wolf
2017-07-11 14:47                       ` Eduardo Habkost
2017-07-05 11:07   ` Daniel P. Berrange
2017-07-05 11:13     ` Thomas Huth
2017-07-06 10:30     ` Stefan Hajnoczi
2017-07-06 10:41       ` Daniel P. Berrange
2017-07-11 10:13         ` Stefan Hajnoczi
2017-07-05 10:49 ` Laszlo Ersek
2017-07-05 11:04 ` Daniel P. Berrange
2017-07-05 11:44   ` Fam Zheng
2017-07-05 11:58     ` Thomas Huth
2017-07-05 12:22       ` Fam Zheng
2017-07-06 10:49         ` Daniel P. Berrange
2017-07-06 10:57           ` Peter Maydell
2017-07-06 11:00           ` Thomas Huth
2017-07-06 11:06             ` Daniel P. Berrange
2017-07-06 11:12               ` Thomas Huth
2017-07-06 11:13               ` Dr. David Alan Gilbert [this message]
2017-07-07 13:49           ` Eduardo Habkost
2017-07-05 12:43       ` Paolo Bonzini

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=20170706111305.GA3174@work-vm \
    --to=dgilbert@redhat.com \
    --cc=berrange@redhat.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=famz@redhat.com \
    --cc=kevin.tian@intel.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).