From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 203477] [AMD][KVM] Windows L1 guest becomes extremely slow and unusable after enabling Hyper-V
Date: Mon, 12 Oct 2020 08:57:45 +0000 [thread overview]
Message-ID: <bug-203477-28872-W1XyR1jiRu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203477-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203477
vkuznets@redhat.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vkuznets@redhat.com
--- Comment #7 from vkuznets@redhat.com ---
(In reply to Yonggang Luo from comment #6)
>-cpu
> host,enforce,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,
> hv_stimer,hv_synic,hv_time,hv_vapic,hv_vpindex,+kvm_pv_eoi,+kvm_pv_unhalt,
> +lahf_lm,+sep,+svm,-hypervisor
> ```
Try adding 'hv_stimer_direct' to the list, Hyper-V can't use synthetic timers
otherwise. Also, why do you need '-hypervisor' flag? Could you try without it?
Also, please try with the latest upstream kernel (5.9). 5.3 has a lot of known
nested SVM related bugs.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-10-12 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 4:30 [Bug 203477] New: [AMD][KVM] Windows L1 guest becomes extremely slow and unusable after enabling Hyper-V bugzilla-daemon
2019-07-29 22:07 ` [Bug 203477] " bugzilla-daemon
2019-07-31 16:01 ` bugzilla-daemon
2019-09-19 3:11 ` bugzilla-daemon
2020-07-26 18:11 ` bugzilla-daemon
2020-10-11 18:47 ` bugzilla-daemon
2020-10-11 18:50 ` bugzilla-daemon
2020-10-12 8:57 ` bugzilla-daemon [this message]
2020-10-12 12:34 ` bugzilla-daemon
2022-05-23 19:23 ` bugzilla-daemon
2023-03-07 8:13 ` bugzilla-daemon
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=bug-203477-28872-W1XyR1jiRu@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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.