Thanks for the update. I have sent the v3 removing the irrelevant
information:
https://patchew.org/QEMU/20231205091903.3640-1-tian...@smartx.com/
Best,
Tianren Zhang
On Tue, Dec 5, 2023 at 4:14 PM Daniel P. Berrangé
wrote:
> On Tue, Dec 05, 2023 at 01:48:26AM -0500, tian...@smartx.com wr
From: Tianren Zhang
The stop process is not finished until bdrv_flush_all
is done. Some users (e.g., libvirt) detect the STOP
event and invokes some lock release logic to revoke
the disk lock held by current qemu when such event is
emitted. In such case, if the bdrv_flush_all is after
the stop
From: Tianren Zhang
The stop process is not finished until bdrv_flush_all
is done. Some users (e.g., libvirt) detect the STOP
event and invokes some lock release logic to revoke
the disk lock held by current qemu when such event is
emitted. In such case, if the bdrv_flush_all is after
the stop
From: Tianren Zhang
The stop process is not finished until bdrv_flush_all
is done. Some users (e.g., libvirt) detects the STOP
event and invokes some lock release logic to revoke
the disk lock held by current qemu when such event is
emitted. In such case, if the bdrv_flush_all is after
the stop
From: Tianren Zhang
The pci option rom is a RAMBlock mapped from a rom file,
but in some cases of migration, the src and dest machine
may have rom files with different size, which causes the
migration to fail due to mismatch of RAMBlock size.
In those cases, we could make the migration more
