From: Thomas Huth <1902451@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1902451] Re: incorrect cpuid feature detection
Date: Sun, 09 May 2021 14:56:09 -0000 [thread overview]
Message-ID: <162057216916.16126.5333833489938775787.malone@soybean.canonical.com> (raw)
In-Reply-To: 160426338728.14730.2439588061093712843.malonedeb@wampee.canonical.com
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".
If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:
1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:
https://gitlab.com/qemu-project/qemu/-/issues
and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.
2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" or "Confirmed" within the next 60 days (other-
wise it will get closed as "Expired"). We will then eventually migrate
the ticket automatically to the new system (but you won't be the reporter
of the bug in the new system and thus you won't get notified on changes
anymore).
Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
** Tags added: i386
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1902451
Title:
incorrect cpuid feature detection
Status in QEMU:
Incomplete
Bug description:
Hello,
I am currently developing a x64 kernel and I wanted to check through
cpuid if some features are available in the guest. When I try to
enable cpu features like vmcb_clean or constant_tsc qemu is saying
that my host doesn't support the requested features. However cat
/proc/cpuinfo tells a different story:
model name: AMD Ryzen 5 3500U
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme pti ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca
I also checked it myself by running cpuid and check the bits as in the
AMD Manual. Everything checks out but qemu still fails.
QEMU version: QEMU emulator version 4.2.0
$ qemu-system-x86_64 -cpu host,+vmcb_clean,enforce -enable-kvm -drive format=raw,file=target/x86_64-os/debug/bootimage-my_kernel.bin -serial stdio -display none
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8000000AH:EDX.vmcb-clean [bit 5]
qemu-system-x86_64: Host doesn't support requested features
or
$ qemu-system-x86_64 -cpu host,+constant_tsc,enforce -enable-kvm -drive format=raw,file=target/x86_64-os/debug/bootimage-my_kernel.bin -serial stdio -display none
qemu-system-x86_64: Property '.constant_tsc' not found
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1902451/+subscriptions
next prev parent reply other threads:[~2021-05-09 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 20:43 [Bug 1902451] [NEW] incorrect cpuid feature detection Luis
2020-11-01 20:57 ` [Bug 1902451] " Luis
2021-05-09 14:56 ` Thomas Huth [this message]
2021-07-09 4:17 ` Launchpad Bug Tracker
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=162057216916.16126.5333833489938775787.malone@soybean.canonical.com \
--to=1902451@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).