From: Jan Kiszka <jan.kiszka@siemens.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Bugs in kvm guest migration
Date: Thu, 03 Dec 2009 20:23:31 +0100 [thread overview]
Message-ID: <4B181033.1020804@siemens.com> (raw)
In-Reply-To: <4B17DB29.9060801@siemens.com>
Jan Kiszka wrote:
> 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.
It is kernel-related, using kvm.git as host kernel makes no difference.
This may now mean that kvm is buggy or that it triggers some msr
save/restore related issues in qemu. Digging even deeper...
Jan
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Bugs in kvm guest migration
Date: Thu, 03 Dec 2009 20:23:31 +0100 [thread overview]
Message-ID: <4B181033.1020804@siemens.com> (raw)
In-Reply-To: <4B17DB29.9060801@siemens.com>
Jan Kiszka wrote:
> 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.
It is kernel-related, using kvm.git as host kernel makes no difference.
This may now mean that kvm is buggy or that it triggers some msr
save/restore related issues in qemu. Digging even deeper...
Jan
next prev parent reply other threads:[~2009-12-03 19:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 15:37 Bugs in kvm guest migration Jan Kiszka
2009-12-03 15:37 ` [Qemu-devel] " Jan Kiszka
2009-12-03 19:23 ` Jan Kiszka [this message]
2009-12-03 19:23 ` [Qemu-devel] " Jan Kiszka
2009-12-04 7:59 ` Avi Kivity
2009-12-04 7:59 ` [Qemu-devel] " Avi Kivity
2009-12-04 13:25 ` Jan Kiszka
2009-12-04 13:25 ` [Qemu-devel] " Jan Kiszka
2009-12-06 14:55 ` Jan Kiszka
2009-12-06 14:55 ` [Qemu-devel] " 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=4B181033.1020804@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 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.