qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Snapshots not bound to an architecture?
Date: Thu, 2 Oct 2008 22:07:49 +0300	[thread overview]
Message-ID: <f43fc5580810021207j14e11dd1wd7527c421d7d566c@mail.gmail.com> (raw)

Hi,

While testing the savevm/loadvm functions, I noticed that it's
possible to attempt to load a snapshot made for entirely different
architecture. There are a lot of warnings, of course.

Could we prevent this somehow? Or is there a use case for this, for
example loading a snapshot made on i386 to an x86_64 emulator?

             reply	other threads:[~2008-10-02 19:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 19:07 Blue Swirl [this message]
2008-10-07 20:22 ` [Qemu-devel] Snapshots not bound to an architecture? Anthony Liguori
2008-10-07 20:30   ` Paul Brook
2008-10-07 20:39     ` Anthony Liguori
2008-10-08 19:06       ` Blue Swirl

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=f43fc5580810021207j14e11dd1wd7527c421d7d566c@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.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 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).