All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Tambe <1723161@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1723161] [NEW] Migration failing in qemu-2.10.1 but working qemu-2.9.1 and earlier with same options
Date: Thu, 12 Oct 2017 15:33:17 -0000	[thread overview]
Message-ID: <150782239801.1729.1327212510076491094.malonedeb@chaenomeles.canonical.com> (raw)

Public bug reported:


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

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

             reply	other threads:[~2017-10-12 15:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 15:33 William Tambe [this message]
2017-10-12 19:24 ` [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
2017-10-12 20:53   ` William Tambe
2017-10-13  9:05 ` Dr. David Alan Gilbert
2017-10-13 10:18 ` Fam Zheng
2017-10-13 20:10   ` William Tambe
2017-10-13 10:41 ` Dr. David Alan Gilbert
2017-10-13 11:09 ` Dr. David Alan Gilbert
2017-12-12 18:39 ` Dr. David Alan Gilbert
2020-10-07 18:40 ` Thomas Huth
2020-12-07  4:17 ` Launchpad Bug Tracker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=150782239801.1729.1327212510076491094.malonedeb@chaenomeles.canonical.com \
    --to=1723161@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.