From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: one out of four existing kvm guest's not starting after system upgrade Date: Sat, 18 Feb 2012 09:39:12 +0100 Message-ID: <4F3F63B0.4060305@web.de> References: <201202172149.36904.thomas@fjellstrom.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1E3EC52E5D34E2A45710BEF5" Cc: KVM To: thomas@fjellstrom.ca Return-path: Received: from fmmailgate03.web.de ([217.72.192.234]:33761 "EHLO fmmailgate03.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751493Ab2BRIj1 (ORCPT ); Sat, 18 Feb 2012 03:39:27 -0500 Received: from moweb002.kundenserver.de (moweb002.kundenserver.de [172.19.20.108]) by fmmailgate03.web.de (Postfix) with ESMTP id 0AFAA1B2AE1EC for ; Sat, 18 Feb 2012 09:39:26 +0100 (CET) In-Reply-To: <201202172149.36904.thomas@fjellstrom.ca> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1E3EC52E5D34E2A45710BEF5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 upgra= de, one=20 > of my guests will not start up. It gets stuck with 60-80% cpu use, almo= st no=20 > memory is allocated by qemu/kvm, and no output of any kind is seen (in = the=20 > host console, or a bunch of the guest output options like curses displa= y,=20 > stdio output, virsh console, vnc or sdl output). I normally use libvirt= to=20 > manage the guests, but I've attempted to run qemu manually, and have th= e same=20 > problems. >=20 > What can cause this?=20 >=20 > Just tested booting back into the old kernel, the one guest still won't= start,=20 > 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 --------------enig1E3EC52E5D34E2A45710BEF5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8/Y7QACgkQitSsb3rl5xSrcQCdGtDWNBcs3hnwaaLjnwLTRp9g eJsAn2NI4rpX7DVj9CPTb3WXtFVXM9k6 =uLAv -----END PGP SIGNATURE----- --------------enig1E3EC52E5D34E2A45710BEF5--