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>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000006415f00619b1d7ce Content-Type: text/plain; charset="UTF-8" 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 > --0000000000006415f00619b1d7ce Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div>Awesome!! Congrats :-)</div><div dir=3D"auto"><br></= div><div dir=3D"auto">Here is some example of running NuttX RTOS on RV in a= web browser using TinyEMU + VirtIO :-)</div><div dir=3D"auto"><br></div><d= iv><a href=3D"https://github.com/lupyuen/nuttx-tinyemu">https://github.com/= lupyuen/nuttx-tinyemu</a><br></div><div dir=3D"auto"><br></div><div data-sm= artmail=3D"gmail_signature">--<br>CeDeROM, SQ7MHZ, <a href=3D"http://www.to= mek.cedro.info">http://www.tomek.cedro.info</a></div></div><br><div class= =3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, May 30, 2024= , 22:16 Emil Tsalapatis <<a href=3D"mailto:emil@etsalapatis.com">emil@et= salapatis.com</a>> wrote:<br></div><blockquote class=3D"gmail_quote" sty= le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div d= ir=3D"ltr">Hi everyone,<br><br>=C2=A0 =C2=A0 while developing a virtiofs ke= rnel driver I have written a debug virtio transport to test virtio drivers = inside a VM without requiring nested virtualization or support from=20 the host. The transport allows paravirt devices to be emulated in local=20 userspace instead of a host, so we can create paravirt devices and test=20 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=20 the FUSE server (which is normally in the host) in a single machine.<br><di= v><br></div><div>I have uploaded the WIP code [<a href=3D"https://reviews.f= reebsd.org/D45370" target=3D"_blank" rel=3D"noreferrer">here</a>], and an o= verview of the design [<a href=3D"https://gist.github.com/etsal/4280b6f16c1= 815d64ffda7ecce0b66f5" target=3D"_blank" rel=3D"noreferrer">here</a>]. The patch has a ways to go, and currently only supports virtio-blk=20 device emulation as a PoC, but feedback is welcome and appreciated.=20 Please also let me know if there is interest in using this for testing=20 other virtio devices apart from virtiofs.</div><font color=3D"#888888"><br>= --Emil</font></div> </blockquote></div> --0000000000006415f00619b1d7ce--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXj=xnnYMk9PUe3j6BA1Z6mt_-Q=1XgpzfZ0bBpnagVXpoA>