If you try migration on ARMv7 you will run into this issue.
If anyone is aware if new patches to handle this
please share.
- Mario
-------- Original Message --------
Subject: [Qemu-devel] [Bug 1294227] [NEW] migration wrong handling of
KVM_GET_DIRTY_LOG ioctl
Date: Tue, 18 Mar 2014 17:24:03 +0000
From: Mario Smarduch <m.smarduch@xxxxxxxxxxx>
Reply-To: Bug 1294227 <1294227@xxxxxxxxxxxxxxxxxx>
To: <qemu-devel@xxxxxxxxxx>
Public bug reported:
In the code below kvm_vm_ioctl(...) can return --errno != -1 from ioctl
call, but return only checks for -1.
Found during KVM-ARM migration which apperead to go through but was
actually failing getting
memslot dirty bitmap.
static int kvm_physical_sync_dirty_bitmap(....)
{
....
if(kvm_vm_ioctl(s, KVM_GET_DIRTY_LOG, &d) == -1) {
- err out
}
... continue
}
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1294227
Title:
migration wrong handling of KVM_GET_DIRTY_LOG ioctl
Status in QEMU:
New
Bug description:
In the code below kvm_vm_ioctl(...) can return --errno != -1 from
ioctl call, but return only checks for -1.
Found during KVM-ARM migration which apperead to go through but was
actually failing getting
memslot dirty bitmap.
static int kvm_physical_sync_dirty_bitmap(....)
{
....
if(kvm_vm_ioctl(s, KVM_GET_DIRTY_LOG, &d) == -1) {
- err out
}
... continue
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1294227/+subscriptions
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
