qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: [Qemu-devel] Bugs in kvm guest migration
Date: Thu, 03 Dec 2009 16:37:13 +0100	[thread overview]
Message-ID: <4B17DB29.9060801@siemens.com> (raw)

Hi,

my migration issues currently look like they are driven by at least two
bugs (that's real fun). One slipped into qemu-kvm during merge of
upstream, the other is either an issue of current kvm.git master or
kvm-kmod's wrapping of the latter.

Problem 1
---------
Setup: qemu-kvm after 249cdd049c7976614ad46eb86409d5e1e53835cc (merge
f9ea97e859dc0fce26c35f7e047a51788a3e5441 is the first usable one again,
and it's affected), any kernel module version, 64-bit host & guest (Linux).
Effect: After resume of the migration target, its timer is still ticking
(APIC IRQs arrive) but timed Linux tasks make no progress. Linux guest
uses highres/nohz, when disabling both, the problem disappears.

Problem 2
---------
Setup: qemu head with vmstate fixes. kvm-kmod master, 64-bit host & guest.
Effect: The migration target either locks up or reboots immediately.
I've nailed this down to 84d0b66c778d881eafca2a5d0d66678211c4e861. Every
kvm module build before that works, everything including and after
26ede77f536d1bb369527a96c7fe7fdc8ba2f890 shows the effect (everything in
between crashes the host for known reasons). It's still unclear if this
is an kvm-kmod wrapping issue of the user-space return notifiers. Will
check once problem #1 is understood.

Any early ideas on this are welcome while I continue digging.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

             reply	other threads:[~2009-12-03 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 15:37 Jan Kiszka [this message]
2009-12-03 19:23 ` [Qemu-devel] Re: Bugs in kvm guest migration Jan Kiszka
2009-12-04  7:59   ` Avi Kivity
2009-12-04 13:25     ` Jan Kiszka
2009-12-06 14:55       ` Jan Kiszka

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=4B17DB29.9060801@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).