Irenes[m] has quit [Read error: Connection reset by peer]
thefloweringash has quit [Read error: Connection reset by peer]
sab7iryudpgf6[m] has quit [Read error: Connection reset by peer]
danielrf[m] has quit [Read error: Connection reset by peer]
smrtak[m] has quit [Read error: Connection reset by peer]
edrex has quit [Remote host closed the connection]
alj[m] has quit [Write error: Connection reset by peer]
smrtak[m] has joined #spectrum
sab7iryudpgf6[m] has joined #spectrum
Irenes[m] has joined #spectrum
edrex has joined #spectrum
colemickens has joined #spectrum
danielrf[m] has joined #spectrum
alj[m] has joined #spectrum
hiroshi[m] has joined #spectrum
thefloweringash has joined #spectrum
CcxWrk has joined #spectrum
andi- has quit [Ping timeout: 260 seconds]
tazjin is now known as nijzat
andi- has joined #spectrum
nijzat is now known as tazjin
tazjin is now known as tazjylin
tazjylin is now known as tazlyjin
tazlyjin is now known as tazjin
tilpner has joined #spectrum
<qyliss>
So I have a couple of options here
<qyliss>
One is to see if I can figure out why the patch for virtio-vhost-user doesn't work
<qyliss>
And the other is to start with the other side (try normal vhost, see if I can port cloud hypervisor's implementation to crosvm)
<qyliss>
In theory I could probably get the other side working, and then say "virtio-vhost-user is currently being developed externally, and we'll be able to integrate it as soon as its ready"