All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Amit Shah <amit.shah@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] KVM call minutes for Feb 15
Date: Wed, 16 Feb 2011 08:41:27 -0600	[thread overview]
Message-ID: <4D5BE217.2020306@codemonkey.ws> (raw)
In-Reply-To: <20110216143934.GB5770@amit-x200.redhat.com>

On 02/16/2011 08:39 AM, Amit Shah wrote:
> On (Tue) 15 Feb 2011 [17:13:13], Anthony Liguori wrote:
>    
>> On 02/15/2011 10:26 AM, Chris Wright wrote:
>>      
>>> revisit new ->   old migration
>>> - Amit offers virtio-serial patches and some legwork
>>>        
>> So, to me, migration correctness trumps compatibility.  I don't
>> think compatibility is useful if it means that a guest may fail
>> during migration.  We have subsections as a way to support the cases
>> where it's safe to migrate to an old version only if a feature is
>> not being used or a corner case is not currently happening.  This is
>> the best way to approach the problem.
>>
>> If a subsection won't work, that means you want to migrate when
>> you're completely sure that migrating will break a guest.  That
>> doesn't seem reasonable at all to me.
>>
>> I think in the last discussion on Amit's patches, I had suggested
>> that subsections could be used to allow migration when there wasn't
>> any queued data.  I think this is the best we can do while
>> preserving correctness.
>>      
> The only problem is that virtio hasn't been converted over to vmstate,
> which is necessary for subsections.
>    

Then it needs to be converted.

Regards,

Anthony Liguori

> 		Amit
>
>    


  reply	other threads:[~2011-02-16 14:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 16:26 KVM call minutes for Feb 15 Chris Wright
2011-02-15 16:26 ` [Qemu-devel] " Chris Wright
2011-02-15 23:13 ` Anthony Liguori
2011-02-15 23:13   ` Anthony Liguori
2011-02-16 10:24   ` Avi Kivity
2011-02-16 10:24     ` Avi Kivity
2011-02-16 13:34     ` Anthony Liguori
2011-02-17  9:26       ` Avi Kivity
2011-02-17 12:12         ` Anthony Liguori
2011-02-17 12:23           ` Avi Kivity
2011-02-17 13:10             ` Anthony Liguori
2011-02-17 13:25               ` Avi Kivity
2011-02-17 13:37                 ` Anthony Liguori
2011-02-17 13:59                   ` Peter Maydell
2011-02-17 13:59                     ` Peter Maydell
2011-02-17 14:01                     ` Anthony Liguori
2011-02-17 14:06                   ` Avi Kivity
2011-02-17 13:37                 ` Anthony Liguori
2011-02-16 14:39   ` Amit Shah
2011-02-16 14:41     ` Anthony Liguori [this message]
2011-02-17 12:42       ` Amit Shah

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=4D5BE217.2020306@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=amit.shah@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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.