[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1396052
Title:
migration f
The QEMU project is currently considering to move its bug tracking to
another system. For this we need to know which bugs are still valid
and which could be closed already. Thus we are setting older bugs to
"Incomplete" now.
If you still think this bug report here is valid, then please switch
the
Thanks for your reply.
I didn't start dest vm. The vm just in pause state and crash.
static void process_incoming_migration_co(void *opaque)
{
--
ret = qemu_loadvm_state(mis->from_src_file); -- return
when recieve "QEMU_VM_EOF"
--
mis->bh = qemu_bh_new(p
So I think the primary problem is a user error: You can't start the
destination VM while the source is still sending data. The mirror
operation must have completed or the guest will see a corrupted disk.
This means that the destination has to be started with -S, after
migration has completed the mi
** Changed in: qemu
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1396052
Title:
migration failed when running BurnInTest in guest
Status in QEMU:
Triaged
B
I think the bug is still there. And I have repaired it myself.
Migration process need wait all nbd-flying-data completion before
bdrv_invalidate_cache_all was called. The solution is working well but not
graceful,so I didn't commit to open source community.
--
You received this bug notificat
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribe
actually, I have met this issue in earlier qemu version, and it expose frankly.
The BDRVQcowState *s was memset to zero in qcow2_invalidate_cache().
So there is a dead-loop in qcow2_grow_l1_table
while (min_size > new_l1_size) {
new_l1_size = (new_l1_size * 3 + 1) / 2;
