<qyliss>
Nice, now I can happily run weston-terminal inside sway in the VM, and do windowing and use the keyboard and mouse
<qyliss>
From here there are two things I need to do -- one is to extract the compositor-side bits of virtio_wl from crosvm into a standalone daemon I can run in the VM, and the other is to write a virtio device for crosvm that somehow copies virtio messages into another running crosvm
<qyliss>
I think I'll start with the latter, but I won't really be able to test either until both are working, which is annoying.
<qyliss>
Demo on the crosvm-demo branch, as always
busu has joined #spectrum
debu has quit [Ping timeout: 260 seconds]
<IdleBot_5e50c57d>
I wonder if hacking virtio_net to work with VM-to-VM virtio has fewer moving parts than compositor bits
<IdleBot_5e50c57d>
Or maybe just a virtio-as-a-pipe could be implemented (a low overhead VM-to-VM pipe could be a useful fallback for many things)
<qyliss>
The latter is what I'm hoping to do
<qyliss>
But I'm using virtio_wl to test because a) it's never been don guest->guest so is more exciting b) I'm more familiar with how that works than other virtio things.