From: Paolo Bonzini <pbonzini@redhat.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: kvm list <kvm@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Krish Sadhukhan <krish.sadhukhan@oracle.com>,
yzt356@gmail.com, jmattson@google.com, namit@vmware.com,
sean.j.christopherson@intel.com,
Basil Eljuse <Basil.Eljuse@arm.com>,
Andrew Jones <drjones@redhat.com>,
Alexandru Elisei <alexandru.elisei@arm.com>
Subject: Re: kvm-unit-tests : Kconfigs and extra kernel args for full coverage
Date: Tue, 25 Feb 2020 15:21:44 +0100 [thread overview]
Message-ID: <fec48277-5f42-8f2d-288c-2b8591c33bee@redhat.com> (raw)
In-Reply-To: <CA+G9fYuTNr3YrehjuQD=nCXhdrirxGaiNEVMS+mHcM0fGVigVQ@mail.gmail.com>
On 25/02/20 10:55, Naresh Kamboju wrote:
> Running latest kvm-unit-tests on x86_64 got this output [1].
> "VMX enabled and locked by BIOS"
> We will enable on our BIOS and re-run these tests.
The message is saying it is already enabled; you don't have to do anything.
Paolo
prev parent reply other threads:[~2020-02-25 14:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 12:53 kvm-unit-tests : Kconfigs and extra kernel args for full coverage Naresh Kamboju
2020-02-24 13:06 ` Paolo Bonzini
2020-02-24 17:06 ` Naresh Kamboju
2020-02-24 17:30 ` Sean Christopherson
2020-02-24 21:22 ` Dan Rue
2020-02-25 7:31 ` Paolo Bonzini
2020-02-24 13:21 ` Alexandru Elisei
2020-02-24 13:38 ` Andrew Jones
2020-02-24 13:47 ` Alexandru Elisei
2020-02-24 14:59 ` Andrew Jones
2020-02-24 16:55 ` Naresh Kamboju
2020-02-24 17:36 ` Alexandru Elisei
2020-02-24 17:44 ` Naresh Kamboju
2020-02-25 8:20 ` Naresh Kamboju
2020-03-03 16:02 ` Alexandru Elisei
2020-03-03 18:53 ` Naresh Kamboju
2020-03-05 10:11 ` Marc Zyngier
2020-02-24 17:29 ` Naresh Kamboju
2020-02-24 20:02 ` Paolo Bonzini
2020-02-25 9:55 ` Naresh Kamboju
2020-02-25 14:21 ` Paolo Bonzini [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=fec48277-5f42-8f2d-288c-2b8591c33bee@redhat.com \
--to=pbonzini@redhat.com \
--cc=Basil.Eljuse@arm.com \
--cc=alexandru.elisei@arm.com \
--cc=drjones@redhat.com \
--cc=jmattson@google.com \
--cc=krish.sadhukhan@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=namit@vmware.com \
--cc=naresh.kamboju@linaro.org \
--cc=sean.j.christopherson@intel.com \
--cc=yzt356@gmail.com \
/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).