[Qemu-devel] [Bug 1723161] Re: Migration failing in qemu-2.10.1 but working qemu-2.9.1 and earlier with same options

[Dr. David Alan Gilbert]

i added some debug, and I'm seeing:

blk_pwrite failed for pflash1 0 @ 0 cluster_size=1048576 ret=-5

so that's an EIO.

The EIO is coming from blk_check_byte_request  because it's trying to
write a 1MB cluster size chunk, yet the var file is only ~128k

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1723161

Title:
  Migration failing in qemu-2.10.1 but working qemu-2.9.1 and earlier
  with same options

Status in QEMU:
  New

Bug description:
  
  Qemu-2.10.1 migration failing with the following error:
  Receiving block device images
  qemu-system-x86_64: error while loading section id 2(block)
  qemu-system-x86_64: load of migration failed: Input/output error

  Migration is setup on the destination system of the migration using:
  -incoming tcp:0:4444

  Migration is initiated from the source using the following commands in its 
qemu monitor:
  migrate -b "tcp:localhost:4444"

  The command-line used in both the source and destination is:
  qemu-system-x86_64 \
          -nodefaults \
          -pidfile vm0.pid \
          -enable-kvm \
          -machine q35 \
          -cpu host -smp 2 \
          -m 4096M \
          -drive if=pflash,format=raw,unit=0,file=OVMF_CODE.fd,readonly \
          -drive if=pflash,format=raw,unit=1,file=OVMF_VARS.fd \
          -drive file=${HDRIVE},format=qcow2 \
          -drive media=cdrom \
          -usb -device usb-tablet \
          -vga std -vnc :0 \
          -net nic,macaddr=${TAPMACADDR} -net 
user,net=192.168.2.0/24,dhcpstart=192.168.2.10 \
          -serial stdio \
          -monitor unix:${MONITORSOCKET},server,nowait

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1723161/+subscriptions