Re: vhost-user implementations

[Demi Marie Obenour <demiobenour@gmail.com>]

[-- Attachment #1.1.1: Type: text/plain, Size: 903 bytes --]

On 5/27/26 05:52, Alyssa Ross wrote:
> Alex Bennée <alex.bennee@linaro.org> writes:
> 
>> *everyone - do we have a comprehensive list of who implements vhost-user
>>  these days?
> 
> I'll get started with some implementations I know about :)
> 
> Frontends
> ---------
> 
> • crosvm
> • QEMU
> • Cloud Hypervisor
> • Firecracker
> • StratoVirt
> • alioth
> • Dragonball

Crosvm, Cloud Hypervisor, Firecracker, and Dragonball all rely on
vm-memory, so they won't have overlapping memory regions.  QEMU and
StratoVirt both have central address space managers and alioth
only creates a few memory regions with non-overlapping addresses.
Therefore, I would be extremely surprised if overlap is actually
possible in practice.

I strongly suspect that it is safe for a backend to reject overlapping
memory regions.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]