qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Li Zhijian <lizhijian@cn.fujitsu.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: quintela@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] migration: send and check the devices between source and distination at the begining
Date: Fri, 30 Sep 2016 15:53:44 +0800	[thread overview]
Message-ID: <6327b0c2-6017-f80c-ed48-db7e9917ad25@cn.fujitsu.com> (raw)
In-Reply-To: <20160930061516.GC1429@amit-lp.rh>



On 09/30/2016 02:15 PM, Amit Shah wrote:
> Hi,
>
> On (Thu) 29 Sep 2016 [19:06:32], Li Zhijian wrote:
>> Priviously, if the source and distination have different devices, source could goto
>> the status "paused (postmigrate)", and the distination will exit that means no qemu
>> is alive.
>>
>> After this patch, at above case, source can dectect the some error early from distination
>> and stop the migration, source keep in status "running".
>
> How would incoming migrations from previous versions work?

You are right. we need to consider more.

How about that:
we need to introduce a new section type(e.g: QEMU_VM_SECTION_DEVICE_LIST).

source side:
- at the beginning of qemu_savevm_state_begin(), send QEMU_VM_SECTION_DEVICE_LIST first
- original path

dst side:
- if we got the QEMU_VM_SECTION_DEVICE_LIST, have a check with the devices(name,version)
- otherwise original path

Please correct me.

Thanks
Zhijian

>
>
> 		Amit
>
>
>

  reply	other threads:[~2016-09-30  7:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 11:06 [Qemu-devel] [PATCH 1/2] migration: split qemu_loadvm_section_start_full() to qemu_loadvm_section_{start(), full()} Li Zhijian
2016-09-29 11:06 ` [Qemu-devel] [PATCH 2/2] migration: send and check the devices between source and distination at the begining Li Zhijian
2016-09-30  6:15   ` Amit Shah
2016-09-30  7:53     ` Li Zhijian [this message]
2016-09-30  9:58       ` Dr. David Alan Gilbert
2016-10-06  2:51         ` Li Zhijian
2016-10-06 12:17           ` Dr. David Alan Gilbert

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=6327b0c2-6017-f80c-ed48-db7e9917ad25@cn.fujitsu.com \
    --to=lizhijian@cn.fujitsu.com \
    --cc=amit.shah@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).