You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new EFI flavor turns libkrun into an open-source alternative of Virtualization.framework on macOS. It brings some excellent additions, such as a Vulkan-capable virtio-gpu, which allows you to offload compute workloads to the host's GPU, and an extended virtio-fs implementation. Podman 5.2 is taking advantage of this: https://linuxiac.com/podman-5-2-enhances-macos-vms-with-gpu-support/. Would be nice to add this VMM backend in addition to qemu and Virtualization.framework.
The text was updated successfully, but these errors were encountered:
libkrun uses Hypervisor.framework the same as QEMU. Adding a new backend is tremendous effort. Why is it not possible to port the vulkan-capable virtio-gpu to QEMU instead? Is there any documentation on how they are doing it?
libkrun uses Hypervisor.framework the same as QEMU. Adding a new backend is tremendous effort. Why is it not possible to port the vulkan-capable virtio-gpu to QEMU instead? Is there any documentation on how they are doing it?
Maybe this patch to make virtio-gpu to support Venus on macOS ?
The new EFI flavor turns
libkrun
into an open-source alternative of Virtualization.framework on macOS. It brings some excellent additions, such as a Vulkan-capable virtio-gpu, which allows you to offload compute workloads to the host's GPU, and an extended virtio-fs implementation. Podman 5.2 is taking advantage of this: https://linuxiac.com/podman-5-2-enhances-macos-vms-with-gpu-support/. Would be nice to add this VMM backend in addition to qemu and Virtualization.framework.The text was updated successfully, but these errors were encountered: