From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Snapshots not bound to an architecture?
Date: Tue, 07 Oct 2008 15:22:44 -0500 [thread overview]
Message-ID: <48EBC514.7010209@codemonkey.ws> (raw)
In-Reply-To: <f43fc5580810021207j14e11dd1wd7527c421d7d566c@mail.gmail.com>
Blue Swirl wrote:
> 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?
>
I think we should introduce a machine section for save/restore that
included that information. It should also be versioned in such a way
that it could be incremented whenever a new piece of hardware is added
to the default machine type.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-10-07 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 19:07 [Qemu-devel] Snapshots not bound to an architecture? Blue Swirl
2008-10-07 20:22 ` Anthony Liguori [this message]
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=48EBC514.7010209@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).