All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Dor Laor <dlaor@redhat.com>
Cc: Andre Przywara <andre.przywara@amd.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] CPUID feature bits not saved with migration
Date: Thu, 16 Jul 2009 15:29:58 +0100	[thread overview]
Message-ID: <20090716142958.GB16461@shareable.org> (raw)
In-Reply-To: <4A5ECEE9.8070708@redhat.com>

Dor Laor wrote:
> On 07/15/2009 06:12 PM, Jamie Lokier wrote:
> >Anthony Liguori wrote:
> >>It's unclear what to do about -cpu host.  If we did migrate cpuid
> >>values, then -cpu would effectively be ignored after an incoming 
> >>migration.
> 
> Actually, it might be better to build all of the guest configurations 
> (devices, cpu, etc) from the migration stream, without stating them in 
> the destination command line.
> 
> The destination command line should only contain host configuration.
> It will bypass any type of conflict between the src/dst pairs.

I agree, but this will be a lot simpler and more satisfying once
there's a machine configuration file which can be dumped from qemu and
reloaded into it, with host configuration from the command line merged
into the configuration file at load time.

-- Jamie

  parent reply	other threads:[~2009-07-16 14:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 12:50 [Qemu-devel] CPUID feature bits not saved with migration Andre Przywara
2009-07-15 14:38 ` Anthony Liguori
2009-07-15 15:12   ` Jamie Lokier
2009-07-16  6:55     ` Dor Laor
2009-07-16 10:09       ` Andre Przywara
2009-07-16 14:29       ` Jamie Lokier [this message]
2009-07-16 10:08     ` Andre Przywara
2009-07-16 14:28       ` Jamie Lokier
2009-07-22 13:24         ` Andre Przywara
2009-07-22 14:46           ` Jamie Lokier
2009-07-16 10:08   ` Andre Przywara

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=20090716142958.GB16461@shareable.org \
    --to=jamie@shareable.org \
    --cc=andre.przywara@amd.com \
    --cc=dlaor@redhat.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 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.