On 09/09/16 23:07, Michael S. Tsirkin wrote:
[...]
> Seems to fail build:
>
> /scm/qemu/hw/s390x/virtio-ccw.c:1664:4: error: ‘VirtioCcwDevice {aka
> struct VirtioCcwDevice}’ has no member named ‘bus_id’
> DEFINE_PROP_STRING("devno", VirtioCcwDevice, bus_id),
> ^
> /scm/qemu/hw/s390x/virtio
On Tue, Aug 16, 2016 at 01:27:22PM +0100, Stefan Hajnoczi wrote:
> Implement the new virtio sockets device for host<->guest communication
> using the Sockets API. Most of the work is done in a vhost kernel
> driver so that virtio-vsock can hook into the AF_VSOCK address family.
> The QEMU vhost-vs
On Tue, 23 Aug 2016 19:45:15 +0200
Claudio Imbrenda wrote:
> Hi Stefan!
>
> I tried it on s390x and... it doesn't compile :(
> Something has been changed somewhere behind our backs, and you need to
> change this line to get it to compile again:
>
> --- virtio-ccw.c~ 2016-08-23 16:37:14.0
Hi Stefan!
I tried it on s390x and... it doesn't compile :(
Something has been changed somewhere behind our backs, and you need to
change this line to get it to compile again:
--- virtio-ccw.c~ 2016-08-23 16:37:14.0 +0200
+++ virtio-ccw.c2016-08-23 16:41:10.587853314 +020
Implement the new virtio sockets device for host<->guest communication
using the Sockets API. Most of the work is done in a vhost kernel
driver so that virtio-vsock can hook into the AF_VSOCK address family.
The QEMU vhost-vsock device handles configuration and live migration
while the rx/tx happe
