From: Eduardo Habkost <ehabkost@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/7] qemu-doc: Document minimum kernel version for KVM in x86_64
Date: Tue, 10 Oct 2017 12:33:35 -0300 [thread overview]
Message-ID: <20171010153335.GC3246@localhost.localdomain> (raw)
In-Reply-To: <f4bd17b9-42ca-0e2a-1a84-57b17510bb30@redhat.com>
On Mon, Oct 09, 2017 at 03:40:02PM +0200, Paolo Bonzini wrote:
> On 06/10/2017 23:52, Eduardo Habkost wrote:
> > The default set of KVM CPU features require the host kernel to
> > support them. KVM_PV_EOI is the newest one, and was included on
> > Linux v3.6 (Linux commit ae7a2a3f).
> >
> > Running on an old host might break management software
> > expectations because the latest machine-type won't be runnable
> > while older machine-types might be runnable. Document v3.6 as
> > the minimum kernel version for KVM on x86_64.
> >
> > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> > ---
> > qemu-doc.texi | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/qemu-doc.texi b/qemu-doc.texi
> > index ecd186a159..be45b6b6f6 100644
> > --- a/qemu-doc.texi
> > +++ b/qemu-doc.texi
> > @@ -37,6 +37,7 @@
> > * QEMU System emulator for non PC targets::
> > * QEMU Guest Agent::
> > * QEMU User space emulator::
> > +* System requirements::
> > * Implementation notes::
> > * Deprecated features::
> > * License::
> > @@ -2348,6 +2349,14 @@ Act as if the host page size was 'pagesize' bytes
> > Run the emulation in single step mode.
> > @end table
> >
> > +@node System requirements
> > +@chapter System requirements
> > +
> > +@section KVM kernel module
> > +
> > +On x86_64 hosts, the default set of CPU features enabled by the KVM accelerator
> > +require the host to be running Linux v3.6 or newer.
> > +
> >
> > @include qemu-tech.texi
> >
> >
>
> Maybe we should expand on the consequences of running on older versions?
I intentionally tried to not make any commitment to what should
happen if running an older kernel. But a quick explanation of
what can happen is probably a good idea. I will try to come up
with something.
--
Eduardo
next prev parent reply other threads:[~2017-10-10 15:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 21:52 [Qemu-devel] [PATCH 0/7] x86: Rework KVM-defaults compat code, enable kvm_pv_unhalt by default Eduardo Habkost
2017-10-06 21:52 ` [Qemu-devel] [PATCH 1/7] qemu-doc: Document minimum kernel version for KVM in x86_64 Eduardo Habkost
2017-10-09 13:40 ` Paolo Bonzini
2017-10-10 15:33 ` Eduardo Habkost [this message]
2017-10-06 21:52 ` [Qemu-devel] [PATCH 2/7] target/i386: x86_cpu_expand_feature() helper Eduardo Habkost
2017-10-06 21:52 ` [Qemu-devel] [PATCH 3/7] target/i386: Use global variables to control KVM defaults Eduardo Habkost
2017-10-06 21:52 ` [Qemu-devel] [PATCH 4/7] kvm: Define KVM_FEAT_* even if CONFIG_KVM is not defined Eduardo Habkost
2017-10-06 21:52 ` [Qemu-devel] [PATCH 5/7] target/i386: Handle kvm_auto_* compat in x86_cpu_expand_features() Eduardo Habkost
2017-10-06 21:52 ` [Qemu-devel] [PATCH 6/7] pc: Use compat_props to control KVM defaults compatibility Eduardo Habkost
2017-10-06 21:52 ` [Qemu-devel] [PATCH 7/7] target/i386: Enable kvm_pv_unhalt by default Eduardo Habkost
2017-10-09 14:40 ` Paolo Bonzini
2017-10-09 14:43 ` Alexander Graf
2017-10-09 13:39 ` [Qemu-devel] [PATCH 0/7] x86: Rework KVM-defaults compat code, enable " Paolo Bonzini
2017-10-09 15:15 ` Waiman Long
2017-10-09 15:47 ` Paolo Bonzini
2017-10-10 15:50 ` Eduardo Habkost
2017-10-10 18:07 ` Waiman Long
2017-10-10 19:41 ` Eduardo Habkost
2017-10-11 20:19 ` Waiman Long
2017-10-13 19:01 ` Eduardo Habkost
2017-10-13 20:58 ` Waiman Long
2017-10-13 23:56 ` Eduardo Habkost
2017-11-07 11:21 ` [Qemu-devel] [libvirt] " Paolo Bonzini
2017-11-08 20:07 ` Eduardo Habkost
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=20171010153335.GC3246@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--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).