From: Xavier <1877716@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1877716] Re: Win10 guest unsuable after a few minutes
Date: Sat, 09 May 2020 08:17:17 -0000 [thread overview]
Message-ID: <158901223755.5986.15843160190337741176.malone@soybean.canonical.com> (raw)
In-Reply-To: 158901182209.5021.12832610872088111923.malonedeb@soybean.canonical.com
Note that bisecting is difficult due to the nature of the bug (does not
appear before 5 to 10 minutes on my machine).
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1877716
Title:
Win10 guest unsuable after a few minutes
Status in QEMU:
New
Bug description:
On Arch Linux, the recent qemu package update seems to misbehave on
some systems. In my case, my Windows 10 guest runs fine for around 5
minutes and then start to get really sluggish, even unresponsive. It
needs to be forced off. I could reproduce this on a minimal VM with no
passthrough, although my current testing setup involves an nvme pcie
passthrough.
I bisected it to the following commit which rapidly starts to run sluggishly on my setup:
https://github.com/qemu/qemu/commit/73fd282e7b6dd4e4ea1c3bbb3d302c8db51e4ccf
I've ran the previous commit (
https://github.com/qemu/qemu/commit/b321051cf48ccc2d3d832af111d688f2282f089b
) for the entire night without an issue so far.
I believe this might be a duplicate of
https://bugs.launchpad.net/qemu/+bug/1873032 , although I'm not sure.
Linux cc 5.6.10-arch1-1 #1 SMP PREEMPT Sat, 02 May 2020 19:11:54 +0000 x86_64 GNU/Linux
AMD Ryzen 7 2700X Eight-Core Processor
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1877716/+subscriptions
next prev parent reply other threads:[~2020-05-09 8:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 8:10 [Bug 1877716] [NEW] Win10 guest unsuable after a few minutes Xavier
2020-05-09 8:15 ` [Bug 1877716] " Xavier
2020-05-09 8:17 ` Xavier [this message]
2020-05-09 8:19 ` Xavier
2020-05-09 11:18 ` zkrx
2020-05-11 8:31 ` [Bug 1877716] Re: Win10 guest unusable " zkrx
2020-05-21 10:27 ` Stefan Hajnoczi
2020-05-11 9:12 ` [Bug 1877716] [NEW] Win10 guest unsuable " Stefan Hajnoczi
2020-05-11 9:12 ` Stefan Hajnoczi
2020-05-11 9:45 ` Stefan Hajnoczi
2020-05-11 9:45 ` Stefan Hajnoczi
2020-05-11 9:58 ` [Bug 1877716] Re: Win10 guest unusable " post-factum
2020-05-11 10:08 ` Alexander Bus
2020-05-11 12:36 ` Stefan Hajnoczi
2020-05-11 15:21 ` Stefan Hajnoczi
2020-05-11 18:09 ` Anatol Pomozov
2020-05-11 19:13 ` Stefan Hajnoczi
2020-05-12 6:11 ` post-factum
2020-05-12 15:19 ` zkrx
2020-05-12 16:21 ` Stefan Hajnoczi
2020-05-14 18:06 ` Anatol Pomozov
2020-05-22 4:48 ` Thomas Huth
2020-08-20 14:55 ` Thomas Huth
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=158901223755.5986.15843160190337741176.malone@soybean.canonical.com \
--to=1877716@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.