From: Jan Kiszka <jan.kiszka@web.de>
To: thomas@fjellstrom.ca
Cc: KVM <kvm@vger.kernel.org>
Subject: Re: one out of four existing kvm guest's not starting after system upgrade
Date: Sat, 18 Feb 2012 09:39:12 +0100 [thread overview]
Message-ID: <4F3F63B0.4060305@web.de> (raw)
In-Reply-To: <201202172149.36904.thomas@fjellstrom.ca>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
On 2012-02-18 05:49, Thomas Fjellstrom wrote:
> I just updated my kvm host, kernel upgraded from 2.6.38 up to 3.2, and
> qemu+qemu-kvm updated (not sure from what to what). But after the upgrade, one
> of my guests will not start up. It gets stuck with 60-80% cpu use, almost no
> memory is allocated by qemu/kvm, and no output of any kind is seen (in the
> host console, or a bunch of the guest output options like curses display,
> stdio output, virsh console, vnc or sdl output). I normally use libvirt to
> manage the guests, but I've attempted to run qemu manually, and have the same
> problems.
>
> What can cause this?
>
> Just tested booting back into the old kernel, the one guest still won't start,
> while the rest do. I'm thoroughly confused.
You mean if you only update qemu-kvm, the problem persists, just with
lower probability? In that case, we definitely need the version of your
current qemu-kvm installation. Also, it would be nice to attach gdb to
the stuck qemu-kvm process, issuing a "thread apply all backtrace" in
that state.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-02-18 8:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-18 4:49 one out of four existing kvm guest's not starting after system upgrade Thomas Fjellstrom
2012-02-18 8:39 ` Jan Kiszka [this message]
2012-02-18 8:50 ` Thomas Fjellstrom
2012-02-18 8:53 ` Thomas Fjellstrom
2012-02-18 8:56 ` Jan Kiszka
2012-02-18 9:00 ` Thomas Fjellstrom
2012-02-18 9:57 ` Thomas Fjellstrom
2012-02-19 20:13 ` Thomas Fjellstrom
2012-02-22 17:58 ` Jan Kiszka
2012-02-28 9:13 ` Jan Kiszka
2012-02-28 17:32 ` Thomas Fjellstrom
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=4F3F63B0.4060305@web.de \
--to=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=thomas@fjellstrom.ca \
/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.