All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, qemu-stable@nongnu.org
Subject: [Qemu-devel] Broken live Migration in Qemu 2.5.1.1?
Date: Mon, 6 Jun 2016 15:32:43 +0200	[thread overview]
Message-ID: <57557B7B.2070301@kamp.de> (raw)

Hi,

during internal testing of Qemu 2.5.1.1 I found a vServer running Ubuntu 12.04 (kernel 3.13) and a slave SQL server to
stop replicating from the master. This seems to be reproducible. It is possible to continue replication when issuing a slave stop / slave start.
There is no error visible on the vServer.

Has anyone a fix in mind that could be related to such an issue?

Host kernel in Linux 4.4, Guest kernel 3.13. Guest driver is virtio-blk via iSCSI. Emulated vCPU is Westmere.

I already have this patch here applied:

target-i386: do not read/write MSR_TSC_AUX from KVM if CPUID bit is not set

Without this migration for Westmere and earlier CPUs is completely broken.

I also found the following commits in git which are not applied (yet):

migration (ordinary): move bdrv_invalidate_cache_all of of coroutine context
migration: fix incorrect memory_global_dirty_log_start outside BQL

I will try with these and also with current master.

Thanks,
Peter

             reply	other threads:[~2016-06-06 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 13:32 Peter Lieven [this message]
2016-06-06 15:51 ` [Qemu-devel] Broken live Migration in Qemu 2.5.1.1? Peter Lieven
2016-06-06 16:13   ` [Qemu-devel] [Qemu-stable] " Stefan Priebe - Profihost AG
2016-06-07  7:11     ` Peter Lieven
2016-06-07  7:38     ` Peter Lieven
2016-06-07  8:33       ` Stefan Priebe - Profihost AG

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=57557B7B.2070301@kamp.de \
    --to=pl@kamp.de \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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.