From: Damir <1811533@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1811533] Re: Unstable Win10 guest with qemu 3.1 + huge pages + hv_stimer
Date: Thu, 19 Sep 2019 19:22:09 -0000 [thread overview]
Message-ID: <156892092959.13812.6362371663429445203.malone@gac.canonical.com> (raw)
In-Reply-To: 154731859474.20612.3794172498936114295.malonedeb@soybean.canonical.com
What can be done to increase the visibility of this? It's quite annoying
to deal with.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1811533
Title:
Unstable Win10 guest with qemu 3.1 + huge pages + hv_stimer
Status in QEMU:
Confirmed
Bug description:
Host:
Gentoo linux x86_64, kernel 4.20.1
Qemu 3.1.0
CPU: Intel i7 6850K
Chipset: X99
Guest:
Windows 10 Pro 64bit (1809)
Machine type: pc-q35_3.1
Hyper-V enlightenments: hv_stimer,hv_reenlightenment,hv_frequencies,hv_vapic,hv_reset,hv_synic,hv_runtime,hv_vpindex,hv_time,hv_relaxed,hv_spinlocks=0x1fff
Memory: 16GB backed by 2MB huge pages
Issue:
Once guest is started, log gets flooded with:
qemu-system-x86_64: vhost_region_add_section: Overlapping but not
coherent sections at 103000
or
qemu-system-x86_64: vhost_region_add_section:Section rounded to 0
prior to previous 1f000
(line endings change)
and as time goes guest loses network access (virtio-net-pci) and
general performance diminishes to extent of freezing applications.
Observations:
1) problem disappears when hv_stimer is removed
2) problem disappears when memory backing with huge pages is disabled
3) problem disappears when machine type is downgraded to pc-q35_3.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1811533/+subscriptions
next prev parent reply other threads:[~2019-09-19 19:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 18:43 [Qemu-devel] [Bug 1811533] [NEW] Unstable Win10 guest with qemu 3.1 + huge pages + hv_stimer Žilvinas Žaltiena
2019-07-12 15:40 ` [Qemu-devel] [Bug 1811533] " Žilvinas Žaltiena
2019-08-07 19:13 ` Damir
2019-08-08 6:04 ` Žilvinas Žaltiena
2019-08-11 7:44 ` Žilvinas Žaltiena
2019-09-19 19:22 ` Damir [this message]
2019-09-20 10:20 ` Dr. David Alan Gilbert
2019-09-20 10:22 ` Dr. David Alan Gilbert
2019-09-20 11:02 ` Žilvinas Žaltiena
2019-09-20 11:24 ` Vitaly Kuznetsov
2019-09-20 15:38 ` Vitaly Kuznetsov
2019-09-20 19:01 ` Žilvinas Žaltiena
2019-09-20 19:41 ` Damir
2019-10-10 17:47 ` Damir
2020-01-08 13:57 ` Dr. David Alan Gilbert
2020-01-08 17:28 ` Žilvinas Žaltiena
2020-03-18 0:01 ` Heiko Sieger
2020-04-01 8:01 ` Žilvinas Žaltiena
2020-04-01 8:28 ` Dr. David Alan Gilbert
2020-08-20 15:38 ` 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=156892092959.13812.6362371663429445203.malone@gac.canonical.com \
--to=1811533@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 NNTP newsgroup(s).