From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Alexander Graf <agraf@suse.de>,
Juan Quintela <quintela@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] migration: new sections and backward compatibility.
Date: Fri, 08 Jul 2011 15:02:24 +0200 [thread overview]
Message-ID: <4E16FFE0.7050709@redhat.com> (raw)
In-Reply-To: <4E15608D.5000201@redhat.com>
On 07/07/11 09:30, Avi Kivity wrote:
> On 07/07/2011 10:14 AM, Gerd Hoffmann wrote:
>>> Can't we just implicitly fail migration whenever there's a device in
>>> the tree that doesn't have VMSTATE?
>>
>>
>> There are cases where the device doesn't need to save state, so that
>> alone doesn't cut it.
>
> It should then say so by having an empty VMSTATE descriptor.
It seems reasonable to me to introduce a situation where devices have to
explicitly marked as migration compatible and fail if there are devices
in the system which are not.
Even for the case like USB devices where migration might simply force a
replug of the devices.
Cheers,
Jes
next prev parent reply other threads:[~2011-07-08 13:04 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
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 [this message]
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=4E16FFE0.7050709@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=kraxel@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).