From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 209809] New: kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
Date: Thu, 22 Oct 2020 10:15:50 +0000 [thread overview]
Message-ID: <bug-209809-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=209809
Bug ID: 209809
Summary: kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
Product: Virtualization
Version: unspecified
Kernel Version: 5.8.16
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: nicolopiazzalunga@gmail.com
Regression: No
It is likely not a bug in itself, just annoying.
Since maybe 5.6 series, with virtualization disabled in BIOS, I get this
warning in my journal:
kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
Is it necessary to produce a message at the 'warning' level?
Would it be possible instead to do it at the 'notice' or lower level?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-10-22 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 10:15 bugzilla-daemon [this message]
2021-04-30 11:20 ` [Bug 209809] kernel: x86/cpu: VMX (outside TXT) disabled by BIOS 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-209809-28872@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 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).