https://git.qemu.org/?p=qemu.git;a=commitdiff;h=76525114736e8f669766
** Changed in: qemu
Status: Fix Committed => Fix Released
--
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:
U
** Changed in: qemu
Status: Confirmed => Fix Committed
--
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 QEM
I have been using this patch
https://patchwork.kernel.org/patch/11346881/ on qemu 4.2 as a fix since
January without any ill effects. It is already included into qemu 5.0
rc0 and rc1, so it seems qemu 5.0 will be free from this bug.
--
You received this bug notification because you are a member o
Also affects me when running Qemu 4.0.0 with -machine pc-q35-3.1. I get
this on the command line:
"qemu-system-x86_64: vhost_region_add_section: Overlapping but not
coherent sections at 11a000".
h/w: AMD Ryzen 3900X, Gigabyte Aorus Pro X570 (latest BIOS), kernel
5.3.0.
With -machine q35 (i.e. pc
I have applied these patches on qemu 4.2 and it seems they do fix the
problem: no more vhost_region_add_section in the log, and I haven't
observed network or general performance loss in the span of one hour.
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Can you try the pair of patches I've just posted:
vhost: Don't pass ram device sections
hyperv/synic: Allocate as ram_device
and let me know if it helps please.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
Hi,
This seems to have died out. How do we proceed to get this looked into
by the correct people?
Thanks,
Damir
--
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 w
Also attaching my libvirt log with a few errors at the end of the log.
Thank you for looking into this!
** Attachment added: "Libvirt_log_command_line"
https://bugs.launchpad.net/qemu/+bug/1811533/+attachment/5290071/+files/libvirt_log.txt
--
You received this bug notification because you
As asked by dgilbert-h, I am attaching my qemu command line. It is
ripped from libvirt log.
** Attachment added: "Bug reproducing Qemu command line from libvirt log."
https://bugs.launchpad.net/qemu/+bug/1811533/+attachment/5290067/+files/qemu_cmdln.txt
--
You received this bug notification
No, I think it's the other way around: clearing guest pages is
unrelated. It is easy to check with the following kernel patch:
diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c
index fff790a3f4ee..73c574f930e3 100644
--- a/arch/x86/kvm/hyperv.c
+++ b/arch/x86/kvm/hyperv.c
@@ -776,7 +776,7
x-hv-synic-kvm-only does two things:
1) Disables in-QEMU synic and this should be unrelated to the issue as it is
unrelated to stimers.
2) Doesn't clear guest pages (HV_X64_MSR_SIEFP/HV_X64_MSR_SIMP). This
can actually be related to huge pages if the cleanup is causing huge
page split. Synic page
Another observation:
Adding CPU flag x-hv-synic-kvm-only also fixes the issue, because it switches
only synic to Qemu 3.0 behavior, leaving other features of > Qemu 3.0 available.
This observation can be related to this commit:
https://github.com/qemu/qemu/commit/9b4cf107b09d18ac30f46fd1c4de8585c
CC's in Vitaly; he knows a bunch about the Hyperv hv_ and windows stuff.
It feels weird that something timer related should change something hugepage
related.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net
Zilvinas/Damir: Can you paste in the qemu commandline you're using
please.
--
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
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 +
Other users are having similar issues:
https://github.com/virtio-win/kvm-guest-drivers-windows/issues/402
https://www.reddit.com/r/VFIO/comments/cc2473/virtio_network_drivers_failing_on_win10_guest/etk6f6i/
** Bug watch added: github.com/virtio-win/kvm-guest-drivers-windows/issues #402
https:/
** Changed in: qemu
Status: New => Confirmed
--
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:
Confi
Still broken with Qemu 4.1rc2 /w Kernel 5.2.
This is a huge problem, as it breaks performance, either in networking
(you can't use the virtio net which is the only 100G adapter afaik), or
you have to disable huge pages, which is a blow to any large vm host, or
it breaks stimer, which increases cpu
Refresh: still happening with Qemu 4.0 and Kernel 5.2.
One additional observation:
4) problem disappears when vhost is disabled.
--
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:
Unstab
19 matches
Mail list logo
