qyliss changed the topic of #spectrum to: A compartmentalized operating system | https://spectrum-os.org/ | Logs: https://logs.spectrum-os.org/spectrum/
cole-h has joined #spectrum
jb55 has quit [Remote host closed the connection]
jb55 has joined #spectrum
cole-h has quit [Quit: Goodbye]
<qyliss> Well, I managed to get a single ping packet in each direction over vvu
<MichaelRaskin> Is it again «but only the first one?»
<qyliss> yeah
<bqv> Has this for the most part stalled?
<qyliss> what do you mean by "this"?
<bqv> I see you have funding, but there's also been no substantial changes for a while
<qyliss> have you read the weekly updates?
<qyliss> the reason for no substantial code changes for a while is that the recent work has mostly not been code, but research and investigation
<bqv> Nope, latest looks relevant, but that's not all that obvious to passers by I'd say
<bqv> I see, fair enough
<qyliss> the weekly updates are linked from the home page, but I'm open to suggestions to make them more obvious
<qyliss> Progress is certainly not going as fast as I'd like, but we are getting there, and I work on Spectrum for hours almost every day.
<qyliss> I realise it's not clear in that email what it actually means to somebody who hasn't been following the work, but essentially it means that it is now possible to run Wayland applications in one VM, and display them on a compositor in another VM, without overhead from e.g. tunneling Wayland over a network connection.
<bqv> I'm not sure. My impression was just built from seeing a fairly minimal page (not a problem) that as I saw, just linked to the repos, which were fairly stale. I definitely wouldn't have thought to check a months old blog post for confirmation that it's still active
<qyliss> I was referring to " For more frequent, detailed updates, a "This Week in Spectrum" message is posted on the “discuss” mailing list every week. "
<qyliss> I suppose I could mention that first, above the blog.
<bqv> Oh
<bqv> Yeah I missed that
cole-h has joined #spectrum
jb55 has quit [Remote host closed the connection]
jb55 has joined #spectrum
cole-h has quit [Quit: Goodbye]
<qyliss> It's looking like maybe vvu can do outbound traffic, but not inbound, or something like that
lejonet has joined #spectrum
<qyliss> Somewhat good news
<qyliss> I looked at the source code and it turns out inbound traffic is not actually implemented in the vvu driver yet
<qyliss> (Why is this good news? Because it presumably will be at some point, and this means that I can just note that and move on.)
<qyliss> (Because it's not my bug)
<qyliss> Compare vvu_process_txq (inbound traffic) to vvu_process_rxq here and you'll see what I mean :) https://github.com/ndragazis/dpdk-next-virtio/blob/virtio-vhost-user/drivers/virtio_vhost_user/trans_virtio_vhost_user.c#L379
<qyliss> So I can move on to trying to do vhost-user from crosvm
<qyliss> VirtioDevice in cloud-hypervisor seems to be much closer to crosvm's than I recall Firecracker's being, which is nice for porting the vhost-user code.
<qyliss> Oh wow cloud-hypervisor actually uses the rust-vmm crates
cole-h has joined #spectrum