From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: jes sorensen <jes.sorensen@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] migration: new sections and backward compatibility.
Date: Thu, 07 Jul 2011 09:19:06 +0200 [thread overview]
Message-ID: <4E155DEA.5020703@redhat.com> (raw)
In-Reply-To: <4E1497C6.4060505@codemonkey.ws>
On 07/06/11 19:13, Anthony Liguori wrote:
> On 07/06/2011 11:04 AM, Gerd Hoffmann wrote:
>> Hi folks,
>>
>> We'll need to figure a sane way to handle migration to older versions
>> with new sections, i.e. devices which used to not save state before do
>> now.
>>
>> We already have one case in tree: usb. qemu 0.14 saves state for usb-hid
>> devices and the usb-hub, whereas qemu 0.13 and older don't. You can't
>> migrate a vm with a usb-tablet from 0.14 to 0.13 because of that even if
>> you use -M pc-0.13.
>
> Because if you did migrate, you would actively break the guest during
> migration. So why is this a problem?
Well, in case of usb hid devices breaking the guest isn't that a big
issue for at least some guests because they manage to reset the device
and continue nevertheless ...
I think this is a case-by-case thing. In some cases we want break
migration because critical state is missing. In other cases we might
want allow it nevertheless.
cheers,
Gerd
next prev parent reply other threads:[~2011-07-07 7:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 16:04 [Qemu-devel] migration: new sections and backward compatibility Gerd Hoffmann
2011-07-06 17:13 ` Anthony Liguori
2011-07-07 7:19 ` Gerd Hoffmann [this message]
2011-07-07 15:36 ` Anthony Liguori
2011-07-12 14:50 ` Gerd Hoffmann
2011-07-07 9:23 ` Markus Armbruster
2011-07-07 11:02 ` Alexander Graf
2011-07-07 15:23 ` Paolo Bonzini
2011-07-11 15:32 ` Kevin Wolf
2011-07-11 15:31 ` Paolo Bonzini
2011-07-07 14:40 ` Gerd Hoffmann
2011-07-07 15:37 ` Anthony Liguori
2011-07-07 16:44 ` Markus Armbruster
2011-07-06 17:28 ` Avi Kivity
2011-07-06 20:01 ` Anthony Liguori
2011-07-06 23:32 ` Alexander Graf
2011-07-07 7:14 ` Gerd Hoffmann
2011-07-07 7:30 ` Avi Kivity
2011-07-08 13:02 ` Jes Sorensen
2011-07-08 14:43 ` Peter Maydell
2011-07-08 15:12 ` Gerd Hoffmann
2011-07-07 15:33 ` Anthony Liguori
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=4E155DEA.5020703@redhat.com \
--to=kraxel@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=jes.sorensen@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).