From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:44337) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UX7WY-0001NG-8p for qemu-devel@nongnu.org; Tue, 30 Apr 2013 06:11:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UX7WQ-0006SA-FF for qemu-devel@nongnu.org; Tue, 30 Apr 2013 06:11:02 -0400 Received: from indium.canonical.com ([91.189.90.7]:54710) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UX7WQ-0006Rz-5s for qemu-devel@nongnu.org; Tue, 30 Apr 2013 06:10:54 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.71 #1 (Debian)) id 1UX7WP-0004iq-Be for ; Tue, 30 Apr 2013 10:10:53 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 572952E8024 for ; Tue, 30 Apr 2013 10:10:53 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Tue, 30 Apr 2013 10:04:16 -0000 From: Maxim Loparev Sender: bounces@canonical.com References: <20130430080722.32341.54160.malonedeb@gac.canonical.com> Message-Id: <20130430100416.31833.19966.malone@gac.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Reply-To: Bug 1174654 <1174654@bugs.launchpad.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org core i3-2120 with kvm accel used on host. -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1174654 Title: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Status in QEMU: New Bug description: I have Windows XP SP3 inside qemu VM. All works fine in 12.10. But after upgraiding to 13.04 i have to restart the VM each time i resuming my host machine, because qemu process starts to take CPU cycles and OS inside VM is very slow and sluggish. However it's still controllable and could be shutdown by itself. According to the taskmgr any active process takes 99% CPU. It's not stucked on some single process. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions