From: Philipp Hahn <hahn@univention.de>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: KVM list <kvm@vger.kernel.org>, nikola.ciprich@linuxbox.cz
Subject: Re: qemu-kvm-0.13.0, 2.6.37.1 - after migration, some of guests got stuck
Date: Mon, 21 Feb 2011 08:43:54 +0100 [thread overview]
Message-ID: <201102210843.58844.hahn@univention.de> (raw)
In-Reply-To: <20110220193235.GA3651@nik-comp.lan>
[-- Attachment #1: Type: text/plain, Size: 1929 bytes --]
Hello,
I'm no KVM core developer, so please take my advise with a grain of caution.
Am Sonntag 20 Februar 2011 20:32:35 schrieb Nikola Ciprich:
> I've just migrated a bunch of guests from one node to another
> due to upgrading host kernel from 2.6.37 to 2.6.37.1.
> After that, some of guests started consuming 100% of CPU time and their os
> seems to be stuck.
>
> Looks like all the stuck guest were running 2.6.32 with kvm paravirt
> enabled. others running same as well as different kernels seem to be ok,
> including windows guests.
I also sometimes experience problems with migrated (in my case: suspended)
VMs, see <http://marc.info/?l=kvm&m=129484437222822&w=2>: They were either
stuck in an interrupt storm or did not receive any interrupts any more (looks
like some interrupts relates state gets not saved/restored properly).
For me the following did help:
1. Suspend VM to disk
2. Restart VM with the -no-kvm-irqchip Option
Perhaps you could test that as well. (An alternative would be to use qemus
internal debugger or gdb to remote debug the VM and detect what your VMs are
doing, especially "x/20i $rip" to dump the next 20 assembler instructions)
Please be advised, that -no-kvm-irqchip opens a new can of worms and should
only be used to diagnose the problem. You probably should also backup the
save file and use the -snapshot option to be able to repeatly test different
strategies.
Sincerely
Philipp
--
Philipp Hahn Open Source Software Engineer hahn@univention.de
Univention GmbH Linux for Your Business fon: +49 421 22 232- 0
Mary-Somerville-Str.1 28359 Bremen fax: +49 421 22 232-99
http://www.univention.de/
** Besuchen Sie uns auf der CeBIT in Hannover **
** Auf dem Univention Stand D36 in Halle 2 **
** Vom 01. bis 05. März 2011 **
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2011-02-21 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 19:32 qemu-kvm-0.13.0, 2.6.37.1 - after migration, some of guests got stuck Nikola Ciprich
2011-02-21 7:43 ` Philipp Hahn [this message]
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=201102210843.58844.hahn@univention.de \
--to=hahn@univention.de \
--cc=extmaillist@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
/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