Рет қаралды 32,387
This presentation will break down the plethora of options available for delivering storage to a virtual machine in KVM/QEMU. It will detail the mechanics and performance trade offs inherent in the different AIO modes, caching options, paravirtualization drivers, and thread settings. We will outline which OpenStack configuration options lead to the most desireable KVM/QEMU configuration settings, and what could be done to further enhance OpenStack's ability to take advantage of everything KVM/QEM.
From the perspective of the Compute service, the QEMU hypervisor is very similar to the KVM hypervisor. Both are controlled through libvirt, both support the same feature set, and all virtual machine images that are compatible with KVM are also compatible with QEMU. The main difference is that QEMU does not support native virtualization. Consequently, QEMU has worse performance than KVM and is a poor choice for a production deployment.
KVM: docs.openstack.org/mitaka/con...
QEMU: docs.openstack.org/ocata/conf...
Speaker(s):
Kyle Bader
Connect with us:
OpenInfra Twitter: / openinfradev
OpenInfra LinkedIn: / mycompany
OpenInfra Facebook: / openinfradev
OpenInfra Website: openinfra.dev/
#OpenInfra #OpenStack #OpenSource