[Rust-VMM] Add Xen support to vmm-reference? (was Re: Call for topics and skipping next weeks sync)

Alex Bennée alex.bennee at linaro.org
Wed Jul 13 15:39:23 UTC 2022

(added xen/rust-vmm to CC)

Trilok Soni <tsoni at quicinc.com> writes:

> Hello Alex,
> It would be good to check if there is a enough interest to make
> "vmm-reference" extended to work w/ Type-1 Hypervisor like Xen. This
> will clean-up vmm-reference w/ KVM references, and it will be a good
> independent tool to test the new interfaces additions in the rust-vmm.
> https://github.com/rust-vmm/vmm-reference

We have certainly talked about it before and the we've put in some of
the groundwork with the xen-sys crate
(https://github.com/rust-vmm/xen-sys) which we are using for the
xen-vhost-master work. Off the top of my head we would need to work out:

  - Which additional APIs need implementing for VMM lifecycle management
  - How the run loop would look
    - AIUI Hyper-V munges this for rust-vmm by providing a KVM-like
      ioctl API (POC via CrosVM: https://github.com/petrutlucian94/crosvm/tree/windows)
    - See also https://github.com/rust-vmm/community/issues/121
  - Would we aim for full independence from the exiting Xen userspace libs?
    - xen-vhost-master was brought up using them, now slowly being
      replaced with pure rust

I've added it as a discussion topic for the sync call:


It would be great is we could get any interested folks from the rust-vmm
and Xen communities to come along to the call.

> ---Trilok Soni
> -----Original Message-----
> From: Alex Bennée <alex.bennee at linaro.org> 
> Sent: Wednesday, July 13, 2022 2:16 AM
> To: Stratos Mailing List <stratos-dev at op-lists.linaro.org>
> Cc: Viresh Kumar <viresh.kumar at linaro.org>; Mathieu Poirier
> <mathieu.poirier at linaro.org>; Mike Holmes <mike.holmes at linaro.org>;
> Azzedine Touzni <atouzni at qti.qualcomm.com>; Stefano Stabellini
> <stefano.stabellini at xilinx.com>; Christopher Clark
> <christopher.w.clark at gmail.com>; Arnd Bergmann
> <arnd.bergmann at linaro.org>; Peter Griffin <peter.griffin at linaro.org>;
> AKASHI Takahiro <takahiro.akashi at linaro.org>; Artem Mygaiev
> <Artem_Mygaiev at epam.com>; Leonardo Garcia
> <leonardo.garcia at linaro.org>; Trilok Soni <tsoni at quicinc.com>; Randy
> Linnell <randy.linnell at linaro.org>; don.harbin at linaro.org; Sumit
> Semwal <sumit.semwal at linaro.org>
> Subject: Call for topics and skipping next weeks sync
> WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
> Hi All,
> I'll be on holiday (moving house) next week so I won't be able to
> chair the Stratos sync meeting. As it is the middle of summer I'm
> going to propose we skip next weeks sync and re-convene on the 3rd of
> August. Any objections?
> While on the subject of sync meetings are there any topics to discuss.
> We've had some discussions on next rust-vmm device to implement but
> beyond a vague "maybe virtio-gpu to help with demos" I don't think
> we've nailed it down. virtio-can also keeps getting mentioned and
> while useful I'm wary it's not pushing our exploration of the
> possibilities of virtio further.
> I did a talk at GST22 last week which was an overview of VirtIO and what we had done so far as well as discussing some future directions. You can see the talk at:
>   https://huawei-events.de/en/gsts22-j83dco-vod.htm
>   (Day 2 stream, Chapter 6/TS 05:13:00)
> In it potential future areas of exploration where:
> Improve Xen API
> ═══════════════
>   • More standard mmap
>   • direct irqfd/eventfd routing
> Memory Isolation
> ════════════════
>   • fat virtqueue
>   • iommu/grants vs regions
>   (x-over with pKVM/CCA?)
> Bare metal rust
> ═══════════════
>   • re-use exiting VirtIO logic
>   • but without POSIX layer
> I'd like to get a better steer on what we should focus on next after we've demoed our existing rust-vmm daemons and the Xen vhost-master work.

Alex Bennée

More information about the Rust-vmm mailing list