Hi Mauro,

On Tue Jun 17, 2025 at 5:49 PM JST, Mauro Carvalho Chehab wrote:

Hi Alex,

Em Tue, 27 May 2025 23:03:39 +0900
Alexandre Courbot [off-list ref] escreveu:

quoted

quoted

quoted

quoted

Btw, I was looking at:

        https://github.com/chromeos/virtio-media

(I'm assuming that this is the QEMU counterpart, right?)  

crosvm actually, but QEMU support is also being worked on.  

Do you have already QEMU patches? The best is to have the Kernel driver
submitted altogether with QEMU, as Kernel developers need it to do the
tests. In my case, I never use crosvm, and I don't have any Chromebook
anymore.  

IIRC Albert Esteve was working on this, maybe he can share the current status.

Any news regards to it?

Albert shared the latest status. There is one in-flight patch series
required in qemu [1], and then this branch of vhost-device should
contain the necessary support [2]. Albert is waiting for the virtio spec
to get merged before sending a pull request IIUC.

[1] https://patchew.org/QEMU/20250217164012.246727-1-aesteve@redhat.com/
[2] https://github.com/aesteve-rh/vhost-device/tree/virtio-media

quoted

Note that crosvm does not require a Chromebook, you can build and run
it pretty easily on a regular PC. I have put together a document to
help with that:

https://github.com/chromeos/virtio-media/blob/main/TRY_IT_OUT.md

I started looking on it today. Already installed crossvm (I had to
install libcap-devel to build it). Still, I'm not familiar with
crossvm, which is a little be painful. In particular, how can I
enable network on it and speedup it?

There is a "./tools/examples/setup_network" in the crosvm repository that
will setup a TAP device. Once this is done, you can pass the "--net
tap-name=crosvm_tap" argument to crosvm, and the network device should
be visible and usable.

Let me reply to the rest of your questions in your latest mail, with the
most recent logs.

Cheers,
Alex.