Ideally, the OP should have clarified it as "QEMU-KVM", since QEMU has a plethora of other use cases than a VMM (e.g. qemu-user, qemu atop Hyper-V/Xen/Hyperviso

Ideally, the OP should have clarified it as "QEMU-KVM", since QEMU has a plethora of other use cases than a VMM (e.g. qemu-user, qemu atop Hyper-V/Xen/Hypervisor.Framework, cross-architecture emulation) that are more-or-less used just as often. It shouldn't be a problem for already knowledgeable readers, but it _might_ give false impression that QEMU only works as a KVM-only VMM monitor to others.