[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 1859418] Re: disk driver with iothread setting hangs live migration

From: John Snow
Subject: [Bug 1859418] Re: disk driver with iothread setting hangs live migrations
Date: Wed, 15 Jan 2020 18:58:02 -0000

Initially I suspected that https://lists.gnu.org/archive/html/qemu-
devel/2020-01/msg03048.html may have addressed this issue, but I think
because you're not using backup it might not.

...Oh, qemu 2.12 is *quite old* and not supported upstream anymore. Do
you have the ability to test on a more modern QEMU version?

If not, I might need to redirect you back to the RH Bugzilla for issues
with the stable version they ship for RH/CentOS. I don't want to play
bug tracker pingpong with you, so I'll leave this issue open (but marked
"incomplete") and wait for a reply.


** Changed in: qemu
       Status: New => Incomplete

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  disk driver with iothread setting hangs live migrations

Status in QEMU:

Bug description:
  Per report raised at

  Description of problem:

  A disk driver definition using iothread parameter causes live
  migration with copy storage to hang during or just before the final
  ram sync stage.

  Interestingly, having the scsi controller as a separate iothread does
  not trigger the issue.

  Version-Release number of selected component (if applicable):

  I can reproduce this on centos7 with qemu-ev and with centos 8:


  Steps to Reproduce:
  1. Create a definition with 1 iothread on the disk image:

        <driver name='qemu' type='qcow2' iothread='1' />

  2. Issue a live migrate request like: virsh migrate --live --copy-storage-all 
vm qemu+tcp://remote/system
  3. Live migrate on source copies storage and then hangs at 80-99%, I guess 
during the ram copy phase.

  Keeping exactly the same config but without the iothread on the disk
  driver has successful migrations every time.

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]