Indeed, Virtualization.framework already supported virtio in guests before, but that's when they added host drivers. By the way this:
> In the Virtio model, providing such support is the task of the operating system, not the virtualiser.
is wrong. Virtualization.framework is a standard implementation of a virtualiser that is shipped with macOS, and while it includes virtio, it does not have to be part of the OS; the same task can be done by anyone (for example QEMU).
The low-level, OS-dependent part of virtualization support is called Hypervisor.framework and it does not have any knowledge of virtio.
> In the Virtio model, providing such support is the task of the operating system, not the virtualiser.
is wrong. Virtualization.framework is a standard implementation of a virtualiser that is shipped with macOS, and while it includes virtio, it does not have to be part of the OS; the same task can be done by anyone (for example QEMU).
The low-level, OS-dependent part of virtualization support is called Hypervisor.framework and it does not have any knowledge of virtio.