[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Question about delaying dirty log stop to next vm_start
|
From: |
Yi Sun |
|
Subject: |
Question about delaying dirty log stop to next vm_start |
|
Date: |
Mon, 2 Aug 2021 15:53:49 +0800 |
|
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Hi, Jay,
We are testing some live migration cases recently. We found your below
patch delays the dirty log stop to the next vm_start.
commit 1931076077254a2886daa7c830c7838ebd1f81ef
Author: Jay Zhou <jianjay.zhou@huawei.com>
Date: Fri Jul 28 18:28:53 2017 +0800
migration: optimize the downtime
We understand this commit can optimize the downtime. But we observed
that the dirty log stop cannot be executed if user inputs "quit" in qemu
monitor after migration completes. Have you considered such case before?
Any suggestion? Thanks!
BRs,
Yi Sun
- Question about delaying dirty log stop to next vm_start,
Yi Sun <=