From: "Philippe Mathieu-Daudé" <1879646@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1879646] Re: [Feature request] x86: dump MSR features in human form
Date: Sun, 09 May 2021 15:45:07 -0000 [thread overview]
Message-ID: <162057510740.7144.17393221593080458391.malone@gac.canonical.com> (raw)
In-Reply-To: 158996169456.22050.5633849401809444729.malonedeb@wampee.canonical.com
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'invalid' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/237
** Changed in: qemu
Status: New => Invalid
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #237
https://gitlab.com/qemu-project/qemu/-/issues/237
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1879646
Title:
[Feature request] x86: dump MSR features in human form
Status in QEMU:
Invalid
Bug description:
QEMU might fail because host/guest cpu features are not properly
configured:
qemu-system-x86_64: error: failed to set MSR 0x48f to 0x7fefff00036dfb
qemu-system-x86_64: /root/qemu-master/target/i386/kvm.c:2695:
kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
To ease debugging, it the MSR features bit could be dumped.
Example in this thread:
https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg05593.html
The high 32 bits are 0111 1111 1110 1111 1111 1111.
The low 32 bits are 0000 0011 0110 1101 1111 1011.
The features that are set are the xor, so 0111 1100 1000 0010 0000
0100:
- bit 2, vmx-exit-nosave-debugctl
- bit 9, host address space size, is handled automatically by QEMU
- bit 15, vmx-exit-ack-intr
- bit 17, vmx-exit-save-pat
- bit 18, vmx-exit-load-pat
- bit 19, vmx-exit-save-efer
- bit 20, vmx-exit-load-efer
- bit 21, vmx-exit-save-preemption-timer
This output ^^^ is easier to digest.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1879646/+subscriptions
prev parent reply other threads:[~2021-05-09 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 8:01 [Bug 1879646] [NEW] [Feature request] x86: dump MSR features in human form Philippe Mathieu-Daudé
2021-05-09 15:45 ` Philippe Mathieu-Daudé [this message]
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=162057510740.7144.17393221593080458391.malone@gac.canonical.com \
--to=1879646@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).