mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-01-09 06:25:19 +00:00
b44f35e2cf
Using virtio-blk with SEV on host kernels prior to 5.1 didn't work because of SWIOTLB limitations and the way virtio has to use it over DMA-API for SEV (see [1] for detailed info). That is no longer true, so reword the kbase article accordingly. For reference, these are the upstream kernel commits lifting the virtio-blk limitation: abe420bfae528c92bd8cc5ecb62dc95672b1fd6f 492366f7b4237257ef50ca9c431a6a0d50225aca 133d624b1cee16906134e92d5befb843b58bcf31 e6d6dd6c875eb3c9b69bb640419405726e6e0bbe fd1068e1860e44aaaa337b516df4518d1ce98da1 [1] https://lore.kernel.org/linux-block/20190110134433.15672-1-joro@8bytes.org/ Signed-off-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Martin Kletzander <mkletzan@redhat.com> |
||
|---|---|---|
| .. | ||
| backing_chains.rst | ||
| debuglogs.rst | ||
| domainstatecapture.rst | ||
| incrementalbackupinternals.rst | ||
| index.rst | ||
| kvm-realtime.rst | ||
| launch_security_sev.rst | ||
| locking-lockd.rst | ||
| locking-sanlock.rst | ||
| locking.rst | ||
| meson.build | ||
| migrationinternals.rst | ||
| qemu-passthrough-security.rst | ||
| rpm-deployment.rst | ||
| s390_protected_virt.rst | ||
| secureusage.rst | ||
| systemtap.rst | ||
| virtiofs.rst | ||