Difference between revisions of "Passthrough"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
== Activities == | == Activities == | ||
* Review https://www.berrange.com/posts/2018/06/29/cpu-model-configuration-for-qemu-kvm-on-x86-hosts/ | * Review https://www.berrange.com/posts/2018/06/29/cpu-model-configuration-for-qemu-kvm-on-x86-hosts/ | ||
| − | * [[GPU]] passthrough | + | * [[GPU]] passthrough and [[virglrenderer]] |
== See also == | == See also == | ||
Revision as of 11:56, 15 October 2020
Device passthrough is about providing an isolation of devices to a given guest operating system so that the device can be used exclusively by that guest.
Activities
- Review https://www.berrange.com/posts/2018/06/29/cpu-model-configuration-for-qemu-kvm-on-x86-hosts/
- GPU passthrough and virglrenderer
See also
- CPU, GPU, NPU, TPU, DPU, Groq, Proliant, thread (
Pthreads), processor, CPU socket, core, ARM , CPU Virtualization, Intel, AMD,nm,lscpu, AVX-512, Passthrough, CPU intensive, Graviton processor, Branch predictor, vCPU, SSE, Power - KVM, Installation, QEMU,
virsh,virtinst,libguestfs-tools, libvirt, qemu, Red Hat Virtualization (RHV), MacVTap, Virtio, oVirt, KVM services, KVM networking, KVM graphics, CPU, KVM on ARM
Advertising:
