qyliss changed the topic of #spectrum to: A compartmentalized operating system | https://spectrum-os.org/ | Logs: https://logs.spectrum-os.org/spectrum/
<qyliss> I'm not that interested in the built-in 9p either, but it's useful enough for testing
andi- has quit [Remote host closed the connection]
andi- has joined #spectrum
cole-h has quit [Quit: Goodbye]
<IdleBot_85f8451c> Well, I hoped that either built-in p9 or builtin virtio-fs could be used to mount the store!
maxdevjs has quit [Ping timeout: 246 seconds]
multi has quit [*.net *.split]
multi has joined #spectrum
AllaDelight has joined #spectrum
AllaDelight has quit [Client Quit]
<qyliss> Cool, now I can dynamically add Wayland sockets at runtime
<qyliss> That was surprisingly easy
<pie_> :O
<IdleBot_85f8451c> In what direction? You can have a Wayland VM that can get more incoming Wayland connections than initially planned?
<qyliss> Well, more incoming sockets
<qyliss> Which can be Wayland connections
<qyliss> (And indeed that's why I wrote this)
<IdleBot_85f8451c> And you can have honest incoming sockets in a VM?
<IdleBot_85f8451c> Which I guess could have many incoming connections naturally…
<qyliss> No
<IdleBot_85f8451c> Which side requests the extra sockets? VM via some server?
<qyliss> These are virtio_wl sockets, which generally have to be interacted with using the virtio_wl ioctls
<qyliss> Although you can use read() and write() on them, like a pipe
<qyliss> But no send/recv/sendmsg/recvmsg
<qyliss> And you can't accept() on these
<qyliss> My motivation for making it possible to add new sockets at runtime is to work around the lack of accept()
<qyliss> Extra sockets are added my the host
<qyliss> I envision it working like: when a new application VM is started, the host code that starts that crosvm creates a socket pair and connects one end to the Wayland VM, and the other to the application VM
<IdleBot_85f8451c> Oh right, you can create two connected sockets that are both listening ones
<qyliss> Yeah
<IdleBot_85f8451c> And then you need to use a separate control socket to tell VM to actually connect to the new socket
<IdleBot_85f8451c> For the record: TWIS does make perfect sense to me this week
nicoo has quit [Remote host closed the connection]
nicoo has joined #spectrum
cole-h has joined #spectrum
nicoo has quit [Remote host closed the connection]
nicoo has joined #spectrum
maxdevjs has joined #spectrum
colemickens has quit [*.net *.split]
grufwub has quit [*.net *.split]
grufwub has joined #spectrum
tnias has quit [*.net *.split]
vilhalmer has quit [*.net *.split]
DrWhax has quit [*.net *.split]
mearon has quit [*.net *.split]
clever has quit [*.net *.split]
lukegb has quit [*.net *.split]
vilhalmer has joined #spectrum
tnias has joined #spectrum
DrWhax has joined #spectrum
lukegb has joined #spectrum
clever has joined #spectrum
mearon has joined #spectrum
thefloweringash has quit [*.net *.split]
zgrep has quit [*.net *.split]
zgrep has joined #spectrum
thefloweringash has joined #spectrum
danielrf[m] has quit [*.net *.split]
edrex has quit [Ping timeout: 244 seconds]
thefloweringash has quit [Ping timeout: 252 seconds]
Irenes[m] has quit [Ping timeout: 260 seconds]
qyliss has quit [*.net *.split]
leah2 has quit [*.net *.split]
leah2 has joined #spectrum
qyliss has joined #spectrum
leah2 has quit [Max SendQ exceeded]
Profpatsch has quit [*.net *.split]
edwtjo has quit [*.net *.split]
Profpatsch has joined #spectrum
edwtjo has joined #spectrum
alj[m] has quit [Ping timeout: 260 seconds]
vilhalmer has quit [Ping timeout: 272 seconds]
leah2 has joined #spectrum
vilhalmer has joined #spectrum
alj[m] has joined #spectrum
colemickens has joined #spectrum
thefloweringash has joined #spectrum
edrex has joined #spectrum
danielrf[m] has joined #spectrum
Irenes[m] has joined #spectrum