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:56:04 +0100 Message-ID: <4F3F67A4.5050309@web.de> References: <201202172149.36904.thomas@fjellstrom.ca> <4F3F63B0.4060305@web.de> <201202180150.39098.thomas@fjellstrom.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig54DC3859340FB84204DD64C9" Cc: KVM To: thomas@fjellstrom.ca Return-path: Received: from fmmailgate03.web.de ([217.72.192.234]:35568 "EHLO fmmailgate03.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752266Ab2BRI4H (ORCPT ); Sat, 18 Feb 2012 03:56:07 -0500 Received: from moweb002.kundenserver.de (moweb002.kundenserver.de [172.19.20.108]) by fmmailgate03.web.de (Postfix) with ESMTP id 7FB551B2B80CF for ; Sat, 18 Feb 2012 09:56:06 +0100 (CET) In-Reply-To: <201202180150.39098.thomas@fjellstrom.ca> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig54DC3859340FB84204DD64C9 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable On 2012-02-18 09:50, Thomas Fjellstrom wrote: > On Sat Feb 18, 2012, Jan Kiszka wrote: >> 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, an= d >>> 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 attemp= ted >>> 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 you= r >> 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 >=20 > Sorry I wasn't clear. If I just update qemu-kvm (And qemu with it, and = not the=20 > kernel), it always just hangs on load.=20 >=20 > current version: > QEMU emulator version 1.0 (qemu-kvm-1.0 Debian 1.0+dfsg-8), Copyright (= c)=20 > 2003-2008 Fabrice Bellard >=20 > gdb thread apply all bt: > Thread 2 (Thread 0x7fe7b810c700 (LWP 14650)): > #0 0x00007fe7c0a11957 in ioctl () from /lib/x86_64-linux-gnu/libc.so.6= > #1 0x00007fe7c53155e9 in kvm_vcpu_ioctl (env=3D, type=3D= out>) at /build/buildd-qemu-kvm_1.0+dfsg-8-amd64-ppNMqm/qemu-kvm-1.0+df= sg/kvm- > all.c:1101 > #2 0x00007fe7c5315731 in kvm_cpu_exec (env=3D0x7fe7c61cb350) at /build= /buildd- > qemu-kvm_1.0+dfsg-8-amd64-ppNMqm/qemu-kvm-1.0+dfsg/kvm-all.c:987 > #3 0x00007fe7c52ecf31 in qemu_kvm_cpu_thread_fn (arg=3D0x7fe7c61cb350)= at=20 > /build/buildd-qemu-kvm_1.0+dfsg-8-amd64-ppNMqm/qemu-kvm-1.0+dfsg/cpus.c= :740 > #4 0x00007fe7c0ccdb50 in start_thread () from /lib/x86_64-linux- > gnu/libpthread.so.0 > #5 0x00007fe7c0a1890d in clone () from /lib/x86_64-linux-gnu/libc.so.6= > #6 0x0000000000000000 in ?? () >=20 > Thread 1 (Thread 0x7fe7c5101900 (LWP 14648)): > #0 0x00007fe7c0a12403 in select () from /lib/x86_64-linux-gnu/libc.so.= 6 > #1 0x00007fe7c525b56c in main_loop_wait (nonblocking=3D= ) at=20 > /build/buildd-qemu-kvm_1.0+dfsg-8-amd64-ppNMqm/qemu-kvm-1.0+dfsg/main- > loop.c:456 > #2 0x00007fe7c51a372f in main_loop () at /build/buildd-qemu-kvm_1.0+df= sg-8- > amd64-ppNMqm/qemu-kvm-1.0+dfsg/vl.c:1482 > #3 main (argc=3D, argv=3D, envp=3D) at=20 > /build/buildd-qemu-kvm_1.0+dfsg-8-amd64-ppNMqm/qemu-kvm-1.0+dfsg/vl.c:3= 523 >=20 > Thanks :) >=20 OK, then we need a kernel view on this. Can you try http://www.linux-kvm.org/page/Tracing ? Thanks, Jan --------------enig54DC3859340FB84204DD64C9 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/Z6QACgkQitSsb3rl5xTpdQCdFPEiC1uL+gR9rWi5FVk+hOyW mf0Anj2MurDycKwtSbI4KwiJLoft+nAg =hWn8 -----END PGP SIGNATURE----- --------------enig54DC3859340FB84204DD64C9--