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

[William Tambe]

Hi Fam,

We used the same host for both src and dest for testing purposes;
ideally it should work regardless of whether src and dst are the same
host.

When we tested it, src and dest were NOT using the same vars file and
rom file; they each had their own copy.

Please, can you keep us updated when a fix is pushed upstream ?

On Fri, Oct 13, 2017 at 5:18 AM, Fam Zheng <address@hidden> wrote:
> Hi William,
>
> Just to confirm: are both src and dest on the same host, using the same
> command line options? Then I'm confused why you need block migration
> because they share the same image files (for OVMF pflash and ${HDRIVE}).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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

-- 
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