qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Snapshots not bound to an architecture?
Date: Tue, 07 Oct 2008 15:39:17 -0500	[thread overview]
Message-ID: <48EBC8F5.4070808@codemonkey.ws> (raw)
In-Reply-To: <200810072130.07903.paul@codesourcery.com>

Paul Brook wrote:
> On Tuesday 07 October 2008, Anthony Liguori wrote:
>   
>> 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.
>>     
>
> Using a single version number to determine the "base" machine is IMHO a bad 
> idea.

I should have said, that I expected this to be an intermediate step.

>  The base peripherals should be identified (and mismatches detected) 
> that same way as any other peripherals.
>   

Yes.  This is particularly important in the context of hot plug because 
the bus/dev/fn of the plugged device may be different than if the device 
were just added directly.

> The simplest way to avoid loading the wrong type of machine is to give the 
> cpus different names (e.g. cpu_i386/cpu_amd64) instead of just calling 
> them "cpu".
>   

Yes, that works too, but it breaks backwards compatibility in a way 
that's hard to reconcile.  Bumping the version of "cpu" and including a 
machine type identifier would also work and would be easier to do in a 
backwards compatible way.

Regards,

Anthony Liguori

> Paul
>   

  reply	other threads:[~2008-10-07 20:39 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
2008-10-07 20:30   ` Paul Brook
2008-10-07 20:39     ` Anthony Liguori [this message]
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=48EBC8F5.4070808@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=paul@codesourcery.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).