qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	jes sorensen <jes.sorensen@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] migration: new sections and backward compatibility.
Date: Wed, 06 Jul 2011 18:04:06 +0200	[thread overview]
Message-ID: <4E148776.4000805@redhat.com> (raw)

   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.

More cases are lurking.  AHCI doesn't support migration today but 
probably will some day.  Markus mentioned that scsi-disk will face that 
issue too.  And that list probably isn't complete.

Subsections don't help here as there is no toplevel section in the first 
place.

Ideas anyone?  Maybe allow test functions like we have for subsections 
for toplevel sections too, so we have a way to skip the section 
altogether on savevm?

We probably also want a way to fail the migration in case the target 
machine doesn't support migration for $device, especially for $device == 
ahci to avoid data loss.  For the usb-tablet it isn't that problematic, 
in the best case the guest just resets the device and goes on, in the 
worst case the mouse is dead.

Comments?

cheers,
   Gerd

             reply	other threads:[~2011-07-06 16:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 16:04 Gerd Hoffmann [this message]
2011-07-06 17:13 ` [Qemu-devel] migration: new sections and backward compatibility 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
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=4E148776.4000805@redhat.com \
    --to=kraxel@redhat.com \
    --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).