[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/1817268
Title:
I guess the bug still exists, I fixed it back in the time by repackaging
OVMF_VARS.fd (padded to be 1M).
I will try to find some time to mount an environment to reproduce the
issue again.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
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
Yes, I think so; although old-style block migration doesn't get much
work on it now; so probably the fix I'd recommend for most cases now
would be to pad the var file.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Thanks you, so it is a bug and not the expected behavior right ?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1817268
Title:
Input/output error during migration
Status in QEMU:
New
Bug
Yep that Length mismatch is expected - the source and destination do
have to match.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1817268
Title:
Input/output error during migration
Status in
Hi David,
Thanks you for your help.
The VARS file is 128K.
I increased the "/var/lib/libvirt/qemu/nvram/testuefi_VARS.fd" var file
to 1M, but had this error during migration:
error: internal error: qemu unexpectedly closed the monitor:
2019-02-22T09:52:34.098833Z qemu-system-x86_64: Length
Hi Mathieu,
How big is your testuefi-VM_VARS.fd file ? Does the problem go away if you
pad it to 1MB?
I've seen a problem migrating pflash where the files aren't 1MB (?)
multiples but only using the 'old style' block migration; normally you
get an NBD based block migration but when you
