From: Randy Rhoads <1883593@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1883593] Re: Windows XP takes much longer to boot in TCG mode since 5.0
Date: Thu, 18 Jun 2020 00:00:18 -0000 [thread overview]
Message-ID: <159243841840.6020.3116249437326838729.malone@soybean.canonical.com> (raw)
In-Reply-To: 159225010396.5666.14857392307926027696.malonedeb@chaenomeles.canonical.com
Bisecting showed that this is the bad commit:
b55f54bc965607c45b5010a107a792ba333ba654 exec: flush CPU TB cache in
breakpoint_invalidate
And I can indeed confirm that this commit is much slower than the
previous one, e18e5501d8ac692d32657a3e1ef545b14e72b730.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1883593
Title:
Windows XP takes much longer to boot in TCG mode since 5.0
Status in QEMU:
New
Bug description:
Since upgrading from 4.2 to 5.0, a Windows XP VM takes much longer to
boot.
It hangs about three minutes on "welcome" screen with the blue
background, while previously the total boot time was less than a
minute.
The issue only happens in TCG mode (not with KVM) and also happens
with the current master which includes the uring patches (7d3660e7).
I can reproduce this issue with a clean XP install with no flags other
than `-m 2G`. After booting, the performance seems to be normal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1883593/+subscriptions
next prev parent reply other threads:[~2020-06-18 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 19:41 [Bug 1883593] [NEW] Windows XP takes much longer to boot in TCG mode since 5.0 Randy Rhoads
2020-06-16 16:48 ` [Bug 1883593] " Alex Bennée
2020-06-18 0:00 ` Randy Rhoads [this message]
2021-05-06 16:52 ` Thomas Huth
2021-06-10 13:27 ` Peter Maydell
2021-06-10 13:53 ` 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=159243841840.6020.3116249437326838729.malone@soybean.canonical.com \
--to=1883593@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).