From: "Mark A. Hershberger" <mah@everybody.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1174654] Re: qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram
Date: Sat, 08 Dec 2018 18:43:32 -0000 [thread overview]
Message-ID: <154429461298.889.622814861831968708.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20130430080722.32341.54160.malonedeb@gac.canonical.com
I was seeing this problem when my Debian laptop suspended. The CentOS
guest would begin consuming a lot of cpu and only a hard-reset would fix
it.
Changing the rtc line to
<timer name='rtc' track='guest'/>
seems to have fixed it, though I haven't done extensive testing yet.
Thanks!
--
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:
Confirmed
Status in qemu package in Ubuntu:
Invalid
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
stuck on some single process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1174654/+subscriptions
next prev parent reply other threads:[~2018-12-08 18:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 8:07 [Qemu-devel] [Bug 1174654] [NEW] qemu-system-x86_64 takes 100% CPU after host machine resumed from suspend to ram Maxim Loparev
2013-04-30 10:04 ` [Qemu-devel] [Bug 1174654] " Maxim Loparev
2013-04-30 12:54 ` [Qemu-devel] [Bug 1174654] [NEW] " Serge Hallyn
2013-04-30 13:32 ` [Qemu-devel] [Bug 1174654] " Maxim Loparev
2013-04-30 13:52 ` Serge Hallyn
2013-04-30 13:42 ` Maxim Loparev
2013-04-30 14:20 ` Maxim Loparev
2013-04-30 14:41 ` Serge Hallyn
2013-04-30 14:50 ` Serge Hallyn
2013-05-08 9:11 ` Maxim Loparev
2013-05-08 15:25 ` Serge Hallyn
2013-05-08 19:01 ` John Basila
2013-07-31 13:34 ` Richard Jones
2013-10-12 9:06 ` tobias
2013-10-13 13:14 ` Paolo Bonzini
2013-10-17 20:29 ` tobias
2013-10-18 2:33 ` mike
2013-10-18 7:12 ` tobias appelo
2013-10-18 7:26 ` mike
2013-10-18 7:41 ` tobias
2013-10-18 8:31 ` tobias
2013-10-30 21:54 ` tobias
2014-02-04 7:15 ` Matt Keith
2015-07-20 2:59 ` derek
2015-12-18 22:10 ` varacanero
2016-10-06 21:25 ` Jürgen Veidt
2017-01-19 18:17 ` Francois Gouget
2018-12-08 18:43 ` Mark A. Hershberger [this message]
2020-11-10 17:57 ` Thomas Huth
2021-01-10 4:17 ` Launchpad Bug Tracker
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=154429461298.889.622814861831968708.malone@chaenomeles.canonical.com \
--to=mah@everybody.org \
--cc=1174654@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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.