From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 208091] vcpu1, guest rIP offset ignored wrmsr or rdmsr
Date: Mon, 08 Jun 2020 16:06:08 +0000 [thread overview]
Message-ID: <bug-208091-28872-E7o1uJpQJG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208091-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208091
--- Comment #5 from Joris L. (commandline@protonmail.com) ---
(In reply to Sean Christopherson from comment #3)
> The "ignored {rd,wr}msr" output is expected when kvm.ignore_msrs=1, which is
> not the default. Is that enabled for any particular reason? Or maybe a
> better question is, what is it that you're trying to do and what, if any,
> errors are occurring?
>
> E.g. in the first trace, it looks like you're advertising an Intel vCPU to
> the guest on top of AMD hardware. That can be made to work, but it's not
> recommended. Ignoring MSRs in that scenario is almost guaranteed to cause
> weirdness.
Thanks Sean. I am cleaning up this config. Will check.
This is indeed a Ryzen CPU with Qemu/Proxmox on top of it.
For GPU Passthrough to a VM the kvm.ignore_msrs=1 is often recommended.
I brief test shows the VM is not working properly without this parameter, even
when booting the VM with CPU:host.
br,
Joris
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-06-08 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 17:09 [Bug 208091] New: vcpu1, guest rIP offset ignored wrmsr or rdmsr bugzilla-daemon
2020-06-06 17:10 ` [Bug 208091] " bugzilla-daemon
2020-06-06 17:16 ` bugzilla-daemon
2020-06-06 17:37 ` bugzilla-daemon
2020-06-08 15:18 ` bugzilla-daemon
2020-06-08 15:50 ` bugzilla-daemon
2020-06-08 15:55 ` bugzilla-daemon
2020-06-08 16:06 ` bugzilla-daemon [this message]
2020-06-08 16:15 ` bugzilla-daemon
2020-06-08 19:15 ` bugzilla-daemon
2020-06-08 19:23 ` bugzilla-daemon
2020-06-19 22:24 ` 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-208091-28872-E7o1uJpQJG@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.