All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: xen-devel@lists.xen.org
Cc: wei.liu2@citrix.com
Subject: What runtime states to be preserved across save / restore?
Date: Mon, 28 Apr 2014 14:10:41 +0100	[thread overview]
Message-ID: <20140428131041.GA28126@zion.uk.xensource.com> (raw)

Hi all

I'm trying to determine what runtime states to be preserved across
save / restore.

Things that are randomly generated if not set, definitely want to
preserve:
1. guest uuid
2. mac address
3. vtpm uuid

Things might change when guest is running, and seem to be worthy of
preserving:
1. max memory size
2. target memory size
3. CDROM state

As for other things, I think using the stored configurations and let the
remote end make its own decision is sufficient.

Thoughts?

Wei.

             reply	other threads:[~2014-04-28 13:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 13:10 Wei Liu [this message]
2014-04-28 13:42 ` What runtime states to be preserved across save / restore? Ian Campbell
2014-04-28 13:57   ` Wei Liu
2014-04-28 14:16     ` Ian Campbell
2014-04-28 14:39       ` Wei Liu
2014-04-29  7:29       ` Daniel Kiper
2014-04-29  9:05         ` Wei Liu
2014-04-29 10:40           ` Daniel Kiper
2014-04-29 10:42             ` Wei Liu
2014-05-06  9:32               ` George Dunlap
2014-05-06  9:44                 ` Wei Liu

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=20140428131041.GA28126@zion.uk.xensource.com \
    --to=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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.