On Tue, Sep 16, 2025 at 06:48:46PM +0200, Magnus Kulke wrote: > Added mshv to the list of accelerators in doc text. > > Signed-off-by: Magnus Kulke <[email protected]> > --- > docs/about/build-platforms.rst | 2 +- > docs/devel/codebase.rst | 2 +- > docs/glossary.rst | 6 +++--- > docs/system/introduction.rst | 3 +++ > qemu-options.hx | 16 ++++++++-------- > 5 files changed, 16 insertions(+), 13 deletions(-) > > diff --git a/docs/about/build-platforms.rst b/docs/about/build-platforms.rst > index 8671c3be9c..06ba0ddc9a 100644 > --- a/docs/about/build-platforms.rst > +++ b/docs/about/build-platforms.rst > @@ -55,7 +55,7 @@ Those hosts are officially supported, with various > accelerators: > * - SPARC > - tcg > * - x86 > - - hvf (64 bit only), kvm, nvmm, tcg, whpx (64 bit only), xen > + - hvf (64 bit only), mshv (64 bit only), kvm, nvmm, tcg, whpx (64 bit > only), xen > > Other host architectures are not supported. It is possible to build QEMU > system > emulation on an unsupported host architecture using the configure > diff --git a/docs/devel/codebase.rst b/docs/devel/codebase.rst > index 2a3143787a..69d8827117 100644 > --- a/docs/devel/codebase.rst > +++ b/docs/devel/codebase.rst > @@ -48,7 +48,7 @@ yet, so sometimes the source code is all you have. > * `accel <https://gitlab.com/qemu-project/qemu/-/tree/master/accel>`_: > Infrastructure and architecture agnostic code related to the various > `accelerators <Accelerators>` supported by QEMU > - (TCG, KVM, hvf, whpx, xen, nvmm). > + (TCG, KVM, hvf, whpx, xen, nvmm, mshv). > Contains interfaces for operations that will be implemented per > `target <https://gitlab.com/qemu-project/qemu/-/tree/master/target>`_. > * `audio <https://gitlab.com/qemu-project/qemu/-/tree/master/audio>`_: > diff --git a/docs/glossary.rst b/docs/glossary.rst > index 4fa044bfb6..0fa75c9d1e 100644 > --- a/docs/glossary.rst > +++ b/docs/glossary.rst
> @@ -102,8 +102,8 @@ hypervisors. > > In the context of QEMU, an hypervisor is an API, provided by the Host OS, > allowing to execute virtual machines. Linux implementation is KVM (and > supports > -Xen as well). For MacOS, it's HVF. Windows defines WHPX. And NetBSD provides > -NVMM. > +Xen and MSHV as well). For MacOS, it's HVF. Windows defines WHPX. And NetBSD > +provides NVMM. This is a bit of a bike-shed colouring comment, but how about saying "Linux provides a choice of KVM, Xen or MSHV; MacOS provides HVF; Windows provides WPHX; NetBSD provides NVMM." With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
