Date: Thu, 30 May 2024 22:37:42 +0200 From: Tomek CEDRO <tomek@cedro.info> To: emil@etsalapatis.com Cc: Virtualisation on FreeBSD <freebsd-virtualization@freebsd.org> Subject: Re: [RFC] virtio testing framework Message-ID: <CAFYkXj=xnnYMk9PUe3j6BA1Z6mt_-Q=1XgpzfZ0bBpnagVXpoA@mail.gmail.com> In-Reply-To: <CABFh=a7-v_c_x6pGW86z1AX95FmcCWEuWciNxPmAOWs31V=s5Q@mail.gmail.com> References: <CABFh=a7-v_c_x6pGW86z1AX95FmcCWEuWciNxPmAOWs31V=s5Q@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Awesome!! Congrats :-) Here is some example of running NuttX RTOS on RV in a web browser using TinyEMU + VirtIO :-) https://github.com/lupyuen/nuttx-tinyemu -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info On Thu, May 30, 2024, 22:16 Emil Tsalapatis <emil@etsalapatis.com> wrote: > Hi everyone, > > while developing a virtiofs kernel driver I have written a debug > virtio transport to test virtio drivers inside a VM without requiring > nested virtualization or support from the host. The transport allows > paravirt devices to be emulated in local userspace instead of a host, so we > can create paravirt devices and test them as necessary. For virtiofs in > particular, it allows us to reuse the existing FUSE tests since we can now > run both the virtiofs driver and the FUSE server (which is normally in the > host) in a single machine. > > I have uploaded the WIP code [here <https://reviews.freebsd.org/D45370>], > and an overview of the design [here > <https://gist.github.com/etsal/4280b6f16c1815d64ffda7ecce0b66f5>]. The > patch has a ways to go, and currently only supports virtio-blk device > emulation as a PoC, but feedback is welcome and appreciated. Please also > let me know if there is interest in using this for testing other virtio > devices apart from virtiofs. > > --Emil > [-- Attachment #2 --] <div dir="auto"><div>Awesome!! Congrats :-)</div><div dir="auto"><br></div><div dir="auto">Here is some example of running NuttX RTOS on RV in a web browser using TinyEMU + VirtIO :-)</div><div dir="auto"><br></div><div><a href="https://github.com/lupyuen/nuttx-tinyemu">https://github.com/lupyuen/nuttx-tinyemu</a><br></div><div dir="auto"><br></div><div data-smartmail="gmail_signature">--<br>CeDeROM, SQ7MHZ, <a href="http://www.tomek.cedro.info">http://www.tomek.cedro.info</a></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 30, 2024, 22:16 Emil Tsalapatis <<a href="mailto:emil@etsalapatis.com">emil@etsalapatis.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi everyone,<br><br> while developing a virtiofs kernel driver I have written a debug virtio transport to test virtio drivers inside a VM without requiring nested virtualization or support from the host. The transport allows paravirt devices to be emulated in local userspace instead of a host, so we can create paravirt devices and test them as necessary. For virtiofs in particular, it allows us to reuse the existing FUSE tests since we can now run both the virtiofs driver and the FUSE server (which is normally in the host) in a single machine.<br><div><br></div><div>I have uploaded the WIP code [<a href="https://reviews.freebsd.org/D45370" target="_blank" rel="noreferrer">here</a>], and an overview of the design [<a href="https://gist.github.com/etsal/4280b6f16c1815d64ffda7ecce0b66f5" target="_blank" rel="noreferrer">here</a>]. The patch has a ways to go, and currently only supports virtio-blk device emulation as a PoC, but feedback is welcome and appreciated. Please also let me know if there is interest in using this for testing other virtio devices apart from virtiofs.</div><font color="#888888"><br>--Emil</font></div> </blockquote></div>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXj=xnnYMk9PUe3j6BA1Z6mt_-Q=1XgpzfZ0bBpnagVXpoA>