From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: William Dauchy <william@gandi.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] migration from qemu2.1.2 to qemu2.2
Date: Thu, 11 Dec 2014 14:34:56 +0000 [thread overview]
Message-ID: <20141211143455.GG2567@work-vm> (raw)
In-Reply-To: <20141211143229.GX14440@gandi.net>
* William Dauchy (william@gandi.net) wrote:
> On Dec11 14:05, Dr. David Alan Gilbert wrote:
> > Hmm, it might even do it on the same hardware between different qemus;
>
> I dont get your last statement;
> my common use case is to live migrate an old userland to a new one
> (so 2.1 to 2.2 here); so if I guarantee same HW, it should work, right?
I wouldn't trust -host cpu to be the same on the same HW between
different QEMUs, especially on newer hardware than your older QEMU new
about.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2014-12-11 14:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 18:37 [Qemu-devel] migration from qemu2.1.2 to qemu2.0 William Dauchy
2014-12-09 18:43 ` William Dauchy
2014-12-09 18:55 ` [Qemu-devel] migration from qemu2.1.2 to qemu2.2 Dr. David Alan Gilbert
2014-12-09 23:25 ` William Dauchy
2014-12-10 8:58 ` Dr. David Alan Gilbert
2014-12-10 17:04 ` William Dauchy
2014-12-10 17:10 ` Dr. David Alan Gilbert
2014-12-10 17:20 ` William Dauchy
2014-12-10 17:28 ` William Dauchy
2014-12-10 17:40 ` Dr. David Alan Gilbert
2014-12-10 17:43 ` Paolo Bonzini
2014-12-10 17:31 ` Dr. David Alan Gilbert
2014-12-10 18:02 ` William Dauchy
2014-12-10 18:21 ` Dr. David Alan Gilbert
2014-12-11 13:44 ` William Dauchy
2014-12-11 14:05 ` Dr. David Alan Gilbert
2014-12-11 14:32 ` William Dauchy
2014-12-11 14:34 ` Dr. David Alan Gilbert [this message]
2014-12-11 14:41 ` William Dauchy
2014-12-11 14:44 ` Dr. David Alan Gilbert
2014-12-11 14:06 ` 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=20141211143455.GG2567@work-vm \
--to=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=william@gandi.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.