提升KVM异构虚拟机启动效率:透传(pass-through)、DMA映射(VFIO、PCI、IOMMU)、virtio-balloon、异步DMA映射、预处理 技术标签: 【操作系统】 【虚拟化与云】导读:KVM Forum 2020 是 KVM 社区最为重要和权威的大会。本文为阿里云工程师李伟男和郭成在 KVM Forum 2020 中的演讲内容整理
Currently, Cloud Hypervisor does not set a VIRTIO_IOMMU_F_INPUT_RANGE feature bit for the VirtIO IOMMU device, which, according to spec[1], means that the guest may use the whole 64-bit address space is for IOMMU purposes: >If the feature is not offered, virtual mappings span over the...
In preparation for bouncing virtio data for devices advertising the VIRTIO_F_IOMMU_PLATFORM feature, allocate an array of bounce buffer structures in the vring, one per descriptor. Signed-off-by: Will Deacon <willdeacon@google.com> [ Paul: pick from the Android tree. Rebase to the upstream ...
Summary: Libvirt: disallow virtio-gpu to boot with vIOMMU Keywords: Status: CLOSED WONTFIX Alias: None Product: Red Hat Enterprise Linux 7 Component: libvirt Version: 7.5 Hardware: Unspecified OS: Unspecified Priority: low Severity: medium Target Milestone: rc Target Release: ...
Description of problem: virtio-win drivers are not reporting VIRTIO_F_IOMMU_PLATFORM feature. There are several things that should be done to fix it: 1. Ensure that Windows drivers are using Windows kernel DMA (easier for storage and network drivers that are already using framework specific APIs...
Bug 1549595 - Add support in virtio-serial Windows driver for VIRTIO_F_IOMMU_PLATFORM virtio feature Keywords: FutureFeature × Status: CLOSED ERRATA Alias: None Product: Red Hat Enterprise Linux 8 Component: virtio-win Sub Component: virtio-win-prewhql Version: 8.0 Hardware: Unsp...
Bug 1549597 - Add support in virtio-balloon Windows driver for VIRTIO_F_IOMMU_PLATFORM virtio feature Keywords: FutureFeature × Status: CLOSED ERRATA Alias: None Product: Red Hat Enterprise Linux 8 Component: virtio-win Sub Component: virtio-win-prewhql Version: 8.0 Hardware: Uns...
Description of problem: virtio-win drivers are not reporting VIRTIO_F_IOMMU_PLATFORM feature. There are several things that should be done to fix it: 1. Ensure that Windows drivers are using Windows kernel DMA (easier for storage and network drivers that are already using framework specific APIs...