qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
	Qinghua Cheng <qcheng@redhat.com>,
	qemu devel list <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: virtio-vsock requires 'disable-legacy=on' in QEMU 5.1
Date: Mon, 17 Aug 2020 16:37:04 +0200	[thread overview]
Message-ID: <20200817163704.33590236.cohuck@redhat.com> (raw)
In-Reply-To: <20200817131128.lgxn3pyzuzly4edp@steredhat>

On Mon, 17 Aug 2020 15:11:28 +0200
Stefano Garzarella <sgarzare@redhat.com> wrote:

> On Mon, Aug 17, 2020 at 12:27:46PM +0200, Cornelia Huck wrote:

> > Speaking of tests: do you have a quick way to test vhost-vsock at hand?
> > Maybe I should add it to my manual repertoire...
> >   
> 
> Sure, maybe the quickest way is to use ncat. Starting from version 7.80,
> it supports AF_VSOCK sockets:
> 
>     host$ ./qemu-system-x86_64 ... -device vhost-vsock-pci,guest-cid=5
> 
>     host$ ncat --vsock -l 1234
> 
>     # vsock address is <cid, port>, cid=2 is used always to reach the host
>     guest$ ncat --vsock 2 1234
> 
> Other tests that I usually run are:
> - iperf-vsock: https://github.com/stefano-garzarella/iperf-vsock
> - vsock test suite in the Linux kernel (tools/testing/vsock)
> 
> Let me know if you want more details on these :-)

Thanks, simply doing some smoke tests with ncat should be enough :)



  reply	other threads:[~2020-08-17 14:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13  9:16 virtio-vsock requires 'disable-legacy=on' in QEMU 5.1 Stefano Garzarella
2020-08-13  9:28 ` Cornelia Huck
2020-08-13 10:24   ` Stefano Garzarella
2020-08-13 10:37     ` Cornelia Huck
2020-08-13 12:04       ` Stefano Garzarella
2020-08-17 10:27         ` Cornelia Huck
2020-08-17 13:11           ` Stefano Garzarella
2020-08-17 14:37             ` Cornelia Huck [this message]
2020-08-18 12:44             ` Cornelia Huck
2020-08-18 14:01               ` Stefano Garzarella
2020-08-18 14:31                 ` Cornelia Huck
2020-08-18 15:28                   ` Stefano Garzarella
2020-08-18 15:49                     ` Cornelia Huck
2020-08-19  9:48       ` Auger Eric
2020-08-13 15:36 ` no-reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200817163704.33590236.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=pasic@linux.ibm.com \
    --cc=qcheng@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).